From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Early-boot kernel panics from udev-165/extras/ata_id/ata_id.c
Date: Mon, 10 Jan 2011 08:10:12 +0000 [thread overview]
Message-ID: <4D2ABEE4.6040408@suse.de> (raw)
In-Reply-To: <4D263BF6.6050305@verizon.net>
On 01/07/2011 03:13 AM, Robby Workman wrote:
> On Thu, 6 Jan 2011 14:29:27 -0800
> Greg KH <greg@kroah.com> wrote:
>
>> On Thu, Jan 06, 2011 at 05:02:30PM -0500, John Stanley wrote:
>>> Hello,
>>> There is a problem in udev-165/extras/ata_id/ata_id.c resulting in
>>> random early boot kernel panics. As it stands, udev-165 is not
>>> usable because the boot panics occur to frequently. The systems are
>>> GNU/Linux i686 with linux-2.6.36.2 and linux-2.6.37, gcc-4.5.1, and
>>> glibc-2.12.1.
>>
>> What is the kernel oops message? That should be fixed first, no
>> userspace code should be able to crash the kernel.
>
>
> Hi Greg,
>
> First, sorry for not posting something about this sooner - I'd
> pinged Kay on IRC about it, and I *promise* I had planned to
> forward it to the scsi/ati guys, but work has been hell this
> week. Anyway, here's the initial report we got about it, along
> with a lot of debugging by other folks (including the OP, who
> I think is 'resonance' in that thread):
> http://www.linuxquestions.org/questions/slackware-14/current-randomly-timed-kernel-oops-on-bootup-of-two-test-boxen-852843/
>
It's all Tejun's fault.
kernel crashing in ata_sff_data_xfer / ioread32 ...
Looks like we're trying a read to a page which wasn't
mapped/allocated properly.
And yes, it definitely should be fixed in the kernel first.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2011-01-10 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 22:02 Early-boot kernel panics from udev-165/extras/ata_id/ata_id.c John Stanley
2011-01-06 22:29 ` Greg KH
2011-01-07 2:13 ` Robby Workman
2011-01-07 8:06 ` Ozan Çağlayan
2011-01-10 8:10 ` Hannes Reinecke [this message]
2011-01-10 11:35 ` Ozan Çağlayan
2011-01-11 13:25 ` Tejun Heo
2011-01-17 3:53 ` John Stanley
2011-01-17 4:03 ` John Stanley
2011-01-17 5:07 ` John Stanley
2011-01-17 15:27 ` Tejun Heo
2011-01-17 15:28 ` Tejun Heo
2011-01-18 3:38 ` John Stanley
2011-01-18 15:09 ` Tejun Heo
2011-01-18 21:48 ` John Stanley
2011-01-19 2:07 ` Brad Price
2011-01-19 20:20 ` John Stanley
2011-01-20 12:59 ` [PATCH #upstream-fixes] libata: set queue DMA alignment to sector Tejun Heo
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=4D2ABEE4.6040408@suse.de \
--to=hare@suse.de \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).