From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [BUG] unable to handle kernel paging request in next-20080516 (scsi_bus_uevent)
Date: Sun, 18 May 2008 11:22:06 +0000 (UTC) [thread overview]
Message-ID: <g0p3gu$3gh$1@ger.gmane.org> (raw)
In-Reply-To: 20080518021423.3dcf0ddd.akpm@linux-foundation.org
On Sun, 18 May 2008 02:14:23 -0700, Andrew Morton wrote:
> (cc's added)
>
> On Sat, 17 May 2008 12:50:24 +0000 (UTC) Sitsofe Wheeler
>
>> Sometimes when booting next-20080516 on Ubuntu Gutsy an oops then a
>> panic will occur. At first I thought it might be provoked by vga=0x164
>> but this does not appear to be the case and the issue is seemingly
>> random. I've hand transcribed the oops so there may be errors in it but
>> hopefully it will still help:
>>
>> BUG: unable to handle kernel paging request at e6f17fac IP:
>> [<c02604d6>] scsi_bus_uevent+0x1/0x17 *pde = 2714b163 *pte = 26f17160
>> Oops: 0000 [#1] DEBUG_PAGEALLOC
>> last sysfs file:
>>
> I thought we'd already fixed this?
Thanks to your tip off I've found that this bug is already in bugzilla
(complete with the commit that caused the regression) - http://
bugzilla.kernel.org/show_bug.cgi?id=10711 . There's nothing there that
says it has been fixed though. I'll look harder before reporting problems
next time.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2008-05-18 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 12:50 [BUG] unable to handle kernel paging request in next-20080516 Sitsofe Wheeler
2008-05-18 9:14 ` Andrew Morton
2008-05-18 11:22 ` Sitsofe Wheeler [this message]
2008-05-18 16:00 ` Sitsofe Wheeler
2008-05-18 17:47 ` Greg KH
2008-05-18 20:22 ` Sitsofe Wheeler
2008-05-22 11:34 ` James Bottomley
2008-05-23 19:34 ` Sitsofe Wheeler
2008-05-23 19:34 ` Sitsofe Wheeler
2008-05-23 20:26 ` James Bottomley
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='g0p3gu$3gh$1@ger.gmane.org' \
--to=sitsofe@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.