public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: yhager at yhager.com <yhager@yhager.com>
To: b43-dev@lists.infradead.org
Subject: System freezes with 2.6.33
Date: Thu, 22 Apr 2010 11:59:52 -0700	[thread overview]
Message-ID: <20100422185951.GA14078@happy.sfsu.edu> (raw)
In-Reply-To: <4BD0858D.7080903@lwfinger.net>

On 12:21 Thu 22 Apr     , Larry Finger wrote:
> On 04/22/2010 11:12 AM, yhager at yhager.com wrote:
> > I have tested the same kernel, with CONFIG_B43_FORCE_PIO=y. The
> > results are mostly the same. Full system freeze. Turning the radio off
> > avoids the freeze. Turning the radio on would not immediately freeze -
> > only when I tried to connect to a wireless network it did. 
> > I also enabled CONFIG_B43_DEBUG, but no messages on the console that
> > would testify a problem.
> 
> Is it possible for you to test with another mac80211-based wireless
> device? I cannot think of any possibility for the system to lock up when
> b43 is using PIO.

No, sorry, I don't have another device.

> 
> When the freeze occurs, how long do you leave it? There are some CPU
> lockups that take as many as 2 minutes to be recognized by the kernel.
> 

I haven't waited that long. I will test again when I have the chance.

> In Archlinux, how difficult is it to incorporate source from an external
> tree and build the kernel?
> 

Not difficult at all.

--y

  reply	other threads:[~2010-04-22 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  7:19 System freezes with 2.6.33 yhager at yhager.com
2010-04-18 16:16 ` Larry Finger
2010-04-20 14:34   ` yhager at yhager.com
2010-04-20 15:51     ` Peter Stuge
2010-04-20 16:07       ` Daniel Kuehn
2010-04-20 16:27         ` Peter Stuge
2010-04-20 17:07           ` Larry Finger
2010-04-22 16:12             ` yhager at yhager.com
2010-04-22 17:21               ` Larry Finger
2010-04-22 18:59                 ` yhager at yhager.com [this message]
2010-05-01 23:28                 ` Yuval Hager
2010-04-19 16:54 ` Peter Stuge

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=20100422185951.GA14078@happy.sfsu.edu \
    --to=yhager@yhager.com \
    --cc=b43-dev@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox