public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Tony Vroon <tony@linx.net>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	"Langsdorf, Mark" <mark.langsdorf@amd.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 2.6.31-07068-g43c1266 Early boot exception
Date: Tue, 22 Sep 2009 20:40:05 +0900	[thread overview]
Message-ID: <4AB8B795.4010400@kernel.org> (raw)
In-Reply-To: <20090922112351.6b07d259@infradead.org>

Arjan van de Ven wrote:
> if you build with debuginfo.. run
> perl scripts/markup_oops.pl on your dmesg
> 
> that gives you not just the line, but the whole context of the crash.

Darn, I knew there gotta be something like that.  That's a pretty nice
script.  Thanks for the tip.  :-)

-- 
tejun

  reply	other threads:[~2009-09-22 11:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 19:14 2.6.31-07068-g43c1266 Early boot exception Tony Vroon
2009-09-21 19:26 ` H. Peter Anvin
2009-09-21 19:35   ` Tony Vroon
2009-09-21 19:36     ` Ingo Molnar
2009-09-21 21:13     ` H. Peter Anvin
2009-09-21 20:47   ` Tony Vroon
2009-09-22  9:08     ` Tejun Heo
2009-09-22  9:23       ` Arjan van de Ven
2009-09-22 11:40         ` Tejun Heo [this message]
2009-09-22 19:36       ` Tony Vroon
2009-09-23  5:52         ` Tejun Heo
2009-09-23  9:19           ` Tony Vroon
2009-09-23  9:23             ` Tejun Heo
2009-09-23 15:46               ` H. Peter Anvin
2009-09-23 23:25                 ` Tejun Heo
2009-09-24  0:05         ` Tejun Heo
2009-09-21 19:53 ` 2.6.31-0.1-default-07068-g43c1266 lockdep warning and scheduling while atomic BUG Henk Martijn
2009-09-21 20:04   ` Oliver Neukum
2009-09-21 20:17     ` Henk Martijn

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=4AB8B795.4010400@kernel.org \
    --to=tj@kernel.org \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mingo@elte.hu \
    --cc=tony@linx.net \
    /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