lkml.org 
[lkml]   [2005]   [Dec]   [18]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSun, 18 Dec 2005 16:42:55 +0100 (MET)
FromJan Engelhardt <>
SubjectRe: Dianogsing a hard lockup
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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-12-18 15:46    [W:9.437 / U:0.050 seconds]
©2003-2008 Jasper Spaans