From: Andrew Morton <akpm@zip.com.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Badari Pulavarty <pbadari@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261!
Date: Fri, 09 Aug 2002 14:00:37 -0700 [thread overview]
Message-ID: <3D542D75.7FEA9DDF@zip.com.au> (raw)
In-Reply-To: 3D542C06.50008@us.ibm.com
Dave Hansen wrote:
>
> Badari Pulavarty wrote:
> > Code; c0160d0f <d_unhash+f/70> <=====
> > 0: 0f 0b ud2a <=====
> > Code; c0160d11 <d_unhash+11/70>
> > 2: 05 01 00 db 2a add $0x2adb0001,%eax
> > Code; c0160d16 <d_unhash+16/70>
> > 7: c0 (bad)
>
> Doesn't that (bad) instruction look suspicious? Martin was seeing
> strange oopses on Hummer (16-way NUMA-Q) compiling with egcs 2.91
> because it was generating bad instructions. It may be another
> problem, but that c0 jumped out at me. The two instructions after it
> look bretty bogus too.
We're encoding the file-and-line information in the program text
immediately after the undefined opcode, so you'll always see junk
in there. Sorry.
It would be much more useful if the oops code were to dump the
text preceding the exception EIP rather than after it, actually.
I think Keith said that ksymoops supports that.
next prev parent reply other threads:[~2002-08-09 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 17:32 kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261! Badari Pulavarty
2002-08-09 20:54 ` Dave Hansen
2002-08-09 21:00 ` Andrew Morton [this message]
2002-08-09 21:22 ` Andries Brouwer
2002-08-09 21:47 ` Patrick Mochel
2002-08-10 1:09 ` Keith Owens
2002-08-10 8:08 ` Russell King
2002-08-10 8:44 ` Keith Owens
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=3D542D75.7FEA9DDF@zip.com.au \
--to=akpm@zip.com.au \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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