From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
bugme-daemon@bugzilla.kernel.org, dchris@gmail.com
Subject: Re: [Bugme-new] [Bug 8940] New: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
Date: Sun, 26 Aug 2007 07:57:45 -0600 [thread overview]
Message-ID: <20070826135745.GE14130@parisc-linux.org> (raw)
In-Reply-To: <20070826005207.4f0b62ce.akpm@linux-foundation.org>
On Sun, Aug 26, 2007 at 12:52:07AM -0700, Andrew Morton wrote:
> On Sat, 25 Aug 2007 09:47:40 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> > Problem Description: I got this error message:
> > BUG: unable to handle kernel NULL pointer dereference at virtual address
> > 00000000
> > in dmesg output when connecting a USB device. Turning off
> > CONFIG_SCSI_SCAN_ASYNC fixed the problem. Apparently there is a bug in SCSI
> > core code.
I don't think SCSI_SCAN_ASYNC is the problem. It's probably a
coincidence. SCSI_SCAN_ASYNC doesn't touch the call-path reported in
the backtrace.
In any case, if it is SCSI_SCAN_ASYNC-related, there's an outstanding
patch to fix the locking, which is slated for inclusion in 2.6.24.
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=a93a091df8232fad60867d41fbc3be855a0b78f2
--
"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:[~2007-08-26 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8940-10286@http.bugzilla.kernel.org/>
2007-08-26 7:52 ` [Bugme-new] [Bug 8940] New: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 Andrew Morton
2007-08-26 13:57 ` Matthew Wilcox [this message]
2007-08-26 20:56 ` Alan Stern
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=20070826135745.GE14130@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=dchris@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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