From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kevin Winchester <kjwinchester@gmail.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
NetDev <netdev@vger.kernel.org>
Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008
Date: Tue, 08 Jan 2008 18:08:04 +0100 [thread overview]
Message-ID: <p73bq7wqm8b.fsf@bingen.suse.de> (raw)
In-Reply-To: <alpine.LFD.1.00.0801071851120.3148@woody.linux-foundation.org> (Linus Torvalds's message of "Mon\, 7 Jan 2008 19\:26\:12 -0800 \(PST\)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> I usually just compile a small program like
Just use scripts/decodecode and cat the Code line into that.
> particularly good way to do it, and the old "ksymoops" program used to do
> a pretty good job of this, but I'm used to that particular idiotic way
> myself, since it's how I've basically always done it)
>
> After that, you still need to try to match up the assembly code with the
> source code and figure out what variables the register contents actually
> are all about. You can often try to do a
>
> make the/affected/file.s
IMHO better is
make the/file/xyz.lst
which gives you a listing with binary data in there which can be
grepped for.
But you should install a very recent binutils because older objdump -S
couldn't deal with unit-at-a-time compilers.
-Andi
next prev parent reply other threads:[~2008-01-08 17:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 21:06 Top 10 kernel oopses for the week ending January 5th, 2008 Arjan van de Ven
2008-01-05 21:26 ` Al Viro
2008-01-05 21:39 ` Al Viro
2008-01-07 17:44 ` J. Bruce Fields
2008-01-08 1:19 ` Kevin Winchester
2008-01-08 3:26 ` Linus Torvalds
2008-01-08 5:59 ` Al Viro
2008-01-08 7:33 ` Jarek Poplawski
2008-01-10 4:13 ` Neil Brown
2008-01-10 5:53 ` Al Viro
2008-01-14 1:36 ` Neil Brown
2008-01-08 16:14 ` Randy Dunlap
2008-01-08 17:42 ` Arjan van de Ven
2008-01-08 18:08 ` Linus Torvalds
2008-01-08 18:16 ` Arjan van de Ven
2008-01-08 18:27 ` Linus Torvalds
2008-01-08 19:05 ` Arjan van de Ven
2008-01-08 19:31 ` Linus Torvalds
2008-01-08 22:56 ` Rafael J. Wysocki
2008-01-08 17:08 ` Andi Kleen [this message]
2008-01-06 3:30 ` Andi Kleen
2008-01-06 3:31 ` Arjan van de Ven
2008-01-06 3:50 ` Andi Kleen
2008-01-09 14:12 ` Johannes Berg
2008-01-09 15:28 ` Arjan van de Ven
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=p73bq7wqm8b.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bfields@fieldses.org \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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).