Bug 53771
| Summary: | ath(9k) module reports beserk errors when not in use, related Oops | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Mark E. (mk) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | high | CC: | j, jirislaby, linville, mcgrof, shafi.wireless, sujith |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.7.6 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | syslog | ||
Which wireless card are you using ? Can you post the output of lspci ? It's build into the motherboard: Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) Subsystem: ASUSTeK Computer Inc. Device 850d Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f7c00000 (64-bit, non-prefetchable) [size=512K] Expansion ROM at f7c80000 [disabled] [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel The card was not in use when this was taken. Can you try with a recent kernel like 3.10-rc5 ? Various fixes for AR9485 have been merged recently. All apologies for the tardy reply. I'm now using a (hand rolled) 3.9.6 and the problem hasn't reoccurred, if that makes sense -- I believe the menu options for atheros wifi are different in that version. I spoke to soon, although apparently the problem is not as predictable now as it was when first reported. I'm going to switch to 3.10.1 today and will report back within the week. I just spend a while trying this with 3.10.1 and 3.9.6; it does not happen consistently on 3.9.6, but it does happen occasionally. It happens consistently on 3.10.1 as per steps 1) and 2) in the original report. However, the `df` related Oops does not happen. I did not manually alter the .config from 3.9.6 to 3.10.1. A patch has been posted: https://patchwork.kernel.org/patch/2846838/ |
Created attachment 93211 [details] syslog This seems to happen consistently when: 1) the wireless has been used, but then turned off and the interface taken down. 2) the system is subsequently suspended to ram When woken up, a backtrace appears in syslog immediately and then the message "ath: phy0: PLL4 meaurement not done", repeated endlessly many times per second. This will go on for hours if unnoticed and only stops when the ath9k module is removed. An example of this is in the top part of the attachment. I do not use the wireless much on this box, and after noticing this the first time I went back through my logs and it also occurred with my previous kernel, 3.6.2. After removing the ath9k module, the 'df' command "Failed" and an Oops appears in syslog whenever df is tried. An example of this is in the second part of the attachment.