Prev: [PATCH -next] block/xd.c: fix brace typo
Next: Linux IO scalability and pushing over million IOPS over software iSCSI?
From: Konrad Rzeszutek Wilk on 22 Jun 2010 12:20
> Ultimately, I was wondering if anyone might be able to take a look at
> my dmesg's that might have any idea as to what feature might be new in
> .26 that could be responsible for the panic. Sadly, it takes about 5
> hours to do a clean run of make-kpkg in debian on these machines, and
> I am not setup for distcc or cross compile on my x64 machine yet, so
> it is a painful experience to recompile over and over to try figure
> out what kernel feature it might be that is causing this.

It looks as the fdc driver is stuck in a loop and the init process never
gets pass this stage.

To see if that is the culprit, find the floppy.ko and rename it to say
floppy.ko.bak. Then recreate the initramfs.

The more worrying is the irqs firring. Try to use the 'irqpoll'
parameter as it suggests.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH -next] block/xd.c: fix brace typo
Next: Linux IO scalability and pushing over million IOPS over software iSCSI?