[PATCH stable] b43: Work around mac80211 race condition

2009-11-15 Thread Michael Buesch
commit 18c6951091eca7645005a71b556106cc99a6f4b1 Author: Larry Finger larry.fin...@lwfinger.net Date: Wed Jul 29 10:54:06 2009 -0500 b43: Work around mac80211 race condition As shown in http://thread.gmane.org/gmane.linux.kernel.wireless.general/36497, mac80211 has a bug that

Re: b43 kills my kernel

2009-11-15 Thread Michael Buesch
On Saturday 14 November 2009 21:20:28 Michael Buesch wrote: Yeah, ok. That doesn't seem to be a bug in b43 then. It's the CRDA subsystem waiting for a userspace daemon. But it won't finish waiting, because userspace is not running, yet. I guess running cfg80211 as module is an acceptable

Re: b43 fatal DMA errors

2009-11-15 Thread Chris Vine
On Sun, 15 Nov 2009 15:42:25 -0800 (PST) Linus Torvalds torva...@linux-foundation.org wrote: On Sun, 25 Oct 2009, Chris Vine wrote: And Chris, just out of interest - does FORCE_PIO work for you too? Yes. So I've been trying to debug this, but no real luck. The Broadcom official

Re: b43 kills my kernel

2009-11-15 Thread Oncaphillis
On 11/15/2009 03:40 PM, Michael Buesch wrote: On Saturday 14 November 2009 21:20:28 Michael Buesch wrote: Yeah, ok. That doesn't seem to be a bug in b43 then. It's the CRDA subsystem waiting for a userspace daemon. But it won't finish waiting, because userspace is not running, yet. I guess

Re: b43-phy0 ERROR: Fatal DMA error: 0x00000400

2009-11-15 Thread Peter Stuge
Larry Finger wrote: merely triggered by some interaction with ACPI and/or the BIOS. From what I found in looking back through the DMA error reports, most (if not all) people with the problem have netbook computers with Intel ATOM processors. Gábor Stefanik wrote: Linus has also reported this

Re: b43 kills my kernel

2009-11-15 Thread Peter Stuge
Oncaphillis wrote: I poked around in the sbb code and found that ssb_do_read never returns: snip static int sprom_do_read(struct ssb_bus *bus, u16 *sprom) You wrote ssb_do_read above, this is sprom_do_read. Maybe they call each other? So I guess the mmio address is wrong. It is set to