Luis R. Rodriguez a écrit : > On Mon, Jan 18, 2010 at 06:31:19PM -0800, Peter Stuge wrote: > >> Today when I came home and resumed my system I got these messages >> from the driver: >> >> [302214.156400] phy1: device no longer idle - scanning >> [302214.341494] ath: ath_isr status=00000009 imask=f4001071 wecare=00000001 >> [302214.341983] ath: ath_isr status=01000009 imask=f4001071 wecare=00000001 >> [302214.345578] ath: ath_isr status=20000008 imask=f4001071 wecare=20000000 >> [302214.359875] ath: Failed to stop TX DMA in 100 msec after killing last >> frame >> [302214.359900] ath: Unable to stop TxDMA. Reset HAL! >> [302214.364010] phy1: device now idle >> >> I didn't save messages from the suspend. (And, those ath_isr messages >> were added by me to aid debugging the disconnect issue.) >> >> I unloaded and reloaded the driver and could connect again. >> >> (A few hours later I was disconnected as per my previous thread. Oh, >> and a friend with a 92xx generation ath9k also experiences similar >> disconnect issues under a little load. But that's another thread.) >> > > What kernel? You should try to use the latest stable. At this point that is > the 2.6.32 kernel release, if you want to stick to an older kernel you can use > compat-wireless: > > http://wireless.kernel.org/en/users/Download/stable/ > > Luis > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > > I am seeing this as well on 2.6.33-rc4-wl, but only at unload time (modprobe -r ath9k).
Regards, Benoit _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
