LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: add option to show more code in oops reports
Date: Mon, 29 Jan 2007 10:40:17 -0500	[thread overview]
Message-ID: <45BE1561.6000303@redhat.com> (raw)
In-Reply-To: <200701290444.21861.ak@suse.de>

Andi Kleen wrote:
> On Friday 26 January 2007 00:56, Chuck Ebbert wrote:
>
>   
>> Can't think of a way to word the justification, but I've wanted to see more
>> code a few times.
>>     
>
> Hmm, not sure I see the point. The Code line is just that you can
> make sense of random mailing list oopses where you don't
> have a vmlinux. But as long as you don't make the option
> the default you would need to ask people to set it for you -- and when you
> ask you could always as well ask about the vmlinux and get
> as much code as you ever wanted.
>   
This was patch inspired by my finding out that code in the running
kernel might have
been modified at runtime by some strange bug, and looking at vmlinux
might not be
helpful.

See:
    http://lkml.org/lkml/2007/1/24/143
> So unless it's default it's likely useless and I don't think
> it is a good idea to make it default because oops screen estate
> is so precious.
>   
Yeah, there's no way it could be the default. But I'd like to see if
Alistair John Strachan's
running kernel matches the vmlinux he posted with that strange
unexplained oops.

  reply	other threads:[~2007-01-29 15:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 20:22 Chuck Ebbert
2007-01-25 22:55 ` Andrew Morton
2007-01-25 23:56   ` Chuck Ebbert
2007-01-29  3:44     ` Andi Kleen
2007-01-29 15:40       ` Chuck Ebbert [this message]
2007-01-29 18:03         ` Andi Kleen
2007-01-29 20:11 Chuck Ebbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45BE1561.6000303@redhat.com \
    --to=cebbert@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [patch] i386: add option to show more code in oops reports' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).