From: Michael Buesch <mb@bu3sch.de>
To: Doug McLain <doug@nostar.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problems with b43 using BCM4306 r3
Date: Mon, 10 Dec 2007 22:58:29 +0100 [thread overview]
Message-ID: <200712102258.29802.mb@bu3sch.de> (raw)
In-Reply-To: <475DA27F.2040004@nostar.net>
On Monday 10 December 2007 21:33:03 Doug McLain wrote:
> I have an emachines M6805 with the BCM4306 r3 wifi chip. Using the
> ndiswrapper driver, all is ok, but using the b43 driver results in
> constant flow of dmesg output (see link), eventual lockup of wifi under
> heavy network traffic, and constant xruns when using JACK audio server.
> Again, when I use the ndiswrapper driver, everything works ok.
>
> http://nostar.net/ardour/dmesg.txt
That's weird. These messages say that interrupts are not disabled in
the IRQ handler. Which driver are you using? Please try vanilla
wireless-2.6.
--
Greetings Michael.
next prev parent reply other threads:[~2007-12-10 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 20:33 Problems with b43 using BCM4306 r3 Doug McLain
2007-12-10 21:58 ` Michael Buesch [this message]
2007-12-12 0:08 ` doug
2007-12-12 0:22 ` Michael Buesch
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=200712102258.29802.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=doug@nostar.net \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).