2010/2/26 Nathan Schulte <[email protected]>: > I apologize for so many messages. I wanted to note that the reasoning > for lsmod only showing the ntfs module, is due the fact that ntfs (and > b43 and ssb) are the only drivers compiled as modules. > > When loading b43 without mmiotrace running, I receive a Fatal DMA > error: 0x800 within a few seconds. > I receive no other errors following, but I am unable to associate with > an access point. > If I then unload b43 and ssb, and reload it, I receive a Fatal DMA > error: 0x400 (and can generate one for every ifconfig wlan0 down/up I > perform). > > The archive http://vulcan.ist.unomaha.edu/~nmschulte/traces.tar.bz2 > contains two traces. The first trace (one) is after a cold boot, > loading b43, associating with an access point, issuing ifconfig wlan0 > down, ifconfig wlan0 up, and then stopping the trace. Immediately > after stopping the trace, I receive a 0x800 error in my logs. I then > unloaded b43 and ssb, and started a new mmiotrace (two). I then > loaded b43, issued ifconfig wlan0 down, ifconfig wlan0 up, and again > issued ifconfig wlan0 down/up (preceeded by trace markers denoting > such), and then stopped the trace. >
It is expected that you only get a single DMA error with 2.6.33, as the driver was modified in 2.6.33 to give up after a single failure. The controller restart mechanism has yet to show a successful error recovery for any card, OTOH the repeated retries had nasty side effects on some machines (including lockups and crashes), so the entire retry mechanism was removed. However, you did not do what I requested - before the 2nd mmiotrace, load and unload wl (the hybrid driver), not b43 - it is wl that appears to make the card work. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
