Subject: Re: What are the general causes of frozen system?
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <43891D97.4000404@lwfinger.net>
References: <43891D97.4000404@lwfinger.net>
Content-Type: text/plain
Date: Mon, 28 Nov 2005 08:11:51 +1100
Message-Id: <1133125912.7768.120.camel@gaston>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1332
Lines: 30

On Sat, 2005-11-26 at 20:44 -0600, Larry Finger wrote:
> I am trying to help the bcm43xx project develop a driver for the 
> Broadcom 43xx wireless chips, using my Linksys WPC54G card. 
> Unfortunately, since the group got far enough to turn on RX DMA, my 
> system has frozen whenever I load the driver. TX DMA was OK. It seems to 
> correlate with the receipt of a beacon from my AP, but that cannot be 
> proven. When the freeze happens, I cannot do anything more and have to 
> power the system off.
> 
> What should I consider as a cause of the freeze? I have reviewed the 
> code and do not find any obvious out-of-bounds memory references. I have 
> tried various 'printk' statements, but none of them in the bottom-half 
> interrupt routine make it to the logs. Are there any tricks that I 
> should try?

spinlock debugging is one... if it's a bad DMA to low memory, you can't
do much. Another common cause is a stale interrupt, is your IRQ handler
called over & over again in a loop ?

The problem is that depending on what you are interrupting, printk may
not work ...

Ben.


-
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/