RE: Dianogsing a hard lockup

["Roger Heflin" <rheflin@atipa.com>]

 

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Lee Revell
> Sent: Saturday, December 17, 2005 12:41 PM
> To: Jan Engelhardt
> Cc: Linux Kernel Mailing List
> Subject: Re: Dianogsing a hard lockup
> 
> On Sat, 2005-12-17 at 17:09 +0100, Jan Engelhardt wrote:
> > 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.
> 
> Try to reproduce the problem from the console, you're more 
> likely to get a usable Oops.
> 
> Check the driver code & make sure it can't get stuck looping 
> in the interrupt handler due to an unhandled IRQ.  Add printks.
> 
> Finally report it to the rt2500 maintainer.

Jan,

I got the rt2500usb driver to blow up nicely if I used the
default ieee* routines from the kernel and not the ones that
came with the rt2500 drivers, you might want to verify which
ieee* that you are using.  Using the ones that came with the
rt2500 seem to work, or at least not crash the kernel out.

                          Roger