Red Hat Bugzilla – Bug 474185
MacBooks ath9k throws many kernel oops while connected.
Last modified: 2009-04-14 13:51:22 EDT
Created attachment 325395 [details]
Description of problem:
When connecting to some unsecured wireless network using a MacBook, the ath9k drivers throws kernel oops every 10min.
Version-Release number of selected component (if applicable):
Appeard with Fedora 10, there was no ath9k in Fedora 9.
Every time connected to an unsecured wireless network.
Steps to Reproduce:
1. Use NM to connect to a wireless network.
2. Use your connection by browsing and reading mails.
3. Wait for a couple of minutes (2-10min)
A small popup tells you that a kernel oops appeard and was reported.
NetworkManager might stall and reconnect.
Smooth internet connection.
dmesg, lspci attached.
Created attachment 325396 [details]
Could you try a recent rawhide kernel? Does it behave similarly? Please include the actual kernel version you try.
Btw. Seems as if it's worse with Cisco APs. My WRT54g works fine.
# uname -a
Linux proprietary.local 2.6.29-0.43.rc2.git1.fc11.i686 #1 SMP Mon Jan 19 01:59:56 EST 2009 i686 i686 i386 GNU/Linux
# rpm -qa | grep kernel
It behaves differently.
It seems as if the signal strength is much better, but I still get a lot of AP reassociations (following dmesg) and the connection is not stable.
Created attachment 329496 [details]
Second dmesg with 2.6.29-0.43.rc2.git1.fc11.i686
Mainly note the wlan associate-disassociating-orgies.
Your disassoc-assoc issues (which are the origin of this bug report) are unrelated to your disasoc/assoc issues. Your diassoc/assoc issues could be related to interoperability issues or issues with your AP's signal, most likely the first.
Can this bug report be merged with bug 488437.
Yes. After some daily experiences it seems to be some interop issues with Cisco APs.
I can't really tell what happens in bug #488437, but if you suggest it I can just support it :)
Sorry what I meant to say was that your assoc/disassoc issues are unrelated to the origins of this bug report which is a WARNING.
For the issues with your Cisco AP please try out wireless-testing or compat-wireless and if you see an issue open up a bug report.
Guide on how to get wirelss-testing:
You can also just use compat-wireless:
Sorry actually if you do see an issue with the latest ath9k (on wireless-testing or through compat-wireless) with your Cisco AP the best way to help debug the issue is to disable netwok manager and pkill wpa_supplicant and then run things manually. Also since you would be using the latest and greatest you can simply report issues using the ath9k mailing list.
When reporting your issue to the ath9k mailing list please be sure to report exactly the model of your AP and your AP configuration settings.
It sounds like this bug is resolved? I'm closing on the basis of the last several comments.