Comment 129 for bug 971809

Revision history for this message
In , gfmichaud (gfmichaud-linux-kernel-bugs) wrote :

So I have enabled
- full debugging in /etc/modprobe.d/ath9k.conf whith options ath9k debug=0xffff
- and kept all my workarounds (ANI, PM, hwcrypt disabled, BSSID set manually)

1) Booted and got network up
> DMESG_ALL_1.txt

2) Took the computer away from the AP and left for some time ; when I came back network was down
> DMESG_ALL_2.txt

3) Took the computer back closer to the AP and got network up again
> DMESG_ALL_3.txt

(As far as I am concerned, it used to work better with 3.8 and those workarounds than this custom 3.10 with the same workarounds.)

I hope the logfiles help understand what's happening.