From: Yuval Hager <yhager@yhager.com>
To: b43-dev@lists.infradead.org
Subject: System freezes with 2.6.33
Date: Sun, 2 May 2010 02:28:10 +0300 [thread overview]
Message-ID: <201005020228.11985.yhager@yhager.com> (raw)
In-Reply-To: <4BD0858D.7080903@lwfinger.net>
On Thursday 22 April 2010 20:21:17 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.
>
> 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.
>
> In Archlinux, how difficult is it to incorporate source from an external
> tree and build the kernel?
>
> Larry
I cannot recreate it with latest 2.6.33.3-1.
--yuval
next prev parent reply other threads:[~2010-05-01 23:28 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
2010-05-01 23:28 ` Yuval Hager [this message]
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=201005020228.11985.yhager@yhager.com \
--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