|
Sébastien BONNET wrote:
It looks like I need to apply this patch to the kernel,
http://lkml.org/lkml/2004/11/24/375 ... which has been included in the
kernel.org kernels.
... if your oops really is related to the bug report you've mentioned
before.
It is ! I had these kernels panics fixed using the mentionned patch
(attached), which is NOT in 2.6.10 (at least RH's 2.6.10)
Sorry, I'm not convinced. Care to explain how you can deduce from his
two line oops _and_ his description that he's seeing the same issue as
you were?
His partial kernel report:
Kernel panic: not syncing: fs/block_dev.c:396: spin_lock
(fs/block_dev.c:c035fc40) already locked by fs/block_dev.c/440
Note, I'm not saying that this patch should not be included, by all
means; all I'm asking for is hard facts and these are missing. Anyway,
RH will soon release a new RHEL update, which will make sure the
aforementioned patch is included. Upstream is already fixed.
Regards,
Roberto Nibali, ratz
--
-------------------------------------------------------------
addr://Kasinostrasse 30, CH-5001 Aarau tel://++41 62 823 9355
http://www.terreactive.com fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG Wir sichern Ihren Erfolg
-------------------------------------------------------------
|
