Pavel Roskin wrote: > On Mon, 2008-04-14 at 20:01 +0100, Daniel wrote: > >> I'm back using Linux on this laptop (HP Compaq Presario C742N) and have >> such upgraded Kernel and b43. I was getting very unreliable(almost none) >> with 2.6.24 so I have jumped to 2.6.25-rc8. So with this version it >> works for a period, then it bails. I tend to notice more of a bail if >> running rtorrent or something generating lots of connections. Thruput is >> fine though, I can still download at my ADSL connections max if just >> downloading with wget or similar. >> >> Here is some debugging info, please let me know if I haven't provided >> enough: > > It may be interesting if you are using an open connection, WEP or WPA.
I am using a WPA2/AES+PSK based network. Where the AP is located approx 15ft away. This device when running under Mac OSX runs perfectly fine. ( I haven't tested Windows. > >> ##### Everthing worked fine for a few minutes here... Then :0! >> wlan0: wrong buffer size > > The message is from ieee80211_rx_h_amsdu() in net/mac80211/rx.c, but I > cannot see it it's the first or the second message. The second message > has a space at the end, but it could have been lost. Maybe you could > change the second message slightly, so that we know which error triggers > it? Ah, the second well only this that came after was <6> (sometimes <7>) and this confused me as it didn't appear immediately, just the next time I checked dmesg. (I actually thought it was some outer glitch as it appeared right after the "size") > It any case, "wrong buffer size" doesn't seem to be considered a major > problem, which is indicated by the fact that it's printed with the > lowest priority, KERNEL_DEBUG. Ah ok, so I guess that isn't enough! > > Maybe you should describe what you see after it happens, the output of > iwconfig and ifconfig. Try reconnecting to the AP. Look for more > kernel messages. I haven't noticed any more kernel messages so far, and I have re-compiled the b43 module with the DEBUG flag. Next time it reproduces I'll get some more info from the cli tools. Normally in order to re-associate with the AP I issue the following: /etc/init.d/net.wlan0 stop && modprobe -rv b43 && sleep 1 && modprobe -v b43 && /etc/init.d/net.wlan0 start And it re-associates quickly. If I don't unload the driver and reload, there is not a chance to get it to re-associate. Cheers, Dan. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
