Bug 832927

Line number matches BUG_ON in ath_edma_get_buffers...

        bf = SKB_CB_ATHBUF(skb);
        BUG_ON(!bf);

(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

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.
Thanks.

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.

Thanks

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
       STATE: TASK_RUNNING (PANIC)

I can provide vmcore (44mb) upon request.

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).

Hi John and all,

a recent fix in the rx path for panic
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/93723

Test kernels w/ the above mentioned patch are building here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=4206016

When they finish building, please give them a try and post the results here...thanks!

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!

(I was talking about 3.4.4-3.bz832927.1.fc17.x86_64)

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!!

*** Bug 835213 has been marked as a duplicate of this bug. ***

I have added that patch to the f17 builds.

*** Bug 835785 has been marked as a duplicate of this bug. ***

Damnit, got an occurence with kernel vmlinuz-3.4.4-3.fc17.x86_64

Call trace:
ath9k_ioread32+0x34/0x90
ath9k_tasklet+0xdx/0x160
__do_softirq
native_sched_clock
call_softirq
do_softirq
irq_exit
do_IRQ
common_interrupt
<EOI>
sysret_audit
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.

3.4.4-3.fc17 does _not_ have the fix...

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?
William

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!

Wes

kernel-3.4.4-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/kernel-3.4.4-5.fc17

kernel-3.4.4-4.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/kernel-3.4.4-4.fc16

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:
https://admin.fedoraproject.org/updates/FEDORA-2012-10319/kernel-3.4.4-4.fc16
then log in and leave karma (feedback).

kernel-3.4.4-5.fc17 works like a charm.
imho, this bug seems fixed.
many thanks!
dirk

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.

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.

Thanks! I have been running 3.4.4-5.fc17.x86_64 for several hours without a crash.

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?

To avoid confusion, please open a new bug with the backtrace information.