From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robby Workman <rw@rlworkman.net>
Date: Fri, 07 Jan 2011 02:13:27 +0000
Subject: Re: Early-boot kernel panics from udev-165/extras/ata_id/ata_id.c
Message-Id: <20110106201327.4020ab64@liberty>
List-Id: <linux-hotplug.vger.kernel.org>
References: <4D263BF6.6050305@verizon.net>
In-Reply-To: <4D263BF6.6050305@verizon.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

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/

-RW