#1863: spin_lock caused by ath_pci freezing my server on a daily basis
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: madwifi: driver | Version: v0.9.4
Resolution: | Keywords: ath_pci spin_lock
soft_lock
Patch_attached: 0 |
--------------------------------------+-------------------------------------
Old description:
> I've had a netgear wireless pci card in my server providing local
> wireless services for several months, then the other day I rebooted the
> server and since then it's been hanging almost every day. I upgraded the
> kernel and madwifi modules to no affect. I think there must be another
> party making some kind of call that is specifically incompatible with the
> madwifi driver but I'm not sure how to find it. I'm at a loss.
>
> this is the dmesg of the driver loading:
>
> ath_hal: module license 'Proprietary' taints kernel.
> ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,
> RF5413)
> wlan: 0.9.4
> ath_pci: 0.9.4
> ath_rate_sample: 1.2 (0.9.4)
> wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
> 24Mbps 36Mbps 48Mbps 54Mbps
> wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> wifi0: H/W encryption support: WEP AES AES_CCM TKIP
> wifi0: mac 7.9 phy 4.5 radio 5.6
> wifi0: Use hw queue 1 for WME_AC_BE traffic
> wifi0: Use hw queue 0 for WME_AC_BK traffic
> wifi0: Use hw queue 2 for WME_AC_VI traffic
> wifi0: Use hw queue 3 for WME_AC_VO traffic
> wifi0: Use hw queue 8 for CAB traffic
> wifi0: Use hw queue 9 for beacons
> wifi0: Atheros 5212: mem=0xfd7e0000, irq=21
>
> This is the start of the server hanging, it will just repeat this in the
> log until i reset it.
>
> BUG: soft lockup - CPU#0 stuck for 11s! [hostapd:4644]
>
> Pid: 4644, comm: hostapd Tainted: P (2.6.24-scsi-1st #1)
> EIP: 0060:[_spin_lock+80/112] EFLAGS: 00200246 CPU: 0
> EIP is at _spin_lock+0x50/0x70
> EAX: 00000000 EBX: f6a45874 ECX: f6a4586c EDX: f6a45874
> ESI: f627a000 EDI: 00000000 EBP: f6a443e0 ESP: f627bc18
> DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> CR0: 8005003b CR2: b7f6c000 CR3: 362b6000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400
> [<f89ee61d>] ath_tx_processq+0x37d/0x790 [ath_pci]
> [<f89f1ada>] ath_tx_tasklet+0x6a/0x100 [ath_pci]
> [tasklet_action+59/160] tasklet_action+0x3b/0xa0
> [__do_softirq+117/240] __do_softirq+0x75/0xf0
> [do_softirq+55/64] do_softirq+0x37/0x40
> [irq_exit+69/80] irq_exit+0x45/0x50
> [do_IRQ+66/128] do_IRQ+0x42/0x80
> [common_interrupt+35/40] common_interrupt+0x23/0x28
> [<f899007b>] ieee80211_add_wpa+0x3b/0x290 [wlan]
> [run_posix_cpu_timers+1752/2208] run_posix_cpu_timers+0x6d8/0x8a0
> [<f89c9a64>] zz005b90cb+0x18/0x20 [ath_hal]
> [<f89ecf67>] ath_tx_start+0xbe7/0x1780 [ath_pci]
> [dev_queue_xmit+173/816] dev_queue_xmit+0xad/0x330
> [memcpy_fromiovec+56/80] memcpy_fromiovec+0x38/0x50
> [<f8b61e6e>] packet_sendmsg+0x22e/0x280 [af_packet]
> [<f89f10fa>] ath_mgtstart+0xea/0x1d0 [ath_pci]
> [<f8992a43>] ieee80211_send_mgmt+0x543/0x1080 [wlan]
> [core_sys_select+589/768] core_sys_select+0x24d/0x300
> [<f8999062>] domlme+0x32/0x50 [wlan]
> [<f899928f>] ieee80211_ioctl_setmlme+0x20f/0x240 [wlan]
> [__dev_get_by_name+114/144] __dev_get_by_name+0x72/0x90
> [wext_handle_ioctl+822/1104] wext_handle_ioctl+0x336/0x450
> [<f8999080>] ieee80211_ioctl_setmlme+0x0/0x240 [wlan]
> [dev_ioctl+1264/1376] dev_ioctl+0x4f0/0x560
> [sock_ioctl+0/560] sock_ioctl+0x0/0x230
> [do_ioctl+43/144] do_ioctl+0x2b/0x90
> [vfs_ioctl+561/688] vfs_ioctl+0x231/0x2b0
> [sys_ioctl+86/112] sys_ioctl+0x56/0x70
> [syscall_call+7/11] syscall_call+0x7/0xb
New description:
I've had a netgear wireless pci card in my server providing local wireless
services for several months, then the other day I rebooted the server and
since then it's been hanging almost every day. I upgraded the kernel and
madwifi modules to no affect. I think there must be another party making
some kind of call that is specifically incompatible with the madwifi
driver but I'm not sure how to find it. I'm at a loss.
this is the dmesg of the driver loading:
{{{
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.9.4
ath_pci: 0.9.4
ath_rate_sample: 1.2 (0.9.4)
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.9 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0xfd7e0000, irq=21
}}}
This is the start of the server hanging, it will just repeat this in the
log until i reset it.
{{{
BUG: soft lockup - CPU#0 stuck for 11s! [hostapd:4644]
Pid: 4644, comm: hostapd Tainted: P (2.6.24-scsi-1st #1)
EIP: 0060:[_spin_lock+80/112] EFLAGS: 00200246 CPU: 0
EIP is at _spin_lock+0x50/0x70
EAX: 00000000 EBX: f6a45874 ECX: f6a4586c EDX: f6a45874
ESI: f627a000 EDI: 00000000 EBP: f6a443e0 ESP: f627bc18
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
CR0: 8005003b CR2: b7f6c000 CR3: 362b6000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
[<f89ee61d>] ath_tx_processq+0x37d/0x790 [ath_pci]
[<f89f1ada>] ath_tx_tasklet+0x6a/0x100 [ath_pci]
[tasklet_action+59/160] tasklet_action+0x3b/0xa0
[__do_softirq+117/240] __do_softirq+0x75/0xf0
[do_softirq+55/64] do_softirq+0x37/0x40
[irq_exit+69/80] irq_exit+0x45/0x50
[do_IRQ+66/128] do_IRQ+0x42/0x80
[common_interrupt+35/40] common_interrupt+0x23/0x28
[<f899007b>] ieee80211_add_wpa+0x3b/0x290 [wlan]
[run_posix_cpu_timers+1752/2208] run_posix_cpu_timers+0x6d8/0x8a0
[<f89c9a64>] zz005b90cb+0x18/0x20 [ath_hal]
[<f89ecf67>] ath_tx_start+0xbe7/0x1780 [ath_pci]
[dev_queue_xmit+173/816] dev_queue_xmit+0xad/0x330
[memcpy_fromiovec+56/80] memcpy_fromiovec+0x38/0x50
[<f8b61e6e>] packet_sendmsg+0x22e/0x280 [af_packet]
[<f89f10fa>] ath_mgtstart+0xea/0x1d0 [ath_pci]
[<f8992a43>] ieee80211_send_mgmt+0x543/0x1080 [wlan]
[core_sys_select+589/768] core_sys_select+0x24d/0x300
[<f8999062>] domlme+0x32/0x50 [wlan]
[<f899928f>] ieee80211_ioctl_setmlme+0x20f/0x240 [wlan]
[__dev_get_by_name+114/144] __dev_get_by_name+0x72/0x90
[wext_handle_ioctl+822/1104] wext_handle_ioctl+0x336/0x450
[<f8999080>] ieee80211_ioctl_setmlme+0x0/0x240 [wlan]
[dev_ioctl+1264/1376] dev_ioctl+0x4f0/0x560
[sock_ioctl+0/560] sock_ioctl+0x0/0x230
[do_ioctl+43/144] do_ioctl+0x2b/0x90
[vfs_ioctl+561/688] vfs_ioctl+0x231/0x2b0
[sys_ioctl+86/112] sys_ioctl+0x56/0x70
[syscall_call+7/11] syscall_call+0x7/0xb
}}}
Comment (by mrenzmann):
Did you try whether trunk also shows this behaviour on your SMP box?
--
Ticket URL: <https://madwifi.org/ticket/1863#comment:1>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets