From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, Jiri Slaby <jslaby@suse.cz>,
stable@kernel.org, "James E.J. Bottomley" <jejb@parisc-linux.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [stable] apparent regression (crash) - 2.6.38.6
Date: Wed, 18 May 2011 17:25:05 -0700 [thread overview]
Message-ID: <20110519002505.GB8697@kroah.com> (raw)
In-Reply-To: <20110511193451.GC26010@kroah.com>
On Wed, May 11, 2011 at 12:34:51PM -0700, Greg KH wrote:
> On Wed, May 11, 2011 at 02:19:17PM -0500, James Bottomley wrote:
> > On Wed, 2011-05-11 at 08:30 +0200, Jiri Slaby wrote:
> > > On 05/10/2011 09:55 PM, Michael Tokarev wrote:
> > > > Hello.
> > > >
> > > > I just tried 2.6.38.6 (which has been released today), and
> > > > discovered that it crashes during bootup on my machine.
> > > > 2.6.38.5 with exactly the same config works.
> > >
> > > Is it reproducible?
> > >
> > > > Unfortunately I don't have time _right now_ to debug the
> > > > issue, but will try tomorrow.
> > > >
> > > > For now, here's a part of dmesg with an oops, captured
> > > > using netconsole. If someone have a clue, please speak
> > > > up ;)
> > > >
> > > > What I also noticed is that for some reason, udev now loads
> > > > option driver (option: v0.7.2:USB Driver for GSM modems),
> > > > even if I don't have any modems connected to the system.
> > > > This is obviously not related to the issue at hand.
> > > ...
> > > > [ 106.761932] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:12.1/usb2/2-2/2-2:1.0/input/input6
> > > > [ 106.762170] generic-usb 0003:046D:C044.0004: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:12.1-2/input0
> > > > [ 106.994177] scsi 10:0:0:0: Direct-Access Kingston DT HyperX HMAP PQ: 0 ANSI: 0 CCS
> > > > [ 106.994458] sd 10:0:0:0: Attached scsi generic sg3 type 0
> > > > [ 106.994628] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
> > > > [ 106.994755] IP: [<ffffffff811bec1b>] elv_queue_empty+0x1b/0x30
> >
> > Hmm, it's another missing elevator guard, like this patch:
> >
> > http://marc.info/?l=linux-scsi&m=130348673628282
> >
> > I think the bug here is that q->elevator is null, so dereferencing
> > elevator->ops gives the bug.
>
> Is this patch going to Linus anytime soon?
Ping?
next prev parent reply other threads:[~2011-05-19 0:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:55 apparent regression (crash) - 2.6.38.6 Michael Tokarev
2011-05-11 6:30 ` Jiri Slaby
2011-05-11 19:19 ` James Bottomley
2011-05-11 19:31 ` Michael Tokarev
2011-05-11 20:22 ` Michael Tokarev
2011-05-19 0:25 ` [stable] " Greg KH
2011-05-11 19:34 ` Greg KH
2011-05-19 0:25 ` Greg KH [this message]
2011-05-19 3:39 ` James Bottomley
2011-05-19 8:20 ` Arkadiusz Miskiewicz
2011-06-01 12:34 ` Atsushi Nemoto
2011-06-03 7:01 ` Michael Tokarev
2011-06-03 7:09 ` lists+linux-kernel
2011-06-03 7:15 ` Jiri Slaby
2011-06-04 11:38 ` Atsushi Nemoto
2011-05-11 7:58 ` Wolfgang Walter
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 13:06 [stable] " Paul Slootman
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=20110519002505.GB8697@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jejb@parisc-linux.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=stable@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