Re: Dianogsing a hard lockup

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

 



Hi list,

>> some time after I load drivers (any, rt2500 or via ndiswrap) for a 
>> rt2500-based wlan card, the box locks up hard. Sysrq does not work, so I 
>> suppose it is during irq-disabled context. How could I find out where this 
>> happens?
>
>First, stick to rt2500 as you won't get help with binary only drivers
>here.
>Check the driver code & make sure it can't get stuck looping in the
>interrupt handler due to an unhandled IRQ.  Add printks.

It happens with both, and that's why I think this is not a problem
with the rt2500 driver(s), but somewhere else in the kernel. But I do
not know where, because it is a lot bigger than the rt code base.

>Try to reproduce the problem from the console, you're more likely to get
>a usable Oops.
>
I did, it just locks. No reaction to Sysrq+T/+P, which is the "hard"
in "hard lockup".



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux