public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: [BUG 2.6.26-rc1] scsi (or sysfs or vm?) oops in sr_probe()
Date: Thu, 08 May 2008 19:05:57 -0500	[thread overview]
Message-ID: <1210291557.3114.74.camel@localhost.localdomain> (raw)
In-Reply-To: <1209915560.16283.31.camel@localhost.localdomain>

On Sun, 2008-05-04 at 10:39 -0500, James Bottomley wrote:
> On Sun, 2008-05-04 at 10:25 -0500, James Bottomley wrote:
> > On Sun, 2008-05-04 at 07:22 -0400, Jeff Garzik wrote:
> > > See attached files for additional config detail.
> > > 
> > > Platform summary:  AMD64 2x2 (== 4 cores), Fedora 8/x86-64
> > > 
> > > Driver 'sr' needs updating - please use bus_type methods
> > > BUG: unable to handle kernel NULL pointer dereference at 00000000000005d8
> > > IP: [<ffffffff8025e10c>] get_page_from_freelist+0x43/0x573
> > > PGD 7e90f067 PUD 7edbc067 PMD 0
> > > Oops: 0000 [1] SMP
> > 
> > Is this with CONFIG_SLAB or CONFIG_SLUB?
> > 
> > I don't see it in my test systems, but they're CONFIG_SLAB
> 
> OK, should have looked at the attachments:
> 
> ...
> CONFIG_SLAB=y
> # CONFIG_SLUB is not set
> # CONFIG_SLOB is not set
> ...
> 
> Since you also have this:
> 
> CONFIG_DEBUG_KERNEL=y
> 
> Can you tell me what source line corresponds to 
> 
> :sr_mod:sr_probe+0x17b/0x4a9

Ping on this, please.  I suspect it will tell us the faulting call is
kmalloc and that it's definitely a vm issue, but we need this data as a
first step.

James



      reply	other threads:[~2008-05-09  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 11:22 [BUG 2.6.26-rc1] scsi (or sysfs or vm?) oops in sr_probe() Jeff Garzik
2008-05-04 15:25 ` James Bottomley
2008-05-04 15:38   ` Matthew Wilcox
2008-05-04 15:39   ` James Bottomley
2008-05-09  0:05     ` James Bottomley [this message]

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=1210291557.3114.74.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.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