All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What are the general causes of frozen system?
Date: Mon, 28 Nov 2005 08:11:51 +1100	[thread overview]
Message-ID: <1133125912.7768.120.camel@gaston> (raw)
In-Reply-To: <43891D97.4000404@lwfinger.net>

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.



      parent reply	other threads:[~2005-11-27 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27  2:44 What are the general causes of frozen system? Larry Finger
2005-11-27  2:52 ` thockin
2005-11-27  3:05   ` Larry Finger
     [not found]     ` <20051127031115.GA31651@hockin.org>
2005-11-28  5:01       ` Larry Finger
2005-11-27 10:59 ` Michael Buesch
2005-11-27 21:11 ` Benjamin Herrenschmidt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1133125912.7768.120.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.