Pazartesi 10 Ocak 2011 gÃnà (saat 10:10:12) Hannes Reinecke ÅunlarÄ yazmÄÅtÄ: > On 01/07/2011 03:13 AM, Robby Workman wrote: > > On Thu, 6 Jan 2011 14:29:27 -0800 > > Greg KH <greg@xxxxxxxxx> 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. I've just had another report about random crashes (udev-165 on 2.6.37) which crash in ioread16_rep: http://img5.imagebanana.com/img/1ub7ghcy/DSCF5552.JPG --- Ozan ÃaÄlayan TUBITAK/UEKAE - Pardus Linux http://www.pardus.org.tr/eng -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
