[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#695169: linux-image-3.6-trunk-amd64: soft lockup in b43 under load



On Wed, 2012-12-05 at 13:20 +0100, Dominik George wrote:
> Hi,
> 
> > >     BUG: soft lockup - CPU#0 stuck for 22s! [irq-17:0002]
> > 
> > Please send the log messages that appear immediately after this.
> 
> There are no messages after this. The I/O part of the kernel goes into a 
> deadlock and the system becomes unresponsible. I can move the mouse and 
> click around in XFCE, but opening menues and everything that would require 
> disk access fails and freezes the process requesting it.
[...]
> I could not even trigger an emergency sync via SysRq. It just didn't 
> happen.
>
> Once the b43 driver goes into the freeze, the whoe kernel fails to do any 
> I/O.

It should be possible to get more log messages on the local console by
using 'sysctl kernel.printk=7'.

Also you could try using netconsole
<http://www.kernel.org/doc/Documentation/networking/netconsole.txt> or
serial console
<http://www.kernel.org/doc/Documentation/serial-console.txt> to capture
log messages remotely.

> I, personally, consider this as a risk of data loss.

If we counted every hang or crash as 'data loss' and therefore grave,
the severity system would then be completely useless and we could never
release the kernel again.  I think it's generally understood that you
can't consider data as 'saved' until the disk is sync'd.

Ben.

-- 
Ben Hutchings
Computers are not intelligent.	They only think they are.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: