Bug 832927 - Kernel bug in driver for Atheros Communications Inc. AR9485 Wireless Network Adapter
Kernel bug in driver for Atheros Communications Inc. AR9485 Wireless Network ...
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
: 835213 835785 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2012-06-18 04:29 EDT by Herald van der Breggen
Modified: 2012-07-11 10:04 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-07-07 17:54:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot of console with crash report (5.76 MB, image/jpeg)
2012-06-18 04:29 EDT, Herald van der Breggen
no flags Details

  None (edit)
Description Herald van der Breggen 2012-06-18 04:29:24 EDT
Created attachment 592560 [details]
screenshot of console with crash report

Description of problem:
Kernel bug in driver for "Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)". The wireless connection looks healthy/operational until the crash.

Version-Release number of selected component (if applicable):

How reproducible:
Use wireless connection. A kernel crash can happen after 10 seconds but also after one hour. It is unpredictable.

Steps to Reproduce:
1. use wireless connection with the Atheros AR9485
Actual results:
kernel crash. Black console screen appears.
I have seen about 10 of them, and all are a bit different. The most clear one was the one I attached, starting with:

Kernel bug at drivers/net/wireless/ath/ath9k/recv.c:671!
invalid opcode: 0000 [#1] SMP

Expected results:

Additional info:
Comment 1 John W. Linville 2012-06-18 15:06:21 EDT
Line number matches BUG_ON in ath_edma_get_buffers...

        bf = SKB_CB_ATHBUF(skb);
Comment 2 Mohammed Shafi 2012-06-21 02:13:04 EDT
(In reply to comment #1)
> Line number matches BUG_ON in ath_edma_get_buffers...
>         bf = SKB_CB_ATHBUF(skb);
>         BUG_ON(!bf);

thanks John, we shall try to recreate/do code analysis
Comment 3 Gianluca Busiello 2012-06-24 20:33:59 EDT
I have an Asus Zenbook UX21 and I have exactly the same problem. I'm running kernel 3.4.3-1 and I get a kernel panic after a few minutes the wireless is on.
Curiously, running the live version of Fedora17 with kernel 3.3.4-5 the kernel panic doesn't happen.

I've recomiled the kernel and activated all the debug options for ath9k driver. If I can help to diagnose, please let me know.
Comment 4 Dirk Maaß 2012-06-25 14:55:43 EDT
I experience the same behavior with my new Asus G55V and kernel 3.4.3-1.fc17.x86_64. Let me know how I can help tracking down the problem. 

I can reproduce it easily because the kernel panic happens after few seconds of traffic on the wireless connection.

Comment 5 Jeffrey Selk 2012-06-26 23:19:31 EDT
I can confirm this behavior on Fedora 17 x64 3.4.3-1 running on an Asus UX31E.

crash output:

     KERNEL: /usr/lib/debug/lib/modules/3.4.3-1.fc17.x86_64/vmlinux
    DUMPFILE: /var/spool/abrt/vmcore-26.06.12-19:49:38/vmcore  [PARTIAL DUMP]
        CPUS: 4
        DATE: Tue Jun 26 19:49:35 2012
      UPTIME: 00:03:51
LOAD AVERAGE: 0.65, 0.32, 0.13
       TASKS: 276
    NODENAME: asuslaptop
     RELEASE: 3.4.3-1.fc17.x86_64
     VERSION: #1 SMP Mon Jun 18 19:53:17 UTC 2012
     MACHINE: x86_64  (1696 Mhz)
      MEMORY: 3.9 GB
       PANIC: "[  230.851508] kernel BUG at drivers/net/wireless/ath/ath9k/recv.c:671!"
         PID: 0
     COMMAND: "swapper/0"
        TASK: ffffffff81c13020  (1 of 4)  [THREAD_INFO: ffffffff81c00000]
         CPU: 0

I can provide vmcore (44mb) upon request.
Comment 6 Jeffrey Selk 2012-06-26 23:23:26 EDT
Also, bug does not appear to be occurring on 3.3.4-5.fc17.x86_64. I can consistency reproduce this bug on any kernel >3.4.x by kicking off a large network traffic task (i.e. transferring media over LAN or WAN; usually occurs after 100mb or so).
Comment 7 Mohammed Shafi 2012-06-28 01:05:55 EDT
Hi John and all,

a recent fix in the rx path for panic
Comment 8 John W. Linville 2012-06-28 13:13:33 EDT
Test kernels w/ the above mentioned patch are building here:


When they finish building, please give them a try and post the results here...thanks!
Comment 9 Herald van der Breggen 2012-06-28 14:53:15 EDT
I just rebooted the new kernel and copied a 500MB file around a few times to different locations and different protocols (ssh, nfs) over wifi. No problems found, so to me this looks like the sulotion. Many thanks!
Comment 10 Herald van der Breggen 2012-06-28 14:55:53 EDT
(I was talking about 3.4.4-3.bz832927.1.fc17.x86_64)
Comment 11 Dirk Maaß 2012-06-28 16:55:05 EDT
I can confirm that with 3.4.4-3.bz832927.1.fc17.x86_64 everything seems OK. I just copied two bigger files (1.5GB,2GB) and afterwards concurrently (in/out) using sftp. Thank you very much!!
Comment 12 John W. Linville 2012-06-29 10:40:20 EDT
*** Bug 835213 has been marked as a duplicate of this bug. ***
Comment 13 John W. Linville 2012-06-29 10:57:44 EDT
I have added that patch to the f17 builds.
Comment 14 Stanislaw Gruszka 2012-07-02 03:08:26 EDT
*** Bug 835785 has been marked as a duplicate of this bug. ***
Comment 15 Pascal Dupuis 2012-07-02 17:19:19 EDT
Damnit, got an occurence with kernel vmlinuz-3.4.4-3.fc17.x86_64

Call trace:
ath_rx_tasklet/0x165/0x1b00 => unable to handle NULL pointer derefence

the mentionned routines have increasing time, the first being ath9k_ioread32, the latest being ath_rx_tasklet

It occured after around two hours of use, playing music on youtube and other web browsing.

I used kernel vmlinuz-3.4.4-3.bz832927.1.fc17.x86_64 for longer time without this issue.
Comment 16 John W. Linville 2012-07-02 17:29:44 EDT
3.4.4-3.fc17 does _not_ have the fix...
Comment 17 William Bader 2012-07-03 19:47:51 EDT
I get this panic on a Sony Vaio laptop with 3.4.4-3.fc17.x86_64.
lspci shows "02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)" and the text mode panic screen mentions ath_rx_tasklet.
It looks like the fix was made on June 28.
When will it be published where "yum update" can find it?
Comment 18 Wesley Hampton 2012-07-04 09:09:22 EDT
I also used kernel-3.4.4-3.bz832927.1.fc17.x86_64.rpm and have not had an ath9k kernel panic since.  The wireless card I have installed is a TP-Link TL-WDN4800 and the lspci output for me is: "03:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01)" on an Intel DG45ID Motherboard.

Prior, I was on kernel 3.4.4-3.fc17.x86_64 and was crashing within seconds of firing up a browser, Skype or YUM Updates.

Thank you very much for patching this problem, it is MUCH appreciated!

Out of the same curiosity as William Bader above, when do special patches like this find their way into mainstream YUM Updates?

Thanks again!

Comment 19 Fedora Update System 2012-07-05 17:55:34 EDT
kernel-3.4.4-5.fc17 has been submitted as an update for Fedora 17.
Comment 20 Fedora Update System 2012-07-05 19:49:57 EDT
kernel-3.4.4-4.fc16 has been submitted as an update for Fedora 16.
Comment 21 Fedora Update System 2012-07-06 17:23:26 EDT
Package kernel-3.4.4-4.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.4.4-4.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Comment 22 Dirk Maaß 2012-07-06 17:37:43 EDT
kernel-3.4.4-5.fc17 works like a charm.
imho, this bug seems fixed.
many thanks!
Comment 23 Fedora Update System 2012-07-07 17:54:09 EDT
kernel-3.4.4-5.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 24 Fedora Update System 2012-07-08 16:51:09 EDT
kernel-3.4.4-4.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 25 William Bader 2012-07-08 19:25:10 EDT
Thanks! I have been running 3.4.4-5.fc17.x86_64 for several hours without a crash.
Comment 26 Jay Guerette 2012-07-10 20:55:58 EDT
Still getting panics. I have to convince my wife not to simply reboot so I can capture a call trace. Should I open a new bug, or can this one be re-opened?
Comment 27 John W. Linville 2012-07-11 10:04:17 EDT
To avoid confusion, please open a new bug with the backtrace information.

Note You need to log in before you can comment on or make changes to this bug.