LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <cebbert@redhat.com>
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 19:03:08 +0100	[thread overview]
Message-ID: <200701291903.08739.ak@suse.de> (raw)
In-Reply-To: <45BE1561.6000303@redhat.com>


> 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.

Hmm ok, although I still suspect in such a case you'll be better
off with a full kcrash dump.

-Andi

  reply	other threads:[~2007-01-29 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 20:22 [patch] i386: add option to show more code in oops reports 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
2007-01-29 18:03         ` Andi Kleen [this message]
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=200701291903.08739.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).