On Wed, 18 Nov 2009 14:42:51 -0500, Bob Copeland <m...@bobcopeland.com>
wrote:
> Ok, fair enough. We should try to figure out where the 0x5d and 0x43
> come from. It could be memory corruption, for example, but 0x5d and
> 0x43 aren't poison values. You may try turning on slub/slab debugging
> just to be sure.
>
> Does this happen frequently enough that you'd be able to capture some
> packets before it happens? Something like:
>
> $ sudo su
> # iw dev wlan0 interface add monitor wlan0.mon
> # ifconfig wlan0.mon up
> # wireshark -i wlan0.mon &
> # iw dev wlan0 scan
I did that, but as i am no expert in wireshark, i just attached the
complete log. i see three "MA-WLAN" APs (:43, :48, :5d). Hope this helps.
Kind regards
Florian
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
