-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Kernel Panic on 4.14.x with Atheros AR9271 #2307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I know these cards work (only up to two, the third only works with nothing else accessing the usb bus, i.e. with ethernet plugged in it doesn't work anymore) with kernels 4.9.28 and 4.9.35 included in Raspian 2017-06-21 and 2017-07-05, maybe that narrows it down a little for you. Another thing I noticed is, they don't like to be switched into promiscous mode, sometimes they just stop working then (but the system stays running), I'd try not doing that (in monitor mode, all frames are forwarded to userspace anyway, promisc mode is not needed). |
I already discovered the "2 card's only" problem, it's also present on my Linux Mint System, I guess that's a firmware thing :) I don't use promiscous mode and in my case the system totally crashes. It happens completely random, sometimes a few hours, sometimes 1-3 days. The RasPi does nothing other than collecting probe requests, so it doesn't even do some TX, boots straight into a python script. |
Still happening with newest Kernel 4.14. and Firmware (there were some updates lately).
|
Hmm. Does the dongle work fine when used as a simple Wifi adaptor? I'd suggest the linux-wireless mailing list might be a better place to get Atheros specific support. |
In fact, it's not only one adapter. I have 3 of them from different brands. They all show the same problem. What's really interesting: If you plug in 2 adapters, the kernel module/driver can crash independently, leaving one still working while the other is not. If I let it run long enough, the other one will crash too, resulting in a complete freeze of the RasPi. Sometimes even with colorful graphic glitches on the screen. Never really tried using them as a Client for a longer period because the RasPi is hardwired. |
Are all the adapters using the same chipset, even though different brands? Colourful graphic glitches during the crash almost certainly means a buffer overrun/random memory writes. Something wrong with the driver. Unfortunately we cannot generally support any old random chipset drivers - it's time consuming enough just supporting the ones built in to the Pi's! If I can find one with the chipset (name some makes) I might have time to take a look, but cannot promise anything. |
The Chipset is neither very old nor random. They all use Atheros AR9271 chipset. they are the most common insisde 150 Mbit 2.4 GHz adapters. I use TP-LINK TL-WN722N (only v1 has Atheros, v2 has Realtek), ALFA Network AWUS036NHA and Sophos AP5 |
Have you tried using them through a powered USB hub? |
I'm Always using an powered USB Hub. In this Case a Ugreen 4 Port powered by a Huawei USB charger. |
Sorry, "any old" is a English turn of phrase, I don't actually mean old, just any arbitrary chipset. There are frequent updates to the atheros drivers in the linux wireless mailing list. Whether they apply to these at all I do not know. Might be worth keeping an eye out there to see if there is anything that might help with your problem. |
I'm also having this problem on a Pi Zero.
|
I have this problem on Manjaro. This computer has a wired connection so wifi isn't used. The wifi was turned on so it was constantly browsing available access points for the week it's up. dmesg is spammed with 'link is not ready' messages. Now I have Cinnamon disable the wifi so no more spamming dmesg.
|
I switched from Atheros to Ralink, problem is gone. So it's def. a firmware/driver problem. |
I think you should try Linux 4.16 (using mainline instead of the foundation kernel would be the best) and if the issue still occurs report it to linux-wireless mailing list. |
I ran Manjaro on 4.16 for a week with Atheros disabled and everything was fine. I ran it another week with Atheros enabled but not connected. There was no 'cut here' message but the GUI was sluggish, same freezing browsers problem as had been happening with 4.9 and 4.14. Seems that it has been improved enough to eliminate the 'cut here' message but the problem has not been fixed. Turns out an Intel Wifi browsing all week also causes sluggish response. That means that the Atheros driver has been fixed and the sluggish response is elsewhere in the wifi stack. |
It looks like the 4.16 kernel fixes this. I doubt we will backport but if anyone can point to the change that fixes it, we might be able to cherry-pick. This issue will be closed within 30 days unless further interactions are posted. If you wish this issue to remain open, please add a comment. A closed issue may be reopened if requested. |
Closing due to lack of activity. Please request to be reopened if you feel this issue is still relevant. |
Hello, I'm experiencing the same issue with a Raspberry Pi 3 B+ using a very common Atheros USB card ( ALFA AWUS036NHA ). [11274.305757] ------------[ cut here ]------------ Any suggestion? |
Hi,
I have 2 Atheros AR9271 which I use in monitor mode. I get regular kernel panic's on stretch stock and latest hexxeh kernels. Sadly there are no entrys in syslog, so I had to take a photo of my screen:
The text was updated successfully, but these errors were encountered: