[Bug 432353] Re: ath5k: phy0: failed to wakeup the MAC Chip

[amichair]

Kubuntu Netbook Remix 10.04 on an Acer Aspire One ZG5 (a.k.a. AOA150)

Linux ubuntu 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC
2010 i686 GNU/Linux

This happens very consistently: netbook boots up, wireless connects (via
network-manager-kde), I run rsync on the netbook to copy several GB from
a remote machine to the netbook, and within a couple of minutes (a few
hundreds of MB transferred), the wireless dies, with the log below.

Interestingly, once wireless freezes, not even a reboot brings it back
(even rebooting into winxp!), only a full shutdown, waiting a few
seconds, and powering back up. There is no hibernation/suspend involved
- this is on a fresh boot within a few minutes of startup, doing nothing
but copying files over wireless. Also, in winxp there is no problem
ever, so it's not the hardware itself.

This bug makes wireless on the netbook hardly usable (requires power
cycle every couple of minutes).


[  226.409020] CE: hpet increasing min_delta_ns to 15000 nsec
[  233.454922] ath5k phy0: failed to wakeup the MAC Chip
[  233.454935] ath5k phy0: can't reset hardware (-5)
[  238.316136] No probe response from AP <address goes here> after 500ms, disconnecting.
[  238.651369] ath5k phy0: failed to wakeup the MAC Chip
[  238.651388] ath5k phy0: can't reset hardware (-5)
[  238.697655] ath5k phy0: failed to wakeup the MAC Chip
[  238.697674] ath5k phy0: can't reset hardware (-5)
[  238.744031] ath5k phy0: failed to wakeup the MAC Chip
[  238.744055] ath5k phy0: can't reset hardware (-5)
[  238.790191] ath5k phy0: failed to wakeup the MAC Chip
[  238.790202] ath5k phy0: can't reset hardware (-5)
[  238.836517] ath5k phy0: failed to wakeup the MAC Chip
[  238.836537] ath5k phy0: can't reset hardware (-5)
[  244.390333] __ratelimit: 18 callbacks suppressed
[  244.390347] ath5k phy0: failed to wakeup the MAC Chip
... 
<and so on repeatedly>

-- 
ath5k: phy0: failed to wakeup the MAC Chip
https://bugs.launchpad.net/bugs/432353
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.