From: Matthew Wilcox <matthew@wil.cx>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: new kernel oops in recent kernels
Date: Sun, 16 Mar 2008 10:42:23 -0600 [thread overview]
Message-ID: <20080316164223.GA26285@parisc-linux.org> (raw)
In-Reply-To: <1205680748.3050.29.camel@localhost>
On Sun, Mar 16, 2008 at 04:19:08PM +0100, Giuseppe Sacco wrote:
> testing latest kernels on SGI O2, I found this new kernel oops. It has
> been produced with kernel from linux-mips.org git of yesterday night.
> A very similar oops has been reported by others[0] using 2.6.22.
> CPU 0 Unable to handle kernel paging request at virtual address 0000000000000000, epc == 0000000000000000, ra == 0000000000000000
I'm not familiar with MIPS; is epc the program counter? If so, this
would be a branch to 0. That's somewhat confusing as I don't see any
function pointers used within sr_drive_status(). How accurate are MIPS
backtraces?
> Call Trace:
> [<ffffffff802460b0>] sr_drive_status+0x50/0xe8
> [<ffffffff8024bb84>] cdrom_ioctl+0x5f4/0x1208
> [<ffffffff80245c6c>] sr_block_ioctl+0x64/0xe8
It would be interesting to see a disassembly (objdump -dr
drivers/scsi/sr_ioctl.o) of sr_drive_status from say 0x40 to 0x60.
And if that calls a function, it would be interesting to put in printks
to figure out where we're dereferencing a null pointer.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-03-16 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 15:19 new kernel oops in recent kernels Giuseppe Sacco
2008-03-16 16:39 ` James Bottomley
2008-03-16 18:32 ` Giuseppe Sacco
2008-03-16 18:47 ` James Bottomley
2008-03-16 16:42 ` Matthew Wilcox [this message]
2008-03-16 18:29 ` Giuseppe Sacco
2008-03-17 3:58 ` Matthew Wilcox
2008-03-17 4:41 ` Matthew Wilcox
2008-03-17 8:17 ` Giuseppe Sacco
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=20080316164223.GA26285@parisc-linux.org \
--to=matthew@wil.cx \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-scsi@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