this suspicion that the lockup happens in the rf off code is a good start. i am experiencing it when i leave atk9k unassociated on network manager and am connected w/ cat5 (which makes no difference). after some time there appears the [phy0] process w/ 100% CPU load again and again with some pauses in between of approx 2 - 3 minutes.
i am fixing it everytime with rmmod ath9k as long as i am not connected and/or dont want to be connected through wlan. On Sun, 5 Jun 2011 14:11:30 +0100 Tony Houghton <h...@realh.co.uk> wrote: > On Sun, 5 Jun 2011 07:30:34 -0400 > Camilo Mesias <cam...@mesias.co.uk> wrote: > > > I have a suspicion the lockup happens in the rf off code, because I > > can cause the lockup reliably simply with iwconfig wlan0 tx off > > Can other people confirm this? Is it worth putting more defensive > > code in that function? > > This is what I found (I forgot to use Reply To All so I only sent this > to Mohammed Shafi before): > > : The freeze is in ath9k_hw_set_power_awake during the for() loop > when it : calls > : REG_SET_BIT(ah, AR_RTC_FORCE_WAKE, AR_RTC_FORCE_WAKE_EN); > > That could be wrong because I used printk to track it down and there > may be a race condition between the crash and the messages appearing > on the console. > > I also discovered that > val = REG_READ(ah, AR_RTC_STATUS) & AR_RTC_STATUS_M; > had a result of 15, but the status should only have one bit set at a > time I think? > > I also wondered why it was trying to go into a wake state when it was > supposed to be shutting down. > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- Lars Schotte @ Hana (F14) _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
