* Re: ath9k crash 3.2-rc7
@ 2012-01-26 22:19 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-26 22:19 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> thanks , i am just looking at this tough to recreate warning and its
> being reported by few users recently. please let us if you some more
> information
Another data point:
3.2.1 + fix + sign catcher
Similar warnings overflowing my /var/log partition...
Note: ath9k per se worked; after reloading ath9k module situation returned
to normal.
Jan 27 00:15:56 401a0bf1 kernel: [241491.957493] ------------[ cut here ]-
-----------
Jan 27 00:15:56 401a0bf1 kernel: [241491.957502] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 27 00:15:56 401a0bf1 kernel: [241491.957504] Hardware name: N53Jn
Jan 27 00:15:56 401a0bf1 kernel: [241491.957505] Modules linked in: ath9k
ath5k xhci_hcd nls_iso8859_1 nls_cp437 vfat fat isofs nls_utf8 udf
crc_itu_t nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs cryptd aes_x86_64
aes_generic af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo
videodev v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate
ppp_async crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel
kvm atl1c ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio
usbserial arc4 mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too
mii fuse thermal ac tun usb_storage usb_libusual cpufreq_conservative
speedstep_lib cpufreq_powersave cpufreq_performance loop ipv6
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc battery
power_supply coretemp cpufreq_ondemand acpi_cpufreq freq_table processor
mperf fbcon tileblit font bitblit softcursor i915 drm_kms_helper drm
intel_agp i2c_algo_bit button intel_gtt agpgart vi
Jan 27 00:15:56 401a0bf1 kernel: eo thermal_sys hwmon ext4 jbd2 crc16
sr_mod cdrom ahci libahci xtkbd ohci_hcd uhci_hcd ehci_hcd usbhid hid
usbcore usb_common btrfs zlib_deflate libcrc32c crc32c ext3 jbd mbcache
synaptics_i2c i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif
libata scsi_mod dm_mod unix [last unloaded: xhci_hcd]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957597] Pid: 20646, comm:
kworker/u:1 Tainted: G W 3.2.1 #1
Jan 27 00:15:56 401a0bf1 kernel: [241491.957599] Call Trace:
Jan 27 00:15:56 401a0bf1 kernel: [241491.957606]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 27 00:15:56 401a0bf1 kernel: [241491.957606] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 27 00:15:56 401a0bf1 kernel: [241491.957608]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 27 00:15:56 401a0bf1 kernel: [241491.957608] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 27 00:15:56 401a0bf1 kernel: [241491.957611]
[ath9k:ath_rc_get_highest_rix.clone.18+0x159/0x200]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957611] [<ffffffffa0782769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957614]
[ath9k:ath_get_rate+0x86/0x480] ath_get_rate+0x86/0x480 [ath9k]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957614] [<ffffffffa0782896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957624]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957624] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957629]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957629] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957635]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957635] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957639] [__alloc_skb+0x82/0x160]
? __alloc_skb+0x82/0x160
Jan 27 00:15:56 401a0bf1 kernel: [241491.957639] [<ffffffff812ac842>] ?
__alloc_skb+0x82/0x160
Jan 27 00:15:56 401a0bf1 kernel: [241491.957644]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957644] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957649]
[mac80211:ieee80211_tx_skb+0x56/0x70] ieee80211_tx_skb+0x56/0x70
[mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957649] [<ffffffffa0549e06>]
ieee80211_tx_skb+0x56/0x70 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957654]
[mac80211:ieee80211_send_nullfunc+0x51/0x70]
ieee80211_send_nullfunc+0x51/0x70 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957654] [<ffffffffa0536f11>]
ieee80211_send_nullfunc+0x51/0x70 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957659]
[mac80211:ieee80211_rx_mgmt_beacon+0x4b3/0x660]
ieee80211_rx_mgmt_beacon+0x4b3/0x660 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957659] [<ffffffffa0537f63>]
ieee80211_rx_mgmt_beacon+0x4b3/0x660 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957664]
[mac80211:ieee80211_sta_rx_queued_mgmt+0x27f/0x3b0]
ieee80211_sta_rx_queued_mgmt+0x27f/0x3b0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957664] [<ffffffffa05393cf>]
ieee80211_sta_rx_queued_mgmt+0x27f/0x3b0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957669]
[mac80211:ieee80211_iface_work+0x22b/0x330]
ieee80211_iface_work+0x22b/0x330 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957669] [<ffffffffa053ca2b>]
ieee80211_iface_work+0x22b/0x330 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957675]
[mac80211:ieee80211_iface_work+0x0/0x330] ?
ieee80211_teardown_sdata+0xd0/0xd0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957675] [<ffffffffa053c800>] ?
ieee80211_teardown_sdata+0xd0/0xd0 [mac80211]
Jan 27 00:15:56 401a0bf1 kernel: [241491.957679]
[process_one_work+0x111/0x390] process_one_work+0x111/0x390
Jan 27 00:15:56 401a0bf1 kernel: [241491.957679] [<ffffffff81062eb1>]
process_one_work+0x111/0x390
Jan 27 00:15:56 401a0bf1 kernel: [241491.957682]
[worker_thread+0x162/0x340] worker_thread+0x162/0x340
Jan 27 00:15:56 401a0bf1 kernel: [241491.957682] [<ffffffff81063d12>]
worker_thread+0x162/0x340
Jan 27 00:15:56 401a0bf1 kernel: [241491.957685]
[worker_thread+0x0/0x340] ? manage_workers.clone.26+0x240/0x240
Jan 27 00:15:56 401a0bf1 kernel: [241491.957685] [<ffffffff81063bb0>] ?
manage_workers.clone.26+0x240/0x240
Jan 27 00:15:56 401a0bf1 kernel: [241491.957688] [kthread+0x96/0xa0]
kthread+0x96/0xa0
Jan 27 00:15:56 401a0bf1 kernel: [241491.957688] [<ffffffff81068936>]
kthread+0x96/0xa0
Jan 27 00:15:56 401a0bf1 kernel: [241491.957692]
[kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
Jan 27 00:15:56 401a0bf1 kernel: [241491.957692] [<ffffffff8135ef34>]
kernel_thread_helper+0x4/0x10
Jan 27 00:15:56 401a0bf1 kernel: [241491.957694] [kthread+0x0/0xa0] ?
kthread_worker_fn+0x190/0x190
Jan 27 00:15:56 401a0bf1 kernel: [241491.957694] [<ffffffff810688a0>] ?
kthread_worker_fn+0x190/0x190
Jan 27 00:15:56 401a0bf1 kernel: [241491.957697]
[kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
Jan 27 00:15:56 401a0bf1 kernel: [241491.957697] [<ffffffff8135ef30>] ?
gs_change+0x13/0x13
Jan 27 00:15:56 401a0bf1 kernel: [241491.957698] ---[ end trace
078f024285127110 ]---
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-20 4:42 MR
@ 2012-01-20 5:16 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-20 5:16 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
Hi,
2012/1/20 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > I read the roaming script. I need to get the scan results and then
> issue
> > "roam" in loop between all the APs I can access, right? Will try just
> to
> > collect some new testing data.
> >
> > Thanks for the patch - looks like it works fine so far.
>
> Got a fresh trace... No idea how it happened, to be honest.
>
> First, I got a few surprisingly non-lethal
>
> Jan 18 11:39:16 401a0bf1 kernel: [401292.709527] ath: Failed to stop TX
> DMA, queues=0x005!
> Jan 18 11:39:16 401a0bf1 kernel: [401292.726868] ath: Failed to stop TX
> DMA, queues=0x005!
>
> Jan 19 04:19:28 401a0bf1 kernel: [452270.295826] ath: Failed to stop TX
> DMA, queues=0x005!
> Jan 19 04:19:28 401a0bf1 kernel: [452270.313079] ath: Failed to stop TX
> DMA, queues=0x005!
>
> On Jan 19, I sshed quite a few gigabytes over cpio/ssh
>
> Got memory allocation warnings, log sample in the end of message. WiFi
> driver is mentioned in the stack, but looks mostly harmless.
>
> Then I suspended (succesfully) and when I got home I checked my email
> succesfully using WiFi.
>
> Then I did my standard mistake (closing the lid without stopping
> screensaver: after some time I get a GL screensaver with DPMS-Off state
> which is bad for i915 for some reason).
>
> I got failed GPU hangcheck at
>
> Jan 19 23:41:39 401a0bf1 kernel: [49726.973809]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> and in two seconds X server was gone (I was asleep by that time)
>
> Then..
>
> Jan 20 06:37:41 401a0bf1 kernel: [74665.029637] ath: Timeout while waiting
> for nf to load: AR_PHY_AGC_CONTROL=0x40d22
> Jan 20 06:37:41 401a0bf1 kernel: [74665.362365] ath: Failed to stop TX
> DMA, queues=0x005!
> Jan 20 06:37:41 401a0bf1 kernel: [74665.371028] ------------[ cut here ]--
> ----------
> Jan 20 06:37:41 401a0bf1 kernel: [74665.371038] WARNING: at
> drivers/net/wireless/ath/ath9k/rc.c:697
> ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
thanks , i am just looking at this tough to recreate warning and its
being reported by few users recently. please let us if you some more
information
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-20 4:42 MR
2012-01-20 5:16 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-20 4:42 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> I read the roaming script. I need to get the scan results and then
issue
> "roam" in loop between all the APs I can access, right? Will try just
to
> collect some new testing data.
>
> Thanks for the patch - looks like it works fine so far.
Got a fresh trace... No idea how it happened, to be honest.
First, I got a few surprisingly non-lethal
Jan 18 11:39:16 401a0bf1 kernel: [401292.709527] ath: Failed to stop TX
DMA, queues=0x005!
Jan 18 11:39:16 401a0bf1 kernel: [401292.726868] ath: Failed to stop TX
DMA, queues=0x005!
Jan 19 04:19:28 401a0bf1 kernel: [452270.295826] ath: Failed to stop TX
DMA, queues=0x005!
Jan 19 04:19:28 401a0bf1 kernel: [452270.313079] ath: Failed to stop TX
DMA, queues=0x005!
On Jan 19, I sshed quite a few gigabytes over cpio/ssh
Got memory allocation warnings, log sample in the end of message. WiFi
driver is mentioned in the stack, but looks mostly harmless.
Then I suspended (succesfully) and when I got home I checked my email
succesfully using WiFi.
Then I did my standard mistake (closing the lid without stopping
screensaver: after some time I get a GL screensaver with DPMS-Off state
which is bad for i915 for some reason).
I got failed GPU hangcheck at
Jan 19 23:41:39 401a0bf1 kernel: [49726.973809]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
and in two seconds X server was gone (I was asleep by that time)
Then..
Jan 20 06:37:41 401a0bf1 kernel: [74665.029637] ath: Timeout while waiting
for nf to load: AR_PHY_AGC_CONTROL=0x40d22
Jan 20 06:37:41 401a0bf1 kernel: [74665.362365] ath: Failed to stop TX
DMA, queues=0x005!
Jan 20 06:37:41 401a0bf1 kernel: [74665.371028] ------------[ cut here ]--
----------
Jan 20 06:37:41 401a0bf1 kernel: [74665.371038] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
It continued to log-spam for an hour, then I shut it down.
Log in the very end of the message
The same warnings got repeated again and again, network was down. Didn't
have time to check whether reloading module would help, though.
Jan 19 16:52:28 401a0bf1 kernel: [29856.739064] ssh: page allocation
failure: order:1, mode:0x4020
Jan 19 16:52:28 401a0bf1 kernel: [29856.739069] Pid: 1657, comm: ssh Not
tainted 3.2.0 #1
Jan 19 16:52:28 401a0bf1 kernel: [29856.739071] Call Trace:
Jan 19 16:52:28 401a0bf1 kernel: [29856.739081]
[warn_alloc_failed+0xeb/0x130] warn_alloc_failed+0xeb/0x130
Jan 19 16:52:28 401a0bf1 kernel: [29856.739081] [<ffffffff810c3fab>]
warn_alloc_failed+0xeb/0x130
Jan 19 16:52:28 401a0bf1 kernel: [29856.739085]
[__alloc_pages_nodemask+0x487/0x6f0] __alloc_pages_nodemask+0x487/0x6f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739085] [<ffffffff810c6237>]
__alloc_pages_nodemask+0x487/0x6f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739091] [new_slab+0x218/0x250]
new_slab+0x218/0x250
Jan 19 16:52:28 401a0bf1 kernel: [29856.739091] [<ffffffff810f8718>]
new_slab+0x218/0x250
Jan 19 16:52:28 401a0bf1 kernel: [29856.739095]
[__slab_alloc.clone.64+0x1f2/0x290] __slab_alloc.clone.64+0x1f2/0x290
Jan 19 16:52:28 401a0bf1 kernel: [29856.739095] [<ffffffff810f9ff2>]
__slab_alloc.clone.64+0x1f2/0x290
Jan 19 16:52:28 401a0bf1 kernel: [29856.739099]
[pskb_expand_head+0x93/0x300] ? pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739099] [<ffffffff812adae3>] ?
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739104]
[led_trigger_event+0x23/0x80] ? led_trigger_event+0x23/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.739104] [<ffffffff812920e3>] ?
led_trigger_event+0x23/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.739130]
[mac80211:ieee80211_led_tx+0x42/0x50] ? ieee80211_led_tx+0x42/0x50
[mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739130] [<ffffffffa054d572>] ?
ieee80211_led_tx+0x42/0x50 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739132]
[pskb_expand_head+0x93/0x300] ? pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739132] [<ffffffff812adae3>] ?
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739134] [__kmalloc+0x164/0x180]
__kmalloc+0x164/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.739134] [<ffffffff810fa364>]
__kmalloc+0x164/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.739137]
[pskb_expand_head+0x93/0x300] pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739137] [<ffffffff812adae3>]
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739143]
[mac80211:ieee80211_skb_resize.clone.28+0x44/0xc0]
ieee80211_skb_resize.clone.28+0x44/0xc0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739143] [<ffffffffa0547c24>]
ieee80211_skb_resize.clone.28+0x44/0xc0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739150]
[mac80211:ieee80211_subif_start_xmit+0x23c/0x7e0]
ieee80211_subif_start_xmit+0x23c/0x7e0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739150] [<ffffffffa054958c>]
ieee80211_subif_start_xmit+0x23c/0x7e0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.739154] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.739154] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.739158]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 19 16:52:28 401a0bf1 kernel: [29856.739158] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 19 16:52:28 401a0bf1 kernel: [29856.739163]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739163] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739166]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739166] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739171]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739171] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.739174] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739174] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739177]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.739177] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.739179] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.739179] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.739182]
[ip_queue_xmit+0x15a/0x400] ip_queue_xmit+0x15a/0x400
Jan 19 16:52:28 401a0bf1 kernel: [29856.739182] [<ffffffff812eef5a>]
ip_queue_xmit+0x15a/0x400
Jan 19 16:52:28 401a0bf1 kernel: [29856.739186]
[tcp_transmit_skb+0x3de/0x8f0] tcp_transmit_skb+0x3de/0x8f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739186] [<ffffffff81305a7e>]
tcp_transmit_skb+0x3de/0x8f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739189]
[tcp_write_xmit+0x1d2/0x9d0] tcp_write_xmit+0x1d2/0x9d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739189] [<ffffffff813066a2>]
tcp_write_xmit+0x1d2/0x9d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739192] [ksize+0x17/0xc0] ?
ksize+0x17/0xc0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739192] [<ffffffff810f8d47>] ?
ksize+0x17/0xc0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739194] [tcp_push_one+0x2b/0x30]
tcp_push_one+0x2b/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.739194] [<ffffffff81306ecb>]
tcp_push_one+0x2b/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.739199] [tcp_sendmsg+0xcde/0xdd0]
tcp_sendmsg+0xcde/0xdd0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739199] [<ffffffff812f8aee>]
tcp_sendmsg+0xcde/0xdd0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739203]
[try_to_wake_up+0xce/0x270] ? try_to_wake_up+0xce/0x270
Jan 19 16:52:28 401a0bf1 kernel: [29856.739203] [<ffffffff8104364e>] ?
try_to_wake_up+0xce/0x270
Jan 19 16:52:28 401a0bf1 kernel: [29856.739208] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739208] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739212]
[sock_aio_write+0x15b/0x170] sock_aio_write+0x15b/0x170
Jan 19 16:52:28 401a0bf1 kernel: [29856.739212] [<ffffffff812a27cb>]
sock_aio_write+0x15b/0x170
Jan 19 16:52:28 401a0bf1 kernel: [29856.739217]
[do_sync_write+0xda/0x120] do_sync_write+0xda/0x120
Jan 19 16:52:28 401a0bf1 kernel: [29856.739217] [<ffffffff811051ba>]
do_sync_write+0xda/0x120
Jan 19 16:52:28 401a0bf1 kernel: [29856.739221]
[handle_mm_fault+0x162/0x260] ? handle_mm_fault+0x162/0x260
Jan 19 16:52:28 401a0bf1 kernel: [29856.739221] [<ffffffff810de432>] ?
handle_mm_fault+0x162/0x260
Jan 19 16:52:28 401a0bf1 kernel: [29856.739227]
[security_file_permission+0x27/0xb0] ? security_file_permission+0x27/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739227] [<ffffffff81187cc7>] ?
security_file_permission+0x27/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739230] [vfs_write+0x16a/0x180]
vfs_write+0x16a/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.739230] [<ffffffff81105b2a>]
vfs_write+0x16a/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.739233] [sys_write+0x4c/0x90]
sys_write+0x4c/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.739233] [<ffffffff81105d9c>]
sys_write+0x4c/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.739239]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 19 16:52:28 401a0bf1 kernel: [29856.739239] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 19 16:52:28 401a0bf1 kernel: [29856.739241] Mem-Info:
Jan 19 16:52:28 401a0bf1 kernel: [29856.739243] DMA per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.739245] CPU 0: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739247] CPU 1: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739249] CPU 2: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739251] CPU 3: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739252] DMA32 per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.739254] CPU 0: hi: 186, btch:
31 usd: 114
Jan 19 16:52:28 401a0bf1 kernel: [29856.739256] CPU 1: hi: 186, btch:
31 usd: 102
Jan 19 16:52:28 401a0bf1 kernel: [29856.739258] CPU 2: hi: 186, btch:
31 usd: 149
Jan 19 16:52:28 401a0bf1 kernel: [29856.739260] CPU 3: hi: 186, btch:
31 usd: 75
Jan 19 16:52:28 401a0bf1 kernel: [29856.739262] Normal per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.739264] CPU 0: hi: 186, btch:
31 usd: 108
Jan 19 16:52:28 401a0bf1 kernel: [29856.739265] CPU 1: hi: 186, btch:
31 usd: 175
Jan 19 16:52:28 401a0bf1 kernel: [29856.739268] CPU 2: hi: 186, btch:
31 usd: 104
Jan 19 16:52:28 401a0bf1 kernel: [29856.739269] CPU 3: hi: 186, btch:
31 usd: 52
Jan 19 16:52:28 401a0bf1 kernel: [29856.739273] active_anon:433335
inactive_anon:153961 isolated_anon:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739274] active_file:166130
inactive_file:140108 isolated_file:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739275] unevictable:0 dirty:87
writeback:0 unstable:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739276] free:13588
slab_reclaimable:20726 slab_unreclaimable:7912
Jan 19 16:52:28 401a0bf1 kernel: [29856.739277] mapped:20503 shmem:33840
pagetables:5073 bounce:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739283] DMA free:15168kB min:28kB
low:32kB high:40kB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:15640kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB
slab_reclaimable:496kB slab_unreclaimable:200kB kernel_stack:8kB
pagetables:24kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
all_unreclaimable? yes
Jan 19 16:52:28 401a0bf1 kernel: [29856.739288] lowmem_reserve[]: 0 2653
3787 3787
Jan 19 16:52:28 401a0bf1 kernel: [29856.739296] DMA32 free:36224kB
min:5504kB low:6880kB high:8256kB active_anon:1202436kB
inactive_anon:426920kB active_file:521536kB inactive_file:442340kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2716812kB
mlocked:0kB dirty:228kB writeback:0kB mapped:31508kB shmem:105520kB
slab_reclaimable:45348kB slab_unreclaimable:12832kB kernel_stack:1344kB
pagetables:9700kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:189 all_unreclaimable? no
Jan 19 16:52:28 401a0bf1 kernel: [29856.739301] lowmem_reserve[]: 0 0 1134
1134
Jan 19 16:52:28 401a0bf1 kernel: [29856.739308] Normal free:2960kB
min:2352kB low:2940kB high:3528kB active_anon:530904kB
inactive_anon:188924kB active_file:142984kB inactive_file:118092kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1161216kB
mlocked:0kB dirty:120kB writeback:0kB mapped:50504kB shmem:29840kB
slab_reclaimable:37060kB slab_unreclaimable:18616kB kernel_stack:2472kB
pagetables:10568kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:43 all_unreclaimable? no
Jan 19 16:52:28 401a0bf1 kernel: [29856.739313] lowmem_reserve[]: 0 0 0 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.739316] DMA: 4*4kB 5*8kB 6*16kB
6*32kB 1*64kB 1*128kB 1*256kB 0*512kB 2*1024kB 2*2048kB 2*4096kB = 15128kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.739324] DMA32: 8823*4kB 3*8kB
5*16kB 9*32kB 1*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
36132kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.739331] Normal: 640*4kB 0*8kB
1*16kB 6*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
2960kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.739338] 352585 total pagecache
pages
Jan 19 16:52:28 401a0bf1 kernel: [29856.739340] 12471 pages in swap cache
Jan 19 16:52:28 401a0bf1 kernel: [29856.739342] Swap cache stats: add
105397, delete 92926, find 133772/141462
Jan 19 16:52:28 401a0bf1 kernel: [29856.739343] Free swap = 6207460kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.739345] Total swap = 6297444kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.754077] 1015792 pages RAM
Jan 19 16:52:28 401a0bf1 kernel: [29856.754080] 56932 pages reserved
Jan 19 16:52:28 401a0bf1 kernel: [29856.754081] 436740 pages shared
Jan 19 16:52:28 401a0bf1 kernel: [29856.754081] 604363 pages non-shared
Jan 19 16:52:28 401a0bf1 kernel: [29856.754085] SLUB: Unable to allocate
memory on node -1 (gfp=0x20)
Jan 19 16:52:28 401a0bf1 kernel: [29856.754087] cache: kmalloc-8192,
object size: 8192, buffer size: 8192, default order: 3, min order: 1
Jan 19 16:52:28 401a0bf1 kernel: [29856.754090] node 0: slabs: 27, objs:
99, free: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.754175] ieee80211 phy3: failed to
reallocate TX buffer
Jan 19 16:52:28 401a0bf1 kernel: [29856.847514] screen: page allocation
failure: order:1, mode:0x4020
Jan 19 16:52:28 401a0bf1 kernel: [29856.847520] Pid: 18660, comm: screen
Not tainted 3.2.0 #1
Jan 19 16:52:28 401a0bf1 kernel: [29856.847522] Call Trace:
Jan 19 16:52:28 401a0bf1 kernel: [29856.847524] <IRQ>
[warn_alloc_failed+0xeb/0x130] warn_alloc_failed+0xeb/0x130
Jan 19 16:52:28 401a0bf1 kernel: [29856.847524] <IRQ>
[<ffffffff810c3fab>] warn_alloc_failed+0xeb/0x130
Jan 19 16:52:28 401a0bf1 kernel: [29856.847537]
[__alloc_pages_nodemask+0x487/0x6f0] __alloc_pages_nodemask+0x487/0x6f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847537] [<ffffffff810c6237>]
__alloc_pages_nodemask+0x487/0x6f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847543] [new_slab+0x218/0x250]
new_slab+0x218/0x250
Jan 19 16:52:28 401a0bf1 kernel: [29856.847543] [<ffffffff810f8718>]
new_slab+0x218/0x250
Jan 19 16:52:28 401a0bf1 kernel: [29856.847547]
[__slab_alloc.clone.64+0x1f2/0x290] __slab_alloc.clone.64+0x1f2/0x290
Jan 19 16:52:28 401a0bf1 kernel: [29856.847547] [<ffffffff810f9ff2>]
__slab_alloc.clone.64+0x1f2/0x290
Jan 19 16:52:28 401a0bf1 kernel: [29856.847552]
[pskb_expand_head+0x93/0x300] ? pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847552] [<ffffffff812adae3>] ?
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847557]
[led_trigger_event+0x23/0x80] ? led_trigger_event+0x23/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.847557] [<ffffffff812920e3>] ?
led_trigger_event+0x23/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.847582]
[mac80211:ieee80211_led_tx+0x42/0x50] ? ieee80211_led_tx+0x42/0x50
[mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847582] [<ffffffffa054d572>] ?
ieee80211_led_tx+0x42/0x50 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847585]
[pskb_expand_head+0x93/0x300] ? pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847585] [<ffffffff812adae3>] ?
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847588] [__kmalloc+0x164/0x180]
__kmalloc+0x164/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.847588] [<ffffffff810fa364>]
__kmalloc+0x164/0x180
Jan 19 16:52:28 401a0bf1 kernel: [29856.847590]
[pskb_expand_head+0x93/0x300] pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847590] [<ffffffff812adae3>]
pskb_expand_head+0x93/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847597]
[mac80211:ieee80211_skb_resize.clone.28+0x44/0xc0]
ieee80211_skb_resize.clone.28+0x44/0xc0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847597] [<ffffffffa0547c24>]
ieee80211_skb_resize.clone.28+0x44/0xc0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847604]
[mac80211:ieee80211_subif_start_xmit+0x23c/0x7e0]
ieee80211_subif_start_xmit+0x23c/0x7e0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847604] [<ffffffffa054958c>]
ieee80211_subif_start_xmit+0x23c/0x7e0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847609] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847609] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847613]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 19 16:52:28 401a0bf1 kernel: [29856.847613] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 19 16:52:28 401a0bf1 kernel: [29856.847619]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847619] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847621]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847621] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847626]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847626] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 19 16:52:28 401a0bf1 kernel: [29856.847629] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847629] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847632]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847632] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847635] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.847635] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.847638]
[ip_queue_xmit+0x15a/0x400] ip_queue_xmit+0x15a/0x400
Jan 19 16:52:28 401a0bf1 kernel: [29856.847638] [<ffffffff812eef5a>]
ip_queue_xmit+0x15a/0x400
Jan 19 16:52:28 401a0bf1 kernel: [29856.847642]
[tcp_transmit_skb+0x3de/0x8f0] tcp_transmit_skb+0x3de/0x8f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847642] [<ffffffff81305a7e>]
tcp_transmit_skb+0x3de/0x8f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847645]
[tcp_write_xmit+0x1d2/0x9d0] tcp_write_xmit+0x1d2/0x9d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847645] [<ffffffff813066a2>]
tcp_write_xmit+0x1d2/0x9d0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847648]
[__tcp_push_pending_frames+0x21/0x90] __tcp_push_pending_frames+0x21/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.847648] [<ffffffff81306ef1>]
__tcp_push_pending_frames+0x21/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.847651]
[tcp_rcv_established+0x4b6/0x840] tcp_rcv_established+0x4b6/0x840
Jan 19 16:52:28 401a0bf1 kernel: [29856.847651] [<ffffffff81303ab6>]
tcp_rcv_established+0x4b6/0x840
Jan 19 16:52:28 401a0bf1 kernel: [29856.847655]
[tcp_v4_do_rcv+0x257/0x460] tcp_v4_do_rcv+0x257/0x460
Jan 19 16:52:28 401a0bf1 kernel: [29856.847655] [<ffffffff8130b137>]
tcp_v4_do_rcv+0x257/0x460
Jan 19 16:52:28 401a0bf1 kernel: [29856.847660]
[security_sock_rcv_skb+0x11/0x20] ? security_sock_rcv_skb+0x11/0x20
Jan 19 16:52:28 401a0bf1 kernel: [29856.847660] [<ffffffff811871a1>] ?
security_sock_rcv_skb+0x11/0x20
Jan 19 16:52:28 401a0bf1 kernel: [29856.847663] [tcp_v4_rcv+0x656/0x900]
tcp_v4_rcv+0x656/0x900
Jan 19 16:52:28 401a0bf1 kernel: [29856.847663] [<ffffffff8130d5d6>]
tcp_v4_rcv+0x656/0x900
Jan 19 16:52:28 401a0bf1 kernel: [29856.847666]
[ip_route_input_common+0xbec/0xe10] ? ip_route_input_common+0xbec/0xe10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847666] [<ffffffff812e7d7c>] ?
ip_route_input_common+0xbec/0xe10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847671]
[neigh_direct_output+0xc/0x10] ? neigh_direct_output+0xc/0x10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847671] [<ffffffff812c27ac>] ?
neigh_direct_output+0xc/0x10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847674]
[ip_local_deliver_finish+0xdd/0x280] ip_local_deliver_finish+0xdd/0x280
Jan 19 16:52:28 401a0bf1 kernel: [29856.847674] [<ffffffff812e9dbd>]
ip_local_deliver_finish+0xdd/0x280
Jan 19 16:52:28 401a0bf1 kernel: [29856.847677]
[ip_local_deliver+0x80/0x90] ip_local_deliver+0x80/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.847677] [<ffffffff812ea120>]
ip_local_deliver+0x80/0x90
Jan 19 16:52:28 401a0bf1 kernel: [29856.847679]
[ip_rcv_finish+0x135/0x3a0] ip_rcv_finish+0x135/0x3a0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847679] [<ffffffff812e9a75>]
ip_rcv_finish+0x135/0x3a0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847682] [ip_rcv+0x224/0x2f0]
ip_rcv+0x224/0x2f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847682] [<ffffffff812ea354>]
ip_rcv+0x224/0x2f0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847687] [<ffffffffa069de65>] ?
packet_rcv_spkt+0x45/0x198 [af_packet]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847691]
[__netif_receive_skb+0x4d6/0x580] __netif_receive_skb+0x4d6/0x580
Jan 19 16:52:28 401a0bf1 kernel: [29856.847691] [<ffffffff812b87c6>]
__netif_receive_skb+0x4d6/0x580
Jan 19 16:52:28 401a0bf1 kernel: [29856.847695]
[netif_receive_skb+0x58/0x80] netif_receive_skb+0x58/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.847695] [<ffffffff812b88c8>]
netif_receive_skb+0x58/0x80
Jan 19 16:52:28 401a0bf1 kernel: [29856.847701]
[mac80211:ieee80211_deliver_skb.clone.25+0xa8/0x210]
ieee80211_deliver_skb.clone.25+0xa8/0x210 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847701] [<ffffffffa05436a8>]
ieee80211_deliver_skb.clone.25+0xa8/0x210 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847707]
[mac80211:ieee80211_rx_handlers+0xc9a/0x1b50]
ieee80211_rx_handlers+0xc9a/0x1b50 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847707] [<ffffffffa05446fa>]
ieee80211_rx_handlers+0xc9a/0x1b50 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847710] [__kfree_skb+0x19/0xa0] ?
__kfree_skb+0x19/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847710] [<ffffffff812ac2f9>] ?
__kfree_skb+0x19/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847713] [consume_skb+0x19/0x40] ?
consume_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847713] [<ffffffff812ac399>] ?
consume_skb+0x19/0x40
Jan 19 16:52:28 401a0bf1 kernel: [29856.847720]
[mac80211:ieee80211_prepare_and_rx_handle+0x2bd/0x900]
ieee80211_prepare_and_rx_handle+0x2bd/0x900 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847720] [<ffffffffa054586d>]
ieee80211_prepare_and_rx_handle+0x2bd/0x900 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847727]
[mac80211:ieee80211_rx+0x30b/0x9a0] ieee80211_rx+0x30b/0x9a0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847727] [<ffffffffa05461bb>]
ieee80211_rx+0x30b/0x9a0 [mac80211]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847734] [<ffffffffa06c01d7>]
ath_rx_tasklet+0xcf7/0x1e30 [ath9k]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847739]
[swiotlb_map_page+0x0/0x100] ? swiotlb_map_sg+0x10/0x10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847739] [<ffffffff811e10d0>] ?
swiotlb_map_sg+0x10/0x10
Jan 19 16:52:28 401a0bf1 kernel: [29856.847744] [<ffffffffa06bcf3f>]
ath9k_tasklet+0xff/0x1c0 [ath9k]
Jan 19 16:52:28 401a0bf1 kernel: [29856.847748]
[tasklet_action+0x64/0xe0] tasklet_action+0x64/0xe0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847748] [<ffffffff81052a74>]
tasklet_action+0x64/0xe0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847751] [__do_softirq+0x98/0x120]
__do_softirq+0x98/0x120
Jan 19 16:52:28 401a0bf1 kernel: [29856.847751] [<ffffffff81052d98>]
__do_softirq+0x98/0x120
Jan 19 16:52:28 401a0bf1 kernel: [29856.847755]
[ack_apic_level+0x71/0x1e0] ? ack_apic_level+0x71/0x1e0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847755] [<ffffffff810296e1>] ?
ack_apic_level+0x71/0x1e0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847761] [call_softirq+0x1c/0x30]
call_softirq+0x1c/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.847761] [<ffffffff8135efec>]
call_softirq+0x1c/0x30
Jan 19 16:52:28 401a0bf1 kernel: [29856.847765] [do_softirq+0x65/0xa0]
do_softirq+0x65/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847765] [<ffffffff8100d815>]
do_softirq+0x65/0xa0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847768] [irq_exit+0x8e/0xb0]
irq_exit+0x8e/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847768] [<ffffffff8105308e>]
irq_exit+0x8e/0xb0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847770] [do_IRQ+0x61/0xe0]
do_IRQ+0x61/0xe0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847770] [<ffffffff8100d441>]
do_IRQ+0x61/0xe0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847773] [ret_from_intr+0x0/0x15]
common_interrupt+0x6e/0x6e
Jan 19 16:52:28 401a0bf1 kernel: [29856.847773] [<ffffffff8135c62e>]
common_interrupt+0x6e/0x6e
Jan 19 16:52:28 401a0bf1 kernel: [29856.847776] <EOI> Mem-Info:
Jan 19 16:52:28 401a0bf1 kernel: [29856.847779] DMA per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.847781] CPU 0: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847783] CPU 1: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847785] CPU 2: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847786] CPU 3: hi: 0, btch:
1 usd: 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847788] DMA32 per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.847789] CPU 0: hi: 186, btch:
31 usd: 169
Jan 19 16:52:28 401a0bf1 kernel: [29856.847791] CPU 1: hi: 186, btch:
31 usd: 38
Jan 19 16:52:28 401a0bf1 kernel: [29856.847793] CPU 2: hi: 186, btch:
31 usd: 53
Jan 19 16:52:28 401a0bf1 kernel: [29856.847795] CPU 3: hi: 186, btch:
31 usd: 150
Jan 19 16:52:28 401a0bf1 kernel: [29856.847796] Normal per-cpu:
Jan 19 16:52:28 401a0bf1 kernel: [29856.847798] CPU 0: hi: 186, btch:
31 usd: 172
Jan 19 16:52:28 401a0bf1 kernel: [29856.847800] CPU 1: hi: 186, btch:
31 usd: 85
Jan 19 16:52:28 401a0bf1 kernel: [29856.847801] CPU 2: hi: 186, btch:
31 usd: 20
Jan 19 16:52:28 401a0bf1 kernel: [29856.847804] CPU 3: hi: 186, btch:
31 usd: 97
Jan 19 16:52:28 401a0bf1 kernel: [29856.847808] active_anon:454825
inactive_anon:152014 isolated_anon:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847809] active_file:146979
inactive_file:142073 isolated_file:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847810] unevictable:0 dirty:87
writeback:0 unstable:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847811] free:11207
slab_reclaimable:20726 slab_unreclaimable:7860
Jan 19 16:52:28 401a0bf1 kernel: [29856.847812] mapped:20393 shmem:33840
pagetables:5174 bounce:0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847818] DMA free:15168kB min:28kB
low:32kB high:40kB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB
present:15640kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB
slab_reclaimable:496kB slab_unreclaimable:152kB kernel_stack:56kB
pagetables:24kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
all_unreclaimable? yes
Jan 19 16:52:28 401a0bf1 kernel: [29856.847823] lowmem_reserve[]: 0 2653
3787 3787
Jan 19 16:52:28 401a0bf1 kernel: [29856.847830] DMA32 free:26764kB
min:5504kB low:6880kB high:8256kB active_anon:1270664kB
inactive_anon:420880kB active_file:463632kB inactive_file:447692kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2716812kB
mlocked:0kB dirty:228kB writeback:0kB mapped:31068kB shmem:105520kB
slab_reclaimable:45348kB slab_unreclaimable:12672kB kernel_stack:1344kB
pagetables:9920kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:0 all_unreclaimable? no
Jan 19 16:52:28 401a0bf1 kernel: [29856.847836] lowmem_reserve[]: 0 0 1134
1134
Jan 19 16:52:28 401a0bf1 kernel: [29856.847843] Normal free:2896kB
min:2352kB low:2940kB high:3528kB active_anon:548636kB
inactive_anon:187176kB active_file:124284kB inactive_file:120600kB
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1161216kB
mlocked:0kB dirty:120kB writeback:0kB mapped:50504kB shmem:29840kB
slab_reclaimable:37060kB slab_unreclaimable:18616kB kernel_stack:2472kB
pagetables:10752kB unstable:0kB bounce:0kB writeback_tmp:0kB
pages_scanned:240 all_unreclaimable? no
Jan 19 16:52:28 401a0bf1 kernel: [29856.847848] lowmem_reserve[]: 0 0 0 0
Jan 19 16:52:28 401a0bf1 kernel: [29856.847851] DMA: 4*4kB 8*8kB 5*16kB
7*32kB 1*64kB 1*128kB 1*256kB 0*512kB 2*1024kB 2*2048kB 2*4096kB = 15168kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.847859] DMA32: 6457*4kB 3*8kB
5*16kB 9*32kB 1*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
26668kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.847866] Normal: 624*4kB 0*8kB
1*16kB 6*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
2896kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.847873] 334392 total pagecache
pages
Jan 19 16:52:28 401a0bf1 kernel: [29856.847875] 11509 pages in swap cache
Jan 19 16:52:28 401a0bf1 kernel: [29856.847876] Swap cache stats: add
105411, delete 93902, find 133781/141475
Jan 19 16:52:28 401a0bf1 kernel: [29856.847878] Free swap = 6207496kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.847879] Total swap = 6297444kB
Jan 19 16:52:28 401a0bf1 kernel: [29856.863600] 1015792 pages RAM
Jan 19 16:52:28 401a0bf1 kernel: [29856.863603] 56932 pages reserved
Jan 19 16:52:28 401a0bf1 kernel: [29856.863605] 417956 pages shared
Jan 19 16:52:28 401a0bf1 kernel: [29856.863606] 626945 pages non-shared
Jan 20 06:37:41 401a0bf1 kernel: [74665.371038] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 20 06:37:41 401a0bf1 kernel: [74665.371041] Hardware name: N53Jn
Jan 20 06:37:41 401a0bf1 kernel: [74665.371043] Modules linked in: ath9k
ath5k xhci_hcd omfs jfs xfs exportfs reiserfs ext2 hfs hfsplus vfat fat
isofs nls_utf8 udf crc_itu_t cryptd aes_x86_64 aes_generic af_packet
snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev v4l2_compat_ioctl32
cdc_phonet phonet bsd_comp ppp_deflate ppp_async crc_ccitt ppp_generic
slhc cdc_acm rtc_cmos configs kvm_intel kvm ide_cd_mod ide_core pktcdvd
pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4 mac80211 ath9k_common
ath9k_hw ath cfg80211 rfkill 8139too mii fuse thermal ac tun usb_storage
usb_libusual cpufreq_conservative speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf fbcon tileblit font bitblit softcursor i915
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd
Jan 20 06:37:41 401a0bf1 kernel: crc16 sr_mod cdrom ahci libahci xtkbd
ohci_hcd uhci_hcd ehci_hcd usbhid hid usbcore usb_common btrfs
zlib_deflate libcrc32c crc32c ext3 jbd mbcache synaptics_i2c i2c_core
sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod dm_mod
unix [last unloaded: xhci_hcd]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371186] Pid: 7032, comm: gw6c Not
tainted 3.2.0 #1
Jan 20 06:37:41 401a0bf1 kernel: [74665.371190] Call Trace:
Jan 20 06:37:41 401a0bf1 kernel: [74665.371201]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371201] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371207]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 20 06:37:41 401a0bf1 kernel: [74665.371207] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 20 06:37:41 401a0bf1 kernel: [74665.371214] [<ffffffffa06c6769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371223] [<ffffffffa06c6896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371239]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371239] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371253]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371253] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371260] [load_balance+0x9e/0x7d0]
? load_balance+0x9e/0x7d0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371260] [<ffffffff8104680e>] ?
load_balance+0x9e/0x7d0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371273]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371273] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371286]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371286] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371299]
[mac80211:ieee80211_subif_start_xmit+0x36f/0x7e0]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371299] [<ffffffffa05496bf>]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:41 401a0bf1 kernel: [74665.371308] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 20 06:37:41 401a0bf1 kernel: [74665.371308] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 20 06:37:41 401a0bf1 kernel: [74665.371314]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:41 401a0bf1 kernel: [74665.371314] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:41 401a0bf1 kernel: [74665.371324]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371324] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371329]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371329] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371336]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 20 06:37:41 401a0bf1 kernel: [74665.371336] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 20 06:37:41 401a0bf1 kernel: [74665.371341] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371341] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 20 06:37:41 401a0bf1 kernel: [74665.371346] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 20 06:37:41 401a0bf1 kernel: [74665.371346] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 20 06:37:41 401a0bf1 kernel: [74665.371351] [ip_send_skb+0x16/0x50]
ip_send_skb+0x16/0x50
Jan 20 06:37:41 401a0bf1 kernel: [74665.371351] [<ffffffff812f00d6>]
ip_send_skb+0x16/0x50
Jan 20 06:37:41 401a0bf1 kernel: [74665.371358]
[udp_send_skb+0x108/0x380] udp_send_skb+0x108/0x380
Jan 20 06:37:41 401a0bf1 kernel: [74665.371358] [<ffffffff81311758>]
udp_send_skb+0x108/0x380
Jan 20 06:37:41 401a0bf1 kernel: [74665.371364]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 20 06:37:41 401a0bf1 kernel: [74665.371364] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.371371] [pollwake+0x0/0x60] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371371] [<ffffffff811179f0>] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371377]
[ip_generic_getfrag+0x0/0xb0] ? ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371377] [<ffffffff812ed1b0>] ?
ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371383] [udp_sendmsg+0x32a/0x910]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.371383] [<ffffffff813137da>]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.371391] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371391] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371399]
[kmem_cache_free+0x15/0x90] ? kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371399] [<ffffffff810fa7b5>] ?
kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371406] [sock_sendmsg+0xea/0x120]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371406] [<ffffffff812a3b8a>]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371415]
[tun:tun_chr_aio_read+0x79/0xd0] ? tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371415] [<ffffffffa0450499>] ?
tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371423] [do_sync_read+0xda/0x120]
? do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371423] [<ffffffff811052da>] ?
do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371430]
[lock_hrtimer_base.clone.35+0x2b/0x60] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.371430] [<ffffffff8106c6fb>] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.371436]
[sockfd_lookup_light+0x24/0x90] ? sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371436] [<ffffffff812a2bb4>] ?
sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371442] [sys_sendto+0x104/0x140]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371442] [<ffffffff812a5c54>]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371451]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.371451] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.371456] ---[ end trace
d38cf8ad260b1371 ]---
Jan 20 06:37:42 401a0bf1 kernel: [74665.371562] ------------[ cut here ]--
----------
Jan 20 06:37:42 401a0bf1 kernel: [74665.371571] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 20 06:37:42 401a0bf1 kernel: [74665.371575] Hardware name: N53Jn
Jan 20 06:37:42 401a0bf1 kernel: [74665.371577] Modules linked in: ath9k
ath5k xhci_hcd omfs jfs xfs exportfs reiserfs ext2 hfs hfsplus vfat fat
isofs nls_utf8 udf crc_itu_t cryptd aes_x86_64 aes_generic af_packet
snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev v4l2_compat_ioctl32
cdc_phonet phonet bsd_comp ppp_deflate ppp_async crc_ccitt ppp_generic
slhc cdc_acm rtc_cmos configs kvm_intel kvm ide_cd_mod ide_core pktcdvd
pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4 mac80211 ath9k_common
ath9k_hw ath cfg80211 rfkill 8139too mii fuse thermal ac tun usb_storage
usb_libusual cpufreq_conservative speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf fbcon tileblit font bitblit softcursor i915
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd
Jan 20 06:37:42 401a0bf1 kernel: crc16 sr_mod cdrom ahci libahci xtkbd
ohci_hcd uhci_hcd ehci_hcd usbhid hid usbcore usb_common btrfs
zlib_deflate libcrc32c crc32c ext3 jbd mbcache synaptics_i2c i2c_core
sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod dm_mod
unix [last unloaded: xhci_hcd]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371707] Pid: 7032, comm: gw6c
Tainted: G W 3.2.0 #1
Jan 20 06:37:42 401a0bf1 kernel: [74665.371709] Call Trace:
Jan 20 06:37:42 401a0bf1 kernel: [74665.371715]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371715] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371721]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.371721] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.371729] [<ffffffffa06c6769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371737] [<ffffffffa06c6896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371750]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371750] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371763]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371763] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371771] [<ffffffffa06bb7b8>] ?
ath9k_tx+0xa8/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371779]
[led_trigger_event+0x23/0x80] ? led_trigger_event+0x23/0x80
Jan 20 06:37:42 401a0bf1 kernel: [74665.371779] [<ffffffff812920e3>] ?
led_trigger_event+0x23/0x80
Jan 20 06:37:42 401a0bf1 kernel: [74665.371791]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371791] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371804]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371804] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371817]
[mac80211:ieee80211_subif_start_xmit+0x36f/0x7e0]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371817] [<ffffffffa05496bf>]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371824] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.371824] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.371829]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.371829] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.371837]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371837] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371842]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371842] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371848]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.371848] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.371854] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371854] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371859] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.371859] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.371864] [ip_send_skb+0x16/0x50]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.371864] [<ffffffff812f00d6>]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.371870]
[udp_send_skb+0x108/0x380] udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.371870] [<ffffffff81311758>]
udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.371874]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.371874] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.371879] [pollwake+0x0/0x60] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371879] [<ffffffff811179f0>] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371891]
[ip_generic_getfrag+0x0/0xb0] ? ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371891] [<ffffffff812ed1b0>] ?
ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371897] [udp_sendmsg+0x32a/0x910]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.371897] [<ffffffff813137da>]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.371904] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371904] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.371910]
[kmem_cache_free+0x15/0x90] ? kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371910] [<ffffffff810fa7b5>] ?
kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371915] [sock_sendmsg+0xea/0x120]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371915] [<ffffffff812a3b8a>]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371924]
[tun:tun_chr_aio_read+0x79/0xd0] ? tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371924] [<ffffffffa0450499>] ?
tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.371930] [do_sync_read+0xda/0x120]
? do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371930] [<ffffffff811052da>] ?
do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.371936]
[lock_hrtimer_base.clone.35+0x2b/0x60] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.371936] [<ffffffff8106c6fb>] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.371941]
[sockfd_lookup_light+0x24/0x90] ? sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371941] [<ffffffff812a2bb4>] ?
sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.371945] [sys_sendto+0x104/0x140]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371945] [<ffffffff812a5c54>]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.371950]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.371950] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.371954] ---[ end trace
d38cf8ad260b1372 ]---
Jan 20 06:37:42 401a0bf1 kernel: [74665.372042] ------------[ cut here ]--
----------
Jan 20 06:37:42 401a0bf1 kernel: [74665.372050] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 20 06:37:42 401a0bf1 kernel: [74665.372054] Hardware name: N53Jn
Jan 20 06:37:42 401a0bf1 kernel: [74665.372056] Modules linked in: ath9k
ath5k xhci_hcd omfs jfs xfs exportfs reiserfs ext2 hfs hfsplus vfat fat
isofs nls_utf8 udf crc_itu_t cryptd aes_x86_64 aes_generic af_packet
snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev v4l2_compat_ioctl32
cdc_phonet phonet bsd_comp ppp_deflate ppp_async crc_ccitt ppp_generic
slhc cdc_acm rtc_cmos configs kvm_intel kvm ide_cd_mod ide_core pktcdvd
pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4 mac80211 ath9k_common
ath9k_hw ath cfg80211 rfkill 8139too mii fuse thermal ac tun usb_storage
usb_libusual cpufreq_conservative speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf fbcon tileblit font bitblit softcursor i915
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd
Jan 20 06:37:42 401a0bf1 kernel: crc16 sr_mod cdrom ahci libahci xtkbd
ohci_hcd uhci_hcd ehci_hcd usbhid hid usbcore usb_common btrfs
zlib_deflate libcrc32c crc32c ext3 jbd mbcache synaptics_i2c i2c_core
sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod dm_mod
unix [last unloaded: xhci_hcd]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372199] Pid: 7032, comm: gw6c
Tainted: G W 3.2.0 #1
Jan 20 06:37:42 401a0bf1 kernel: [74665.372202] Call Trace:
Jan 20 06:37:42 401a0bf1 kernel: [74665.372208]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372208] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372213]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.372213] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.372220] [<ffffffffa06c6769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372228] [<ffffffffa06c6896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372241]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372241] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372253]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372253] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372260] [<ffffffffa06bb7b8>] ?
ath9k_tx+0xa8/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372267]
[led_trigger_event+0x23/0x80] ? led_trigger_event+0x23/0x80
Jan 20 06:37:42 401a0bf1 kernel: [74665.372267] [<ffffffff812920e3>] ?
led_trigger_event+0x23/0x80
Jan 20 06:37:42 401a0bf1 kernel: [74665.372279]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372279] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372290]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372290] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372301]
[mac80211:ieee80211_subif_start_xmit+0x36f/0x7e0]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372301] [<ffffffffa05496bf>]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372308] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.372308] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.372314]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.372314] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.372321]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372321] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372326]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372326] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372331]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.372331] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.372336] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372336] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372341] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.372341] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.372346] [ip_send_skb+0x16/0x50]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.372346] [<ffffffff812f00d6>]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.372352]
[udp_send_skb+0x108/0x380] udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.372352] [<ffffffff81311758>]
udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.372357]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.372357] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.372362] [pollwake+0x0/0x60] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372362] [<ffffffff811179f0>] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372367]
[ip_generic_getfrag+0x0/0xb0] ? ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.372367] [<ffffffff812ed1b0>] ?
ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.372373] [udp_sendmsg+0x32a/0x910]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.372373] [<ffffffff813137da>]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.372379] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372379] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.372385] [sock_sendmsg+0xea/0x120]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.372385] [<ffffffff812a3b8a>]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.372393]
[tun:tun_chr_aio_read+0x79/0xd0] ? tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372393] [<ffffffffa0450499>] ?
tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.372399] [do_sync_read+0xda/0x120]
? do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.372399] [<ffffffff811052da>] ?
do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.372405]
[lock_hrtimer_base.clone.35+0x2b/0x60] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.372405] [<ffffffff8106c6fb>] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.372411]
[sockfd_lookup_light+0x24/0x90] ? sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.372411] [<ffffffff812a2bb4>] ?
sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.372416] [sys_sendto+0x104/0x140]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.372416] [<ffffffff812a5c54>]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.372423]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.372423] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.372427] ---[ end trace
d38cf8ad260b1373 ]---
Jan 20 06:37:42 401a0bf1 kernel: [74665.379268] ------------[ cut here ]--
----------
Jan 20 06:37:42 401a0bf1 kernel: [74665.379279] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 20 06:37:42 401a0bf1 kernel: [74665.379283] Hardware name: N53Jn
Jan 20 06:37:42 401a0bf1 kernel: [74665.379285] Modules linked in: ath9k
ath5k xhci_hcd omfs jfs xfs exportfs reiserfs ext2 hfs hfsplus vfat fat
isofs nls_utf8 udf crc_itu_t cryptd aes_x86_64 aes_generic af_packet
snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev v4l2_compat_ioctl32
cdc_phonet phonet bsd_comp ppp_deflate ppp_async crc_ccitt ppp_generic
slhc cdc_acm rtc_cmos configs kvm_intel kvm ide_cd_mod ide_core pktcdvd
pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4 mac80211 ath9k_common
ath9k_hw ath cfg80211 rfkill 8139too mii fuse thermal ac tun usb_storage
usb_libusual cpufreq_conservative speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf fbcon tileblit font bitblit softcursor i915
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd
Jan 20 06:37:42 401a0bf1 kernel: crc16 sr_mod cdrom ahci libahci xtkbd
ohci_hcd uhci_hcd ehci_hcd usbhid hid usbcore usb_common btrfs
zlib_deflate libcrc32c crc32c ext3 jbd mbcache synaptics_i2c i2c_core
sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod dm_mod
unix [last unloaded: xhci_hcd]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379417] Pid: 16970, comm:
fusesmb.cache Tainted: G W 3.2.0 #1
Jan 20 06:37:42 401a0bf1 kernel: [74665.379420] Call Trace:
Jan 20 06:37:42 401a0bf1 kernel: [74665.379428]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379428] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379433]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.379433] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.379440] [<ffffffffa06c6769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379446] [<ffffffffa06c6896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379460]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379460] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379472]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379472] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379477] [load_balance+0x9e/0x7d0]
? load_balance+0x9e/0x7d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379477] [<ffffffff8104680e>] ?
load_balance+0x9e/0x7d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379489]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379489] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379500]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379500] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379511]
[mac80211:ieee80211_subif_start_xmit+0x36f/0x7e0]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379511] [<ffffffffa05496bf>]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.379518] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.379518] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.379523]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.379523] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.379530]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379530] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379534]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379534] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379540]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.379540] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.379544]
[ip_mc_output+0x139/0x250] ip_mc_output+0x139/0x250
Jan 20 06:37:42 401a0bf1 kernel: [74665.379544] [<ffffffff812ef539>]
ip_mc_output+0x139/0x250
Jan 20 06:37:42 401a0bf1 kernel: [74665.379549] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.379549] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.379553] [ip_send_skb+0x16/0x50]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.379553] [<ffffffff812f00d6>]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.379558]
[udp_send_skb+0x108/0x380] udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.379558] [<ffffffff81311758>]
udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.379562]
[ip_generic_getfrag+0x0/0xb0] ? ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.379562] [<ffffffff812ed1b0>] ?
ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.379567] [udp_sendmsg+0x32a/0x910]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.379567] [<ffffffff813137da>]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.379574]
[__alloc_pages_nodemask+0x114/0x6f0] ? __alloc_pages_nodemask+0x114/0x6f0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379574] [<ffffffff810c5ec4>] ?
__alloc_pages_nodemask+0x114/0x6f0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379579] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379579] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.379584] [sock_sendmsg+0xea/0x120]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.379584] [<ffffffff812a3b8a>]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.379590]
[handle_pte_fault+0x408/0xa60] ? handle_pte_fault+0x408/0xa60
Jan 20 06:37:42 401a0bf1 kernel: [74665.379590] [<ffffffff810dc8e8>] ?
handle_pte_fault+0x408/0xa60
Jan 20 06:37:42 401a0bf1 kernel: [74665.379597]
[core_sys_select+0x2e7/0x340] ? core_sys_select+0x2e7/0x340
Jan 20 06:37:42 401a0bf1 kernel: [74665.379597] [<ffffffff811186e7>] ?
core_sys_select+0x2e7/0x340
Jan 20 06:37:42 401a0bf1 kernel: [74665.379602]
[handle_mm_fault+0x162/0x260] ? handle_mm_fault+0x162/0x260
Jan 20 06:37:42 401a0bf1 kernel: [74665.379602] [<ffffffff810de432>] ?
handle_mm_fault+0x162/0x260
Jan 20 06:37:42 401a0bf1 kernel: [74665.379607]
[move_addr_to_kernel+0x69/0x70] ? move_addr_to_kernel+0x69/0x70
Jan 20 06:37:42 401a0bf1 kernel: [74665.379607] [<ffffffff812a5389>] ?
move_addr_to_kernel+0x69/0x70
Jan 20 06:37:42 401a0bf1 kernel: [74665.379611] [sys_sendto+0x104/0x140]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.379611] [<ffffffff812a5c54>]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.379617]
[poll_select_copy_remaining+0x101/0x150] ?
poll_select_copy_remaining+0x101/0x150
Jan 20 06:37:42 401a0bf1 kernel: [74665.379617] [<ffffffff81117b51>] ?
poll_select_copy_remaining+0x101/0x150
Jan 20 06:37:42 401a0bf1 kernel: [74665.379624]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.379624] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.379628] ---[ end trace
d38cf8ad260b1374 ]---
Jan 20 06:37:42 401a0bf1 kernel: [74665.471609] ------------[ cut here ]--
----------
Jan 20 06:37:42 401a0bf1 kernel: [74665.471619] WARNING: at
drivers/net/wireless/ath/ath9k/rc.c:697
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]()
Jan 20 06:37:42 401a0bf1 kernel: [74665.471623] Hardware name: N53Jn
Jan 20 06:37:42 401a0bf1 kernel: [74665.471625] Modules linked in: ath9k
ath5k xhci_hcd omfs jfs xfs exportfs reiserfs ext2 hfs hfsplus vfat fat
isofs nls_utf8 udf crc_itu_t cryptd aes_x86_64 aes_generic af_packet
snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev v4l2_compat_ioctl32
cdc_phonet phonet bsd_comp ppp_deflate ppp_async crc_ccitt ppp_generic
slhc cdc_acm rtc_cmos configs kvm_intel kvm ide_cd_mod ide_core pktcdvd
pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4 mac80211 ath9k_common
ath9k_hw ath cfg80211 rfkill 8139too mii fuse thermal ac tun usb_storage
usb_libusual cpufreq_conservative speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf fbcon tileblit font bitblit softcursor i915
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd
Jan 20 06:37:42 401a0bf1 kernel: crc16 sr_mod cdrom ahci libahci xtkbd
ohci_hcd uhci_hcd ehci_hcd usbhid hid usbcore usb_common btrfs
zlib_deflate libcrc32c crc32c ext3 jbd mbcache synaptics_i2c i2c_core
sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod dm_mod
unix [last unloaded: xhci_hcd]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471737] Pid: 7032, comm: gw6c
Tainted: G W 3.2.0 #1
Jan 20 06:37:42 401a0bf1 kernel: [74665.471739] Call Trace:
Jan 20 06:37:42 401a0bf1 kernel: [74665.471746]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471746] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471751]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.471751] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 20 06:37:42 401a0bf1 kernel: [74665.471757] [<ffffffffa06c6769>]
ath_rc_get_highest_rix.clone.18+0x159/0x200 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471763] [<ffffffffa06c6896>]
ath_get_rate+0x86/0x480 [ath9k]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471774]
[mac80211:rate_control_get_rate+0x86/0x160]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471774] [<ffffffffa053ea26>]
rate_control_get_rate+0x86/0x160 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471785]
[mac80211:invoke_tx_handlers+0x7fa/0x1170] invoke_tx_handlers+0x7fa/0x1170
[mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471785] [<ffffffffa054849a>]
invoke_tx_handlers+0x7fa/0x1170 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471798]
[double_rq_lock+0x2f/0x60] ? double_rq_lock+0x2f/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.471798] [<ffffffff8103f0df>] ?
double_rq_lock+0x2f/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.471808]
[mac80211:ieee80211_tx+0x5b/0xb0] ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471808] [<ffffffffa0548f6b>]
ieee80211_tx+0x5b/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471818]
[mac80211:ieee80211_xmit+0x87/0xb0] ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471818] [<ffffffffa0549047>]
ieee80211_xmit+0x87/0xb0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471828]
[mac80211:ieee80211_subif_start_xmit+0x36f/0x7e0]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471828] [<ffffffffa05496bf>]
ieee80211_subif_start_xmit+0x36f/0x7e0 [mac80211]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471834] [kfree_skb+0x19/0x40] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.471834] [<ffffffff812ac3d9>] ?
kfree_skb+0x19/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.471838]
[dev_hard_start_xmit+0x275/0x620] dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.471838] [<ffffffff812ba605>]
dev_hard_start_xmit+0x275/0x620
Jan 20 06:37:42 401a0bf1 kernel: [74665.471844]
[sch_direct_xmit+0xe7/0x1b0] sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471844] [<ffffffff812d50d7>]
sch_direct_xmit+0xe7/0x1b0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471848]
[dev_queue_xmit+0x176/0x5d0] dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471848] [<ffffffff812bab26>]
dev_queue_xmit+0x176/0x5d0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471852]
[ip_finish_output+0x173/0x300] ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.471852] [<ffffffff812eeba3>]
ip_finish_output+0x173/0x300
Jan 20 06:37:42 401a0bf1 kernel: [74665.471856] [ip_output+0x98/0xa0]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471856] [<ffffffff812ef6e8>]
ip_output+0x98/0xa0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471860] [ip_local_out+0x24/0x30]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.471860] [<ffffffff812eedf4>]
ip_local_out+0x24/0x30
Jan 20 06:37:42 401a0bf1 kernel: [74665.471864] [ip_send_skb+0x16/0x50]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.471864] [<ffffffff812f00d6>]
ip_send_skb+0x16/0x50
Jan 20 06:37:42 401a0bf1 kernel: [74665.471869]
[udp_send_skb+0x108/0x380] udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.471869] [<ffffffff81311758>]
udp_send_skb+0x108/0x380
Jan 20 06:37:42 401a0bf1 kernel: [74665.471873]
[ipv4_dst_check+0x39/0x40] ? ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.471873] [<ffffffff812e6749>] ?
ipv4_dst_check+0x39/0x40
Jan 20 06:37:42 401a0bf1 kernel: [74665.471878] [pollwake+0x0/0x60] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471878] [<ffffffff811179f0>] ?
__pollwait+0xf0/0xf0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471882]
[ip_generic_getfrag+0x0/0xb0] ? ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.471882] [<ffffffff812ed1b0>] ?
ip_setup_cork+0x140/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.471887] [udp_sendmsg+0x32a/0x910]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.471887] [<ffffffff813137da>]
udp_sendmsg+0x32a/0x910
Jan 20 06:37:42 401a0bf1 kernel: [74665.471892] [inet_sendmsg+0x5f/0xb0]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471892] [<ffffffff8131cd7f>]
inet_sendmsg+0x5f/0xb0
Jan 20 06:37:42 401a0bf1 kernel: [74665.471897]
[kmem_cache_free+0x15/0x90] ? kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.471897] [<ffffffff810fa7b5>] ?
kmem_cache_free+0x15/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.471902] [sock_sendmsg+0xea/0x120]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.471902] [<ffffffff812a3b8a>]
sock_sendmsg+0xea/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.471909]
[tun:tun_chr_aio_read+0x79/0xd0] ? tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471909] [<ffffffffa0450499>] ?
tun_chr_aio_read+0x79/0xd0 [tun]
Jan 20 06:37:42 401a0bf1 kernel: [74665.471914] [do_sync_read+0xda/0x120]
? do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.471914] [<ffffffff811052da>] ?
do_sync_read+0xda/0x120
Jan 20 06:37:42 401a0bf1 kernel: [74665.471919]
[lock_hrtimer_base.clone.35+0x2b/0x60] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.471919] [<ffffffff8106c6fb>] ?
lock_hrtimer_base.clone.35+0x2b/0x60
Jan 20 06:37:42 401a0bf1 kernel: [74665.471924]
[sockfd_lookup_light+0x24/0x90] ? sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.471924] [<ffffffff812a2bb4>] ?
sockfd_lookup_light+0x24/0x90
Jan 20 06:37:42 401a0bf1 kernel: [74665.471928] [sys_sendto+0x104/0x140]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.471928] [<ffffffff812a5c54>]
sys_sendto+0x104/0x140
Jan 20 06:37:42 401a0bf1 kernel: [74665.471934]
[system_call_fastpath+0x16/0x1b] system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.471934] [<ffffffff8135cd92>]
system_call_fastpath+0x16/0x1b
Jan 20 06:37:42 401a0bf1 kernel: [74665.471937] ---[ end trace
d38cf8ad260b1375 ]---
Jan 20 06:37:42 401a0bf1 kernel: [74665.570722] ------------[ cut here ]--
----------
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-18 17:30 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-18 17:30 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> 2012/1/18 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
>> > I wonder if maybe a congested AP could help.. But unclear how to
>obtain
> > > that quickly and reliably.
> >
> > Even with debugging off WiFi works reliably across different
conditions.
> >
>
> you can test frequent roaming with the attached script. also you can
> test roaming, after enabling ASPM(attached script, courtesy: Luis)
> please completely read and understand
> http://linuxwireless.org/en/users/Documentation/ASPM
> incorrect tweak may cause hardware issues.
Well, when I got the failure, exactly one roaming attempt happenned...
ASPM seems disabled and from what I understood, it is a Bad Idea to enable
it before fully understanding why exactly it was disabled. I have no time to
acquire this understanding now.
I read the roaming script. I need to get the scan results and then issue
"roam" in loop between all the APs I can access, right? Will try just to
collect some new testing data.
Thanks for the patch - looks like it works fine so far.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-17 18:53 MR
@ 2012-01-18 5:32 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-18 5:32 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
2012/1/18 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > Turned out I got lucky previous time.
> > >
> > >This time I went to the other AP, spent some time under it, roamed
> back
> > and
> > >
> > >WiFi didn't disappear. I didn't even lose XMPP connections in the
> > process.
> > >
> > >
> > >Maybe debug printing (which prints a lot) managed to introduce some
> > extra
> > > delays into some race condition.
> > >
> > > I hope I will have time to test this more on Monday. Tomorrow I will
> be
> >
> > > using WiFi less than usual.
> >
> >Now I went a few time back and forth, spent a lot of time under
> previously
> >
> > risky AP and still there are no problems..
> >
> > I wonder if maybe a congested AP could help.. But unclear how to obtain
> > that quickly and reliably.
>
> Even with debugging off WiFi works reliably across different conditions.
>
you can test frequent roaming with the attached script. also you can
test roaming, after enabling ASPM(attached script, courtesy: Luis)
please completely read and understand
http://linuxwireless.org/en/users/Documentation/ASPM
incorrect tweak may cause hardware issues.
--
shafi
[-- Attachment #2: roam-script.sh --]
[-- Type: application/x-sh, Size: 2008 bytes --]
[-- Attachment #3: enable-aspm --]
[-- Type: application/octet-stream, Size: 7310 bytes --]
#!/bin/bash
# Copyright (c) 2010 Luis R. Rodriguez <mcgrof@gmail.com>
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
# ASPM Tuning script
#
# This script lets you enable ASPM on your devices in case your BIOS
# does not have it enabled for some reason. If your BIOS does not have
# it enabled it is usually for a good reason so you should only use this if
# you know what you are doing. Typically you would only need to enable
# ASPM manually when doing development and using a card that typically
# is not present on a laptop, or using the cardbus slot. The BIOS typically
# disables ASPM for foreign cards and on the cardbus slot. Check also
# if you may need to do other things than what is below on your vendor
# documentation.
#
# To use this script You will need for now to at least query your device
# PCI endpoint and root complex addresses using the convention output by
# lspci: [<bus>]:[<slot>].[<func>]
#
# For example:
#
# 03:00.0 Network controller: Atheros Communications Inc. AR9300 Wireless LAN adaptor (rev 01
# 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
#
# The root complex for the endpoint can be found using lspci -t
#
# For more details refer to:
#
# http://wireless.kernel.org/en/users/Documentation/ASPM
# You just need to modify these three values:
ROOT_COMPLEX="00:1c.3"
ENDPOINT="05:00.0"
# We'll only enable the last 2 bits by using a mask
# of :3 to setpci, this will ensure we keep the existing
# values on the byte.
#
# Hex Binary Meaning
# -------------------------
# 0 0b00 L0 only
# 1 0b01 L0s only
# 2 0b10 L1 only
# 3 0b11 L1 and L0s
ASPM_SETTING=2
function aspm_setting_to_string()
{
case $1 in
0)
echo -e "\t${BLUE}L0 only${NORMAL}, ${RED}ASPM disabled${NORMAL}"
;;
1)
;;
2)
echo -e "\t${GREEN}L1 only${NORMAL}"
;;
3)
echo -e "\t${GREEN}L1 and L0s${NORMAL}"
;;
*)
echo -e "\t${RED}Invalid${NORMAL}"
;;
esac
}
###################################################################
# Do not edit below here unless you are sending me a patch
###################################################################
#
# TODO: patches are welcomed to me until we submit to to
# PCI Utilities upstream.
#
# This can be improved by in this order:
#
# * Accept arguments for endpoint and root complex address, and
# desired ASPM settings
# * Look for your ASPM capabilities by quering your
# LnkCap register first. Use these values to let you
# select whether you want to enable only L1 or L1 & L0s
# * Searching for your root complex for you
# * Search for your PCI device by using the driver
# * Disable your driver and ask to reboot ?
# * Rewrite in C
# * Write ncurses interface [ wishlist ]
# * Write GTK/QT interface [ wishlist ]
# * Submit upstream as aspm.c to the PCI Utilities, which are
# maintained by Martin Mares <mj@ucw.cz>
# Pretty colors
GREEN="\033[01;32m"
YELLOW="\033[01;33m"
NORMAL="\033[00m"
BLUE="\033[34m"
RED="\033[31m"
PURPLE="\033[35m"
CYAN="\033[36m"
UNDERLINE="\033[02m"
# we can surely read the spec to get a better value
MAX_SEARCH=20
SEARCH_COUNT=1
ASPM_BYTE_ADDRESS="INVALID"
ROOT_PRESENT=$(lspci | grep -c "$ROOT_COMPLEXT")
ENDPOINT_PRESENT=$(lspci | grep -c "$ENDPOINT")
if [[ $(id -u) != 0 ]]; then
echo "This needs to be run as root"
exit 1
fi
if [[ $ROOT_PRESENT -eq 0 ]]; then
echo "Root complex $ROOT_COMPLEX is not present"
exit
fi
if [[ $ENDPOINT_PRESENT -eq 0 ]]; then
echo "Endpoint $ENDPOINT is not present"
exit
fi
# XXX: lspci -s some_device_not_existing does not return positive
# if the device does not exist, fix this upstream
function device_present()
{
PRESENT=$(lspci | grep -c "$1")
COMPLAINT="${RED}not present${NORMAL}"
if [[ $PRESENT -eq 0 ]]; then
if [[ $2 != "present" ]]; then
COMPLAINT="${RED}disappeared${NORMAL}"
fi
echo -e "Device ${BLUE}${1}${NORMAL} $COMPLAINT"
return 1
fi
return 0
}
function find_aspm_byte_address()
{
device_present $ENDPOINT present
if [[ $? -ne 0 ]]; then
exit
fi
SEARCH=$(setpci -s $1 34.b)
# We know on the first search $SEARCH will not be
# 10 but this simplifies the implementation.
while [[ $SEARCH != 10 && $SEARCH_COUNT -le $MAX_SEARCH ]]; do
END_SEARCH=$(setpci -s $1 ${SEARCH}.b)
# Convert hex digits to uppercase for bc
SEARCH_UPPER=$(printf "%X" 0x${SEARCH})
if [[ $END_SEARCH = 10 ]]; then
ASPM_BYTE_ADDRESS=$(echo "obase=16; ibase=16; $SEARCH_UPPER + 10" | bc)
break
fi
SEARCH=$(echo "obase=16; ibase=16; $SEARCH + 1" | bc)
SEARCH=$(setpci -s $1 ${SEARCH}.b)
let SEARCH_COUNT=$SEARCH_COUNT+1
done
if [[ $SEARCH_COUNT -ge $MAX_SEARCH ]]; then
echo -e "Long loop while looking for ASPM word for $1"
return 1
fi
return 0
}
function enable_aspm_byte()
{
device_present $1 present
if [[ $? -ne 0 ]]; then
exit
fi
find_aspm_byte_address $1
if [[ $? -ne 0 ]]; then
return 1
fi
ASPM_BYTE_HEX=$(setpci -s $1 ${ASPM_BYTE_ADDRESS}.b)
ASPM_BYTE_HEX=$(printf "%X" 0x${ASPM_BYTE_HEX})
# setpci doesn't support a mask on the query yet, only on the set,
# so to verify a setting on a mask we have no other optoin but
# to do do this stuff ourselves.
DESIRED_ASPM_BYTE_HEX=$(printf "%X" $(( (0x${ASPM_BYTE_HEX} & ~0x7) |0x${ASPM_SETTING})))
if [[ $ASPM_BYTE_ADDRESS = "INVALID" ]]; then
echo -e "No ASPM byte could be found for $(lspci -s $1)"
return
fi
echo -e "$(lspci -s $1)"
echo -en "\t${YELLOW}0x${ASPM_BYTE_ADDRESS}${NORMAL} : ${CYAN}0x${ASPM_BYTE_HEX}${GREEN} --> ${BLUE}0x${DESIRED_ASPM_BYTE_HEX}${NORMAL} ... "
device_present $1 present
if [[ $? -ne 0 ]]; then
exit
fi
# Avoid setting if already set
if [[ $ASPM_BYTE_HEX = $DESIRED_ASPM_BYTE_HEX ]]; then
echo -e "[${GREEN}SUCESS${NORMAL}] (${GREEN}already set${NORMAL})"
aspm_setting_to_string $ASPM_SETTING
return 0
fi
# This only writes the last 3 bits
setpci -s $1 ${ASPM_BYTE_ADDRESS}.b=${ASPM_SETTING}:3
sleep 3
ACTUAL_ASPM_BYTE_HEX=$(setpci -s $1 ${ASPM_BYTE_ADDRESS}.b)
ACTUAL_ASPM_BYTE_HEX=$(printf "%X" 0x${ACTUAL_ASPM_BYTE_HEX})
# Do not retry this if it failed, if it failed to set.
# Likey if it failed its a good reason and you should look
# into that.
if [[ $ACTUAL_ASPM_BYTE_HEX != $DESIRED_ASPM_BYTE_HEX ]]; then
echo -e "\t[${RED}FAIL${NORMAL}] (0x${ACTUAL_ASPM_BYTE_HEX})"
return 1
fi
echo -e "\t[${GREEN}SUCCESS]${NORMAL}]"
aspm_setting_to_string $ASPM_SETTING
return 0
}
device_present $ENDPOINT not_sure
if [[ $? -ne 0 ]]; then
exit
fi
echo -e "${CYAN}Root complex${NORMAL}:"
enable_aspm_byte $ROOT_COMPLEX
echo
echo -e "${CYAN}Endpoint${NORMAL}:"
enable_aspm_byte $ENDPOINT
echo
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-17 18:53 MR
2012-01-18 5:32 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-17 18:53 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> > Turned out I got lucky previous time.
> >
> >This time I went to the other AP, spent some time under it, roamed
back
> and
> >
> >WiFi didn't disappear. I didn't even lose XMPP connections in the
> process.
> >
> >
> >Maybe debug printing (which prints a lot) managed to introduce some
> extra
> > delays into some race condition.
> >
> > I hope I will have time to test this more on Monday. Tomorrow I will
be
>
> > using WiFi less than usual.
>
>Now I went a few time back and forth, spent a lot of time under
previously
>
> risky AP and still there are no problems..
>
> I wonder if maybe a congested AP could help.. But unclear how to obtain
> that quickly and reliably.
Even with debugging off WiFi works reliably across different conditions.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-16 15:52 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-16 15:52 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> Turned out I got lucky previous time.
>
>This time I went to the other AP, spent some time under it, roamed back
and
>
>WiFi didn't disappear. I didn't even lose XMPP connections in the
process.
>
>
>Maybe debug printing (which prints a lot) managed to introduce some
extra
> delays into some race condition.
>
> I hope I will have time to test this more on Monday. Tomorrow I will be
> using WiFi less than usual.
Now I went a few time back and forth, spent a lot of time under previously
risky AP and still there are no problems..
I wonder if maybe a congested AP could help.. But unclear how to obtain
that quickly and reliably.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-12 18:04 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-12 18:04 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> 2012/1/11 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> >> does roaming seems to trigger this issue consistently ?
> >> . please provide the logs
> >> sudo modprobe -v ath9k debug=0xffffffff
> >> http://linuxwireless.org/en/users/Drivers/ath9k/debug
> >
> > As I need to rebuild for CONFIG_ATH_DEBUG: should I check the
allegedely
> > proper fix or wide-angle code removal first?
>
> please check with the proper fix
Turned out I got lucky previous time.
This time I went to the other AP, spent some time under it, roamed back and
WiFi didn't disappear. I didn't even lose XMPP connections in the process.
Maybe debug printing (which prints a lot) managed to introduce some extra
delays into some race condition.
I hope I will have time to test this more on Monday. Tomorrow I will be
using WiFi less than usual.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-11 17:20 MR
@ 2012-01-12 6:06 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-12 6:06 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
2012/1/11 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
>> does roaming seems to trigger this issue consistently ?
>> . please provide the logs
>> sudo modprobe -v ath9k debug=0xffffffff
>> http://linuxwireless.org/en/users/Drivers/ath9k/debug
>
> As I need to rebuild for CONFIG_ATH_DEBUG: should I check the allegedely
> proper fix or wide-angle code removal first?
please check with the proper fix
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-11 17:20 MR
2012-01-12 6:06 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-11 17:20 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> does roaming seems to trigger this issue consistently ?
> . please provide the logs
> sudo modprobe -v ath9k debug=0xffffffff
> http://linuxwireless.org/en/users/Drivers/ath9k/debug
As I need to rebuild for CONFIG_ATH_DEBUG: should I check the allegedely
proper fix or wide-angle code removal first?
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-10 18:14 MR
@ 2012-01-11 15:26 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-11 15:26 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
2012/1/10 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > >> So, I am building 3.2 with two patches: over/under-flow catcher (pity
> > >that
> >>> it seems to be on a multiple-times-per-second codepath and just leaving
> > >the
> >> > checks there for everyone is suboptimal) and allegedely proper fix.
> >Both
> > > > applied OK with a small offset.
> > >
> > > as per our assumption, we should not see those over/underflow errors,
> > > with the patch
> > > above mentioned. please let us know if you hit upon this warnings,
> > > even after the proper fix.
> >
> > 2 hours in. It looks like 10%-20% throughput loss (both up and down with
> >similar ratio) relative to "remove suspicious code" build. It may be some
> >other change, of course (slightly moving the notebook, removing USB device
> >
> > charging from the notebook or something like that)
>
> Seems to be AP-dependent.
>
> I spent entire day on one AP with no problems, went across the building,
> roamed (went offline, found new AP) succesfully, and then ten minutes later:
> (logs saved)
does roaming seems to trigger this issue consistently ?
. please provide the logs
sudo modprobe -v ath9k debug=0xffffffff
http://linuxwireless.org/en/users/Drivers/ath9k/debug
>
> Jan 10 10:35:57 401a0bf1 kernel: [ 7681.407314] wlan0: deauthenticating from
> 00:19:5b:be:3c:a7 by local choice (reason=3)
> Jan 10 10:35:57 401a0bf1 kernel: [ 7681.427485] cfg80211: Calling CRDA to
> update world regulatory domain
> Jan 10 10:35:57 401a0bf1 kernel: [ 7681.694908] ADDRCONF(NETDEV_UP): wlan0:
> link is not ready
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.545018] wlan0: authenticate with
> 00:19:5b:be:3c:a7 (try 1)
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.546922] wlan0: authenticated
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.546954] wlan0: associate with
> 00:19:5b:be:3c:a7 (try 1)
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549414] wlan0: RX AssocResp from
> 00:19:5b:be:3c:a7 (capab=0x431 status=0 aid=1)
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549421] wlan0: associated
> Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549900] ADDRCONF(NETDEV_CHANGE):
> wlan0: link becomes ready
> Jan 10 10:36:09 401a0bf1 kernel: [ 7693.095841] wlan0: no IPv6 routers
> present
> Jan 10 21:01:14 401a0bf1 kernel: [45162.286679] cfg80211: Calling CRDA to
> update world regulatory domain
> Jan 10 21:01:14 401a0bf1 kernel: [45163.155037] wlan0: authenticate with
> 00:24:8c:81:e1:76 (try 1)
> Jan 10 21:01:14 401a0bf1 kernel: [45163.157132] wlan0: authenticated
> Jan 10 21:01:14 401a0bf1 kernel: [45163.157159] wlan0: associate with
> 00:24:8c:81:e1:76 (try 1)
> Jan 10 21:01:14 401a0bf1 kernel: [45163.159708] wlan0: RX AssocResp from
> 00:24:8c:81:e1:76 (capab=0x411 status=0 aid=2)
> Jan 10 21:01:14 401a0bf1 kernel: [45163.159713] wlan0: associated
> Jan 10 21:34:32 401a0bf1 kernel: [47159.166426] ath: Failed to wakeup in
> 500us
> Jan 10 21:34:34 401a0bf1 kernel: [47160.506049] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:34:34 401a0bf1 kernel: [47160.518977] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:34:34 401a0bf1 kernel: [47160.518982] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:34:34 401a0bf1 kernel: [47160.635143] ath: Chip reset failed
> Jan 10 21:34:34 401a0bf1 kernel: [47160.635146] ath: Unable to reset
> channel, reset status -22
> Jan 10 21:34:34 401a0bf1 kernel: [47161.226194] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:34:34 401a0bf1 kernel: [47161.239098] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:34:34 401a0bf1 kernel: [47161.239103] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
>
>
> Jan 10 21:42:53 401a0bf1 kernel: [47659.159537] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:42:53 401a0bf1 kernel: [47659.172508] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:42:53 401a0bf1 kernel: [47659.172510] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:42:53 401a0bf1 kernel: [47659.288040] ath: Chip reset failed
> Jan 10 21:42:53 401a0bf1 kernel: [47659.288045] ath: Unable to reset
> channel, reset status -22
> Jan 10 21:42:53 401a0bf1 kernel: [47659.288091] ath: Unable to set channel
> Jan 10 21:42:53 401a0bf1 kernel: [47659.353999] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:42:53 401a0bf1 kernel: [47659.366852] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:42:53 401a0bf1 kernel: [47659.366857] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:42:53 401a0bf1 kernel: [47659.482275] ath: Chip reset failed
> Jan 10 21:42:53 401a0bf1 kernel: [47659.482280] ath: Unable to reset
> channel, reset status -22
> Jan 10 21:42:53 401a0bf1 kernel: [47659.482302] ath: Unable to set channel
> Jan 10 21:42:53 401a0bf1 kernel: [47659.548509] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:42:53 401a0bf1 kernel: [47659.561477] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:42:53 401a0bf1 kernel: [47659.561481] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:42:53 401a0bf1 kernel: [47659.677601] ath: Chip reset failed
> Jan 10 21:42:53 401a0bf1 kernel: [47659.677604] ath: Unable to reset channel
> (2462 MHz), reset status -22
> Jan 10 21:42:54 401a0bf1 kernel: [47660.682084] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.231280] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.245756] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.273456] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.284277] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.349214] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:42:55 401a0bf1 kernel: [47661.362013] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:42:55 401a0bf1 kernel: [47661.362016] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:42:55 401a0bf1 kernel: [47661.604443] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:55 401a0bf1 kernel: [47661.670201] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 10 21:42:55 401a0bf1 kernel: [47661.683148] ath: DMA failed to stop in
> 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 10 21:42:55 401a0bf1 kernel: [47661.683152] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 10 21:42:55 401a0bf1 kernel: [47661.799038] ath: Chip reset failed
> Jan 10 21:42:55 401a0bf1 kernel: [47661.799043] ath: Unable to reset channel
> (2462 MHz), reset status -22
> Jan 10 21:42:56 401a0bf1 kernel: [47662.373472] ath: Failed to wakeup in
> 500us
> Jan 10 21:42:56 401a0bf1 kernel: [47662.489762] ath: Chip reset failed
> Jan 10 21:42:56 401a0bf1 kernel: [47662.489769] ath: Unable to reset
> hardware; reset status -22 (freq 2462 MHz)
> Jan 10 21:42:59 401a0bf1 kernel: [47665.685279] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:04 401a0bf1 kernel: [47670.688494] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:09 401a0bf1 kernel: [47675.675943] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:14 401a0bf1 kernel: [47680.663071] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:19 401a0bf1 kernel: [47685.666297] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:24 401a0bf1 kernel: [47690.669649] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:25 401a0bf1 kernel: [47691.020335] ath: Failed to wakeup in
> 500us
> Jan 10 21:43:25 401a0bf1 kernel: [47691.135856] ath: Chip reset failed
> Jan 10 21:43:25 401a0bf1 kernel: [47691.135861] ath: Unable to reset
> hardware; reset status -22 (freq 2462 MHz)
> Jan 10 21:43:29 401a0bf1 kernel: [47695.656864] ath: Failed to wakeup in
> 500us
>
>
>
> Jan 10 21:44:01 401a0bf1 kernel: [47727.484465] ath9k: Driver unloaded
> Jan 10 21:44:04 401a0bf1 kernel: [47729.913403] ath9k 0000:03:00.0: enabling
> device (0000 -> 0002)
> Jan 10 21:44:04 401a0bf1 kernel: [47729.913414] ath9k 0000:03:00.0: PCI INT
> A -> GSI 17 (level, low) -> IRQ 17
> Jan 10 21:44:04 401a0bf1 kernel: [47729.913427] ath9k 0000:03:00.0: setting
> latency timer to 64
> Jan 10 21:44:04 401a0bf1 kernel: [47730.028960] ath: Couldn't reset chip
> Jan 10 21:44:04 401a0bf1 kernel: [47730.028963] ath: Unable to initialize
> hardware; initialization status: -5
> Jan 10 21:44:04 401a0bf1 kernel: [47730.028968] ath9k 0000:03:00.0: Failed
> to initialize device
> Jan 10 21:44:04 401a0bf1 kernel: [47730.029010] ath9k 0000:03:00.0: PCI INT
> A disabled
> Jan 10 21:44:04 401a0bf1 kernel: [47730.029033] ath9k: probe of 0000:03:00.0
> failed with error -5
>
>
>
> 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
> Network Adapter (PCI-Express) (rev 01)
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [40] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-
> ,D3hot+,D3cold-)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
> Address: 00000000 Data: 0000
> Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> <128ns, L1 <2us
> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
> TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 <512ns, L1 <64us
> ClockPM- Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> CommClk-
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
> DevCap2: Completion Timeout: Not Supported, TimeoutDis+
> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
> LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
> SpeedDis-, Selectable De-emphasis: -6dB
> Transmit Margin: Normal Operating Range,
> EnterModifiedCompliance- ComplianceSOS-
> Compliance De-emphasis: -6dB
> LnkSta2: Current De-emphasis Level: -6dB
> Capabilities: [100 v1] Advanced Error Reporting
> UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
> UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
> UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
> CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> NonFatalErr+
> CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
> NonFatalErr+
> AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+
> ChkEn-
> Capabilities: [140 v1] Virtual Channel
> Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
> Arb: Fixed- WRR32- WRR64- WRR128-
> Ctrl: ArbSelect=Fixed
> Status: InProgress-
> VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
> Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
> WRR256-
> Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
> Status: NegoPending- InProgress-
> Capabilities: [160 v1] Device Serial Number 00-00-00-00-00-00-00-00
> Capabilities: [170 v1] Power Budgeting <?>
>
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-10 18:14 MR
2012-01-11 15:26 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-10 18:14 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> >> So, I am building 3.2 with two patches: over/under-flow catcher (pity
> >that
>>> it seems to be on a multiple-times-per-second codepath and just leaving
> >the
>> > checks there for everyone is suboptimal) and allegedely proper fix.
>Both
> > > applied OK with a small offset.
> >
> > as per our assumption, we should not see those over/underflow errors,
> > with the patch
> > above mentioned. please let us know if you hit upon this warnings,
> > even after the proper fix.
>
> 2 hours in. It looks like 10%-20% throughput loss (both up and down with
>similar ratio) relative to "remove suspicious code" build. It may be some
>other change, of course (slightly moving the notebook, removing USB device
>
> charging from the notebook or something like that)
Seems to be AP-dependent.
I spent entire day on one AP with no problems, went across the building,
roamed (went offline, found new AP) succesfully, and then ten minutes later:
(logs saved)
Jan 10 10:35:57 401a0bf1 kernel: [ 7681.407314] wlan0: deauthenticating from
00:19:5b:be:3c:a7 by local choice (reason=3)
Jan 10 10:35:57 401a0bf1 kernel: [ 7681.427485] cfg80211: Calling CRDA to
update world regulatory domain
Jan 10 10:35:57 401a0bf1 kernel: [ 7681.694908] ADDRCONF(NETDEV_UP): wlan0:
link is not ready
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.545018] wlan0: authenticate with
00:19:5b:be:3c:a7 (try 1)
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.546922] wlan0: authenticated
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.546954] wlan0: associate with
00:19:5b:be:3c:a7 (try 1)
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549414] wlan0: RX AssocResp from
00:19:5b:be:3c:a7 (capab=0x431 status=0 aid=1)
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549421] wlan0: associated
Jan 10 10:35:58 401a0bf1 kernel: [ 7682.549900] ADDRCONF(NETDEV_CHANGE):
wlan0: link becomes ready
Jan 10 10:36:09 401a0bf1 kernel: [ 7693.095841] wlan0: no IPv6 routers
present
Jan 10 21:01:14 401a0bf1 kernel: [45162.286679] cfg80211: Calling CRDA to
update world regulatory domain
Jan 10 21:01:14 401a0bf1 kernel: [45163.155037] wlan0: authenticate with
00:24:8c:81:e1:76 (try 1)
Jan 10 21:01:14 401a0bf1 kernel: [45163.157132] wlan0: authenticated
Jan 10 21:01:14 401a0bf1 kernel: [45163.157159] wlan0: associate with
00:24:8c:81:e1:76 (try 1)
Jan 10 21:01:14 401a0bf1 kernel: [45163.159708] wlan0: RX AssocResp from
00:24:8c:81:e1:76 (capab=0x411 status=0 aid=2)
Jan 10 21:01:14 401a0bf1 kernel: [45163.159713] wlan0: associated
Jan 10 21:34:32 401a0bf1 kernel: [47159.166426] ath: Failed to wakeup in
500us
Jan 10 21:34:34 401a0bf1 kernel: [47160.506049] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:34:34 401a0bf1 kernel: [47160.518977] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:34:34 401a0bf1 kernel: [47160.518982] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:34:34 401a0bf1 kernel: [47160.635143] ath: Chip reset failed
Jan 10 21:34:34 401a0bf1 kernel: [47160.635146] ath: Unable to reset
channel, reset status -22
Jan 10 21:34:34 401a0bf1 kernel: [47161.226194] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:34:34 401a0bf1 kernel: [47161.239098] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:34:34 401a0bf1 kernel: [47161.239103] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:53 401a0bf1 kernel: [47659.159537] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:42:53 401a0bf1 kernel: [47659.172508] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:42:53 401a0bf1 kernel: [47659.172510] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:53 401a0bf1 kernel: [47659.288040] ath: Chip reset failed
Jan 10 21:42:53 401a0bf1 kernel: [47659.288045] ath: Unable to reset
channel, reset status -22
Jan 10 21:42:53 401a0bf1 kernel: [47659.288091] ath: Unable to set channel
Jan 10 21:42:53 401a0bf1 kernel: [47659.353999] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:42:53 401a0bf1 kernel: [47659.366852] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:42:53 401a0bf1 kernel: [47659.366857] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:53 401a0bf1 kernel: [47659.482275] ath: Chip reset failed
Jan 10 21:42:53 401a0bf1 kernel: [47659.482280] ath: Unable to reset
channel, reset status -22
Jan 10 21:42:53 401a0bf1 kernel: [47659.482302] ath: Unable to set channel
Jan 10 21:42:53 401a0bf1 kernel: [47659.548509] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:42:53 401a0bf1 kernel: [47659.561477] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:42:53 401a0bf1 kernel: [47659.561481] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:53 401a0bf1 kernel: [47659.677601] ath: Chip reset failed
Jan 10 21:42:53 401a0bf1 kernel: [47659.677604] ath: Unable to reset channel
(2462 MHz), reset status -22
Jan 10 21:42:54 401a0bf1 kernel: [47660.682084] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.231280] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.245756] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.273456] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.284277] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.349214] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:42:55 401a0bf1 kernel: [47661.362013] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:42:55 401a0bf1 kernel: [47661.362016] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:55 401a0bf1 kernel: [47661.604443] ath: Failed to wakeup in
500us
Jan 10 21:42:55 401a0bf1 kernel: [47661.670201] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 10 21:42:55 401a0bf1 kernel: [47661.683148] ath: DMA failed to stop in
10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 10 21:42:55 401a0bf1 kernel: [47661.683152] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 10 21:42:55 401a0bf1 kernel: [47661.799038] ath: Chip reset failed
Jan 10 21:42:55 401a0bf1 kernel: [47661.799043] ath: Unable to reset channel
(2462 MHz), reset status -22
Jan 10 21:42:56 401a0bf1 kernel: [47662.373472] ath: Failed to wakeup in
500us
Jan 10 21:42:56 401a0bf1 kernel: [47662.489762] ath: Chip reset failed
Jan 10 21:42:56 401a0bf1 kernel: [47662.489769] ath: Unable to reset
hardware; reset status -22 (freq 2462 MHz)
Jan 10 21:42:59 401a0bf1 kernel: [47665.685279] ath: Failed to wakeup in
500us
Jan 10 21:43:04 401a0bf1 kernel: [47670.688494] ath: Failed to wakeup in
500us
Jan 10 21:43:09 401a0bf1 kernel: [47675.675943] ath: Failed to wakeup in
500us
Jan 10 21:43:14 401a0bf1 kernel: [47680.663071] ath: Failed to wakeup in
500us
Jan 10 21:43:19 401a0bf1 kernel: [47685.666297] ath: Failed to wakeup in
500us
Jan 10 21:43:24 401a0bf1 kernel: [47690.669649] ath: Failed to wakeup in
500us
Jan 10 21:43:25 401a0bf1 kernel: [47691.020335] ath: Failed to wakeup in
500us
Jan 10 21:43:25 401a0bf1 kernel: [47691.135856] ath: Chip reset failed
Jan 10 21:43:25 401a0bf1 kernel: [47691.135861] ath: Unable to reset
hardware; reset status -22 (freq 2462 MHz)
Jan 10 21:43:29 401a0bf1 kernel: [47695.656864] ath: Failed to wakeup in
500us
Jan 10 21:44:01 401a0bf1 kernel: [47727.484465] ath9k: Driver unloaded
Jan 10 21:44:04 401a0bf1 kernel: [47729.913403] ath9k 0000:03:00.0: enabling
device (0000 -> 0002)
Jan 10 21:44:04 401a0bf1 kernel: [47729.913414] ath9k 0000:03:00.0: PCI INT
A -> GSI 17 (level, low) -> IRQ 17
Jan 10 21:44:04 401a0bf1 kernel: [47729.913427] ath9k 0000:03:00.0: setting
latency timer to 64
Jan 10 21:44:04 401a0bf1 kernel: [47730.028960] ath: Couldn't reset chip
Jan 10 21:44:04 401a0bf1 kernel: [47730.028963] ath: Unable to initialize
hardware; initialization status: -5
Jan 10 21:44:04 401a0bf1 kernel: [47730.028968] ath9k 0000:03:00.0: Failed
to initialize device
Jan 10 21:44:04 401a0bf1 kernel: [47730.029010] ath9k 0000:03:00.0: PCI INT
A disabled
Jan 10 21:44:04 401a0bf1 kernel: [47730.029033] ath9k: probe of 0000:03:00.0
failed with error -5
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
Network Adapter (PCI-Express) (rev 01)
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 17
Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-
,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000 Data: 0000
Capabilities: [60] Express (v2) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<128ns, L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1,
Latency L0 <512ns, L1 <64us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance-
SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
NonFatalErr+
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+
ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128-
WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [170 v1] Power Budgeting <?>
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-09 11:11 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-09 11:11 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
>> So, I am building 3.2 with two patches: over/under-flow catcher (pity
>that
>> it seems to be on a multiple-times-per-second codepath and just leaving
>the
> > checks there for everyone is suboptimal) and allegedely proper fix. Both
> > applied OK with a small offset.
>
> as per our assumption, we should not see those over/underflow errors,
> with the patch
> above mentioned. please let us know if you hit upon this warnings,
> even after the proper fix.
2 hours in. It looks like 10%-20% throughput loss (both up and down with
similar ratio) relative to "remove suspicious code" build. It may be some
other change, of course (slightly moving the notebook, removing USB device
charging from the notebook or something like that)
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-09 7:40 MR
@ 2012-01-09 7:57 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-09 7:57 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
2012/1/9 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> >> So, I am building 3.2 with two patches: over/under-flow catcher (pity
> >that
> >> it seems to be on a multiple-times-per-second codepath and just leaving
> >the
> > > checks there for everyone is suboptimal) and allegedely proper fix. Both
> > > applied OK with a small offset.
> >
> > as per our assumption, we should not see those over/underflow errors,
> > with the patch
> > above mentioned. please let us know if you hit upon this warnings,
> > even after the proper fix.
>
> In my experience (and as I understand the situation) if garbage is writen to
> the "chan", it is caught by the check and device is dead-until-reboot anyway.
> On 3.0, even without checks device was dead-until-reboot, but no crash
> happened. All these checks do is converting "panic" to "WiFi broken" for 3.2.
>
true those checks are to confirm that 'chan' is corrupted and the
patch is to fix it.
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-09 7:40 MR
2012-01-09 7:57 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-09 7:40 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
>> So, I am building 3.2 with two patches: over/under-flow catcher (pity
>that
>> it seems to be on a multiple-times-per-second codepath and just leaving
>the
> > checks there for everyone is suboptimal) and allegedely proper fix. Both
> > applied OK with a small offset.
>
> as per our assumption, we should not see those over/underflow errors,
> with the patch
> above mentioned. please let us know if you hit upon this warnings,
> even after the proper fix.
In my experience (and as I understand the situation) if garbage is writen to
the "chan", it is caught by the check and device is dead-until-reboot anyway.
On 3.0, even without checks device was dead-until-reboot, but no crash
happened. All these checks do is converting "panic" to "WiFi broken" for 3.2.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-09 7:05 MR
@ 2012-01-09 7:30 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-09 7:30 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
2012/1/9 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
>
> > > Around 23 hours have elapsed.
> > >
> >> WiFi seems to be working 100% of time. It is always at least lightly
> >loaded.
>
> 45h - all OK.
>
> > great and thanks a lot for testing!
>
> Doesn't really require _doing_ anything except building patched kernels. And
> it is in my best interest to test the driver for the WiFi card I use...
>
> > rather than removing the suspicious code
> > this is properly fixed by us with this patch.
> > http://marc.info/?l=linux-wireless&m=132595161516806&w=2
>
> Ah, I saw the message and wondered whether it is the fix I needed and what
> patches should I apply.
>
> So, I am building 3.2 with two patches: over/under-flow catcher (pity that
> it seems to be on a multiple-times-per-second codepath and just leaving the
> checks there for everyone is suboptimal) and allegedely proper fix. Both
> applied OK with a small offset.
as per our assumption, we should not see those over/underflow errors,
with the patch
above mentioned. please let us know if you hit upon this warnings,
even after the proper fix.
>
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-09 7:05 MR
2012-01-09 7:30 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-09 7:05 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
> > Around 23 hours have elapsed.
> >
>> WiFi seems to be working 100% of time. It is always at least lightly
>loaded.
45h - all OK.
> great and thanks a lot for testing!
Doesn't really require _doing_ anything except building patched kernels. And
it is in my best interest to test the driver for the WiFi card I use...
> rather than removing the suspicious code
> this is properly fixed by us with this patch.
> http://marc.info/?l=linux-wireless&m=132595161516806&w=2
Ah, I saw the message and wondered whether it is the fix I needed and what
patches should I apply.
So, I am building 3.2 with two patches: over/under-flow catcher (pity that
it seems to be on a multiple-times-per-second codepath and just leaving the
checks there for everyone is suboptimal) and allegedely proper fix. Both
applied OK with a small offset.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-08 7:19 MR
@ 2012-01-09 5:11 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-09 5:11 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless, Rajkumar Manoharan
2012/1/8 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > *does the other patch which remove some suspicious looking code, to
> > > see if it improves the situation and avoids the warnings itself.
> >
> >I have built and loaded the kernel with this patch. I even have netconsole
> >
> > apparently working. But ten hours have not elapsed yet. So far so good.
> >
> > If it works till the 10th, I will test it with roaming, too.
>
> Around 23 hours have elapsed.
>
> WiFi seems to be working 100% of time. It is always at least lightly loaded.
>
> Speedtests seems to gve slightly better upload results than I remember with
> 2.6.* (and I have a good enough ISP for WiFi to be the weakest link), so it
> doesn't seem to be a performance regression, either.
great and thanks a lot for testing!
rather than removing the suspicious code
this is properly fixed by us with this patch.
http://marc.info/?l=linux-wireless&m=132595161516806&w=2
you can download the raw message. please report back if you again
get the issue.
>
> As for roaming while connected - I will try not to forget to test it on the
> 10th.
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-08 7:19 MR
2012-01-09 5:11 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-08 7:19 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> > *does the other patch which remove some suspicious looking code, to
> > see if it improves the situation and avoids the warnings itself.
>
>I have built and loaded the kernel with this patch. I even have netconsole
>
> apparently working. But ten hours have not elapsed yet. So far so good.
>
> If it works till the 10th, I will test it with roaming, too.
Around 23 hours have elapsed.
WiFi seems to be working 100% of time. It is always at least lightly loaded.
Speedtests seems to gve slightly better upload results than I remember with
2.6.* (and I have a good enough ISP for WiFi to be the weakest link), so it
doesn't seem to be a performance regression, either.
As for roaming while connected - I will try not to forget to test it on the
10th.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-07 12:11 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-07 12:11 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> thanks for the providing the log. it looks like there is some other
> problem in doing the chip reset and
>eventually when we get into ath_update_survey_stats we are hitting the
>panic.
> you can try two things:
>
> *after these WARNINGS, is your card in some stable state?. are you
> able to see it in lspci(ie does it gets disappeared) and still
> continue your wifi operation. if not then there is some other problem
> while the panic is a symptom of it.
There is another failure mode.
I think rmmod/modprobe says all:
Jan 7 00:25:04 401a0bf1 kernel: [ 5373.686727] ath9k: Driver unloaded
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.441778] ath9k 0000:03:00.0: enabling
device (0000 -> 0002)
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.441789] ath9k 0000:03:00.0: PCI INT A
-> GSI 17 (level, low) -> IRQ 17
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.441802] ath9k 0000:03:00.0: setting
latency timer to 64
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.558038] ath: Couldn't reset chip
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.558042] ath: Unable to initialize
hardware; initialization status: -5
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.558048] ath9k 0000:03:00.0: Failed to
initialize device
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.558092] ath9k 0000:03:00.0: PCI INT A
disabled
Jan 7 00:25:07 401a0bf1 kernel: [ 5376.558259] ath9k: probe of 0000:03:00.0
failed with error -5
When I had the card just stop working without crashing my notebook (3.0, 3.1)
I got the same when trying to reload the driver.
> *does the other patch which remove some suspicious looking code, to
> see if it improves the situation and avoids the warnings itself.
I have built and loaded the kernel with this patch. I even have netconsole
apparently working. But ten hours have not elapsed yet. So far so good.
If it works till the 10th, I will test it with roaming, too.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-06 20:55 MR
@ 2012-01-07 11:48 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-07 11:48 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
2012/1/7 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > 2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > > > > can a find a fix
> > > > > > for both of them
> > > > >
> > > > > I am building kernel with pos<0 check added...
> > > >
> > > > thanks! if it does not works, i have only one more idea(a patch
> >> > which removes some suspicious code which abuses a pointer any way that
> >> > has to be fixed properly ). otherwise i need to recreate the issue and
> > > > capture the stack trace completely, put debug prints. i ran an
> >> > overnight test but was unable to recreate the issue. later today AN i
> > > > got a crash accidentally but only once, after that never.
> > >
> >> What is a complete stack trace? Maybe I can configure console in some way
> >and
> > > get the needed information.
> > >
> > >
> > yes, you can try netconsole
> >
> > *connect your test machine with wifi with another machine via ethernet
> > *give IPS 192.168.2.45 for your test machine and 192.168.2.35 for the
> > machine that collects the logs
> >
> > in the machine collecting log
> >
> > nc -l -u 1111
> >
> >
> > in your test machine this script should be started
> >
> > #!/bin/sh
> > #sudo service network-manager stop
> > sudo ifconfig eth0 192.168.2.45 netmask 255.255.255.0 up
> > sudo dmesg -n 8
> > sudo modprobe netconsole
> > netconsole=4444@192.168.2.45/eth0,1111@192.168.2.35/00:15:58:c3:bf:25
> >
> > the last one is your mac address of machine you collect logs
>
> I managed to get some _weird_ effects with it. I.e, I did something right
> (emergency syncs do appear on the target computer), but most of dmesg doesn't
> manage to get across one meter of copper.
>
> That doesn't matter, though. It does look like pos>37 check may trigger some
> adverse sign effects or something. So pos<0 check - or blind luck? - gave me
> a good disk-saveable trace...
thanks for the providing the log. it looks like there is some other
problem in doing the chip reset and
eventually when we get into ath_update_survey_stats we are hitting the panic.
you can try two things:
*after these WARNINGS, is your card in some stable state?. are you
able to see it in lspci(ie does it gets disappeared) and still
continue your wifi operation. if not then there is some other problem
while the panic is a symptom of it.
*does the other patch which remove some suspicious looking code, to
see if it improves the situation and avoids the warnings itself.
>
> There is more of the same later, of course. Much more. It looks the same,
> though.
>
> Jan 6 23:33:07 401a0bf1 kernel: [ 2259.717612] netconsole: network logging
> started
> Jan 7 00:21:28 401a0bf1 kernel: [ 5158.210728] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:28 401a0bf1 kernel: [ 5158.276098] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:28 401a0bf1 kernel: [ 5158.288955] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:28 401a0bf1 kernel: [ 5158.288958] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.404436] ath: Chip reset failed
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.404440] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.867030] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.932325] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.945170] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:29 401a0bf1 kernel: [ 5158.945172] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:29 401a0bf1 kernel: [ 5159.060572] ath: Chip reset failed
> Jan 7 00:21:29 401a0bf1 kernel: [ 5159.060576] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.523536] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.588735] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.601586] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.601588] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.717074] ath: Chip reset failed
> Jan 7 00:21:30 401a0bf1 kernel: [ 5159.717078] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.709373] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.774656] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.787499] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.787501] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.903039] ath: Chip reset failed
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.903041] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.968449] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.981289] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:31 401a0bf1 kernel: [ 5160.981294] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.096681] ath: Chip reset failed
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.096686] ath: Unable to reset channel
> (2417 MHz), reset status -22
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.223178] ath: Failed to wakeup in
> 500us
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.239556] ath: Failed to wakeup in
> 500us
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.255021] ath: Failed to wakeup in
> 500us
> Jan 7 00:21:31 401a0bf1 kernel: [ 5161.255111] cfg80211: Calling CRDA for
> country: RU
> Jan 7 00:21:32 401a0bf1 kernel: [ 5161.400675] ath: Failed to wakeup in
> 500us
> Jan 7 00:21:32 401a0bf1 kernel: [ 5161.411484] ath: Failed to wakeup in
> 500us
> Jan 7 00:21:32 401a0bf1 kernel: [ 5161.527195] ath: Chip reset failed
> Jan 7 00:21:32 401a0bf1 kernel: [ 5161.527199] ath: Unable to reset channel
> (2417 MHz), reset status -22
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.022122] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.087365] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.100217] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.100219] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.215756] ath: Chip reset failed
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.215759] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:32 401a0bf1 kernel: [ 5162.280986] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.293810] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.293814] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409170] ath: Chip reset failed
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409175] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409228] ath: Unable to set channel
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.474544] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.487419] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.487422] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.602974] ath: Chip reset failed
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.602979] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603031] ath: Unable to set channel
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603045] ------------[ cut here ]-----
> -------
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603058] WARNING: at
> drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
> [ath9k]()
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603060] Hardware name: N53Jn
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603061] Modules linked in: netconsole
> af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
> v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
> crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
> ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
> ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
> thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
> cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
> snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
> freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
> drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
> thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
> uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
> libcrc32c
> Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
> i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
> dm_mod unix [last unloaded: ath5k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603129] Pid: 777, comm: kworker/u:0
> Not tainted 3.2.0 #1
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603131] Call Trace:
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603138]
> [warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603138] [<ffffffff8104c9ba>]
> warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603141]
> [warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603141] [<ffffffff8104ca05>]
> warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603144]
> [ath9k:ath_update_survey_stats+0x233/0x260]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603144] [<ffffffffa055e453>]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603147]
> [ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603147] [<ffffffffa0560a45>]
> ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603152] [queue_work+0x1a/0x20] ?
> queue_work+0x1a/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603152] [<ffffffff81061dba>] ?
> queue_work+0x1a/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603154]
> [queue_delayed_work+0x25/0x30] ? queue_delayed_work+0x25/0x30
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603154] [<ffffffff81061e65>] ?
> queue_delayed_work+0x25/0x30
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603161]
> [mac80211:ieee80211_queue_delayed_work+0x46/0x60] ?
> ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603161] [<ffffffffa053d3f6>] ?
> ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603165]
> [ath9k:ath9k_flush+0x155/0x1d0] ? ath9k_flush+0x155/0x1d0 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603165] [<ffffffffa055f7b5>] ?
> ath9k_flush+0x155/0x1d0 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603168]
> [mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603168] [<ffffffffa051e272>]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603173]
> [mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603173] [<ffffffffa0523a03>]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603178]
> [mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603178] [<ffffffffa05237c0>] ?
> ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603180]
> [process_one_work+0x111/0x390] process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603180] [<ffffffff81062eb1>]
> process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603183] [worker_thread+0x162/0x340]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603183] [<ffffffff81063d12>]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603185] [worker_thread+0x0/0x340] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603185] [<ffffffff81063bb0>] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603188] [kthread+0x96/0xa0]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603188] [<ffffffff81068936>]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603193]
> [kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603193] [<ffffffff8135eef4>]
> kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603195] [kthread+0x0/0xa0] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603195] [<ffffffff810688a0>] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603197]
> [kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603197] [<ffffffff8135eef0>] ?
> gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603199] ---[ end trace
> 852186af63bdb712 ]---
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603200]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603201] pos is 1810403901 index out
> of bounds!!! in ath_update_survey_stats
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.668425] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.681273] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.681275] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796837] ath: Chip reset failed
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796839] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796863] ath: Unable to set channel
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796873] ------------[ cut here ]-----
> -------
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796889] WARNING: at
> drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
> [ath9k]()
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796892] Hardware name: N53Jn
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796893] Modules linked in: netconsole
> af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
> v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
> crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
> ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
> ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
> thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
> cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
> snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
> freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
> drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
> thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
> uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
> libcrc32c
> Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
> i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
> dm_mod unix [last unloaded: ath5k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796970] Pid: 777, comm: kworker/u:0
> Tainted: G W 3.2.0 #1
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796972] Call Trace:
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796981]
> [warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796981] [<ffffffff8104c9ba>]
> warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796984]
> [warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796984] [<ffffffff8104ca05>]
> warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796988]
> [ath9k:ath_update_survey_stats+0x233/0x260]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796988] [<ffffffffa055e453>]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796992]
> [ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796992] [<ffffffffa0560a45>]
> ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797000]
> [mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797000] [<ffffffffa051e272>]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797007]
> [mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797007] [<ffffffffa0523a03>]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797014]
> [mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797014] [<ffffffffa05237c0>] ?
> ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797019]
> [process_one_work+0x111/0x390] process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797019] [<ffffffff81062eb1>]
> process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797023] [worker_thread+0x162/0x340]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797023] [<ffffffff81063d12>]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797026] [worker_thread+0x0/0x340] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797026] [<ffffffff81063bb0>] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797030] [kthread+0x96/0xa0]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797030] [<ffffffff81068936>]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797036]
> [kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797036] [<ffffffff8135eef4>]
> kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797039] [kthread+0x0/0xa0] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797039] [<ffffffff810688a0>] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797042]
> [kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797042] [<ffffffff8135eef0>] ?
> gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797044] ---[ end trace
> 852186af63bdb713 ]---
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797046]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797047] pos is 1810403901 index out
> of bounds!!! in ath_update_survey_stats
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.862420] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.875272] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.875274] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990646] ath: Chip reset failed
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990651] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990758] ath: Unable to set channel
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991392] ------------[ cut here ]-----
> -------
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991408] WARNING: at
> drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
> [ath9k]()
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991411] Hardware name: N53Jn
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991412] Modules linked in: netconsole
> af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
> v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
> crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
> ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
> ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
> thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
> cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
> snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
> freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
> drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
> thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
> uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
> libcrc32c
> Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
> i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
> dm_mod unix [last unloaded: ath5k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991511] Pid: 777, comm: kworker/u:0
> Tainted: G W 3.2.0 #1
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991513] Call Trace:
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991521]
> [warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991521] [<ffffffff8104c9ba>]
> warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991525]
> [warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991525] [<ffffffff8104ca05>]
> warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991530]
> [ath9k:ath_update_survey_stats+0x233/0x260]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991530] [<ffffffffa055e453>]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991535]
> [ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991535] [<ffffffffa0560a45>]
> ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991544]
> [mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991544] [<ffffffffa051e272>]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991551]
> [mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991551] [<ffffffffa0523a03>]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991558]
> [mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991558] [<ffffffffa05237c0>] ?
> ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991563]
> [process_one_work+0x111/0x390] process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991563] [<ffffffff81062eb1>]
> process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991568] [worker_thread+0x162/0x340]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991568] [<ffffffff81063d12>]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991571] [worker_thread+0x0/0x340] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991571] [<ffffffff81063bb0>] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991575] [kthread+0x96/0xa0]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991575] [<ffffffff81068936>]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991581]
> [kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991581] [<ffffffff8135eef4>]
> kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991585] [kthread+0x0/0xa0] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991585] [<ffffffff810688a0>] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991588]
> [kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991588] [<ffffffff8135eef0>] ?
> gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991591] ---[ end trace
> 852186af63bdb714 ]---
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991592]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991593] pos is 1810403901 index out
> of bounds!!! in ath_update_survey_stats
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.056922] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.069872] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.069875] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185503] ath: Chip reset failed
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185507] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185579] ath: Unable to set channel
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185584] ------------[ cut here ]-----
> -------
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185597] WARNING: at
> drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
> [ath9k]()
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185599] Hardware name: N53Jn
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185600] Modules linked in: netconsole
> af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
> v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
> crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
> ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
> ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
> thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
> cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
> snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
> freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
> drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
> thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
> uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
> libcrc32c
> Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
> i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
> dm_mod unix [last unloaded: ath5k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185664] Pid: 777, comm: kworker/u:0
> Tainted: G W 3.2.0 #1
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185666] Call Trace:
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185673]
> [warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185673] [<ffffffff8104c9ba>]
> warn_slowpath_common+0x7a/0xb0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185675]
> [warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185675] [<ffffffff8104ca05>]
> warn_slowpath_null+0x15/0x20
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185678]
> [ath9k:ath_update_survey_stats+0x233/0x260]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185678] [<ffffffffa055e453>]
> ath_update_survey_stats+0x233/0x260 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185682]
> [ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185682] [<ffffffffa0560a45>]
> ath9k_config+0x115/0x780 [ath9k]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185688]
> [mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185688] [<ffffffffa051e272>]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185693]
> [mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185693] [<ffffffffa0523a03>]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185697]
> [mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
> [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185697] [<ffffffffa05237c0>] ?
> ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185702]
> [process_one_work+0x111/0x390] process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185702] [<ffffffff81062eb1>]
> process_one_work+0x111/0x390
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185705] [worker_thread+0x162/0x340]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185705] [<ffffffff81063d12>]
> worker_thread+0x162/0x340
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185707] [worker_thread+0x0/0x340] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185707] [<ffffffff81063bb0>] ?
> manage_workers.clone.26+0x240/0x240
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185710] [kthread+0x96/0xa0]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185710] [<ffffffff81068936>]
> kthread+0x96/0xa0
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185715]
> [kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185715] [<ffffffff8135eef4>]
> kernel_thread_helper+0x4/0x10
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185717] [kthread+0x0/0xa0] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185717] [<ffffffff810688a0>] ?
> kthread_worker_fn+0x190/0x190
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185719]
> [kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185719] [<ffffffff8135eef0>] ?
> gs_change+0x13/0x13
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185721] ---[ end trace
> 852186af63bdb715 ]---
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185722]
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185723] pos is 1810403901 index out
> of bounds!!! in ath_update_survey_stats
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.251027] ath: Failed to stop TX DMA,
> queues=0x10f!
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.263892] ath: DMA failed to stop in 10
> ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Jan 7 00:21:33 401a0bf1 kernel: [ 5163.263894] ath: Could not stop RX, we
> could be confusing the DMA engine when we start RX up
> Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379438] ath: Chip reset failed
> Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379441] ath: Unable to reset channel,
> reset status -22
> Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379510] ath: Unable to set channel
> Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379519] ------------[ cut here ]-----
> -------
>
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-06 20:55 MR
2012-01-07 11:48 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-06 20:55 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> 2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > > > can a find a fix
> > > > > for both of them
> > > >
> > > > I am building kernel with pos<0 check added...
> > >
> > > thanks! if it does not works, i have only one more idea(a patch
>> > which removes some suspicious code which abuses a pointer any way that
>> > has to be fixed properly ). otherwise i need to recreate the issue and
> > > capture the stack trace completely, put debug prints. i ran an
>> > overnight test but was unable to recreate the issue. later today AN i
> > > got a crash accidentally but only once, after that never.
> >
>> What is a complete stack trace? Maybe I can configure console in some way
>and
> > get the needed information.
> >
> >
> yes, you can try netconsole
>
> *connect your test machine with wifi with another machine via ethernet
> *give IPS 192.168.2.45 for your test machine and 192.168.2.35 for the
> machine that collects the logs
>
> in the machine collecting log
>
> nc -l -u 1111
>
>
> in your test machine this script should be started
>
> #!/bin/sh
> #sudo service network-manager stop
> sudo ifconfig eth0 192.168.2.45 netmask 255.255.255.0 up
> sudo dmesg -n 8
> sudo modprobe netconsole
> netconsole=4444@192.168.2.45/eth0,1111@192.168.2.35/00:15:58:c3:bf:25
>
> the last one is your mac address of machine you collect logs
I managed to get some _weird_ effects with it. I.e, I did something right
(emergency syncs do appear on the target computer), but most of dmesg doesn't
manage to get across one meter of copper.
That doesn't matter, though. It does look like pos>37 check may trigger some
adverse sign effects or something. So pos<0 check - or blind luck? - gave me
a good disk-saveable trace...
There is more of the same later, of course. Much more. It looks the same,
though.
Jan 6 23:33:07 401a0bf1 kernel: [ 2259.717612] netconsole: network logging
started
Jan 7 00:21:28 401a0bf1 kernel: [ 5158.210728] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:28 401a0bf1 kernel: [ 5158.276098] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:28 401a0bf1 kernel: [ 5158.288955] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:28 401a0bf1 kernel: [ 5158.288958] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.404436] ath: Chip reset failed
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.404440] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.867030] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.932325] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.945170] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:29 401a0bf1 kernel: [ 5158.945172] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:29 401a0bf1 kernel: [ 5159.060572] ath: Chip reset failed
Jan 7 00:21:29 401a0bf1 kernel: [ 5159.060576] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.523536] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.588735] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.601586] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.601588] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.717074] ath: Chip reset failed
Jan 7 00:21:30 401a0bf1 kernel: [ 5159.717078] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.709373] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.774656] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.787499] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.787501] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.903039] ath: Chip reset failed
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.903041] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.968449] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.981289] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:31 401a0bf1 kernel: [ 5160.981294] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.096681] ath: Chip reset failed
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.096686] ath: Unable to reset channel
(2417 MHz), reset status -22
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.223178] ath: Failed to wakeup in
500us
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.239556] ath: Failed to wakeup in
500us
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.255021] ath: Failed to wakeup in
500us
Jan 7 00:21:31 401a0bf1 kernel: [ 5161.255111] cfg80211: Calling CRDA for
country: RU
Jan 7 00:21:32 401a0bf1 kernel: [ 5161.400675] ath: Failed to wakeup in
500us
Jan 7 00:21:32 401a0bf1 kernel: [ 5161.411484] ath: Failed to wakeup in
500us
Jan 7 00:21:32 401a0bf1 kernel: [ 5161.527195] ath: Chip reset failed
Jan 7 00:21:32 401a0bf1 kernel: [ 5161.527199] ath: Unable to reset channel
(2417 MHz), reset status -22
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.022122] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.087365] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.100217] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.100219] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.215756] ath: Chip reset failed
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.215759] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:32 401a0bf1 kernel: [ 5162.280986] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.293810] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.293814] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409170] ath: Chip reset failed
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409175] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.409228] ath: Unable to set channel
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.474544] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.487419] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.487422] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.602974] ath: Chip reset failed
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.602979] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603031] ath: Unable to set channel
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603045] ------------[ cut here ]-----
-------
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603058] WARNING: at
drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
[ath9k]()
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603060] Hardware name: N53Jn
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603061] Modules linked in: netconsole
af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
libcrc32c
Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
dm_mod unix [last unloaded: ath5k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603129] Pid: 777, comm: kworker/u:0
Not tainted 3.2.0 #1
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603131] Call Trace:
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603138]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603138] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603141]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603141] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603144]
[ath9k:ath_update_survey_stats+0x233/0x260]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603144] [<ffffffffa055e453>]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603147]
[ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603147] [<ffffffffa0560a45>]
ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603152] [queue_work+0x1a/0x20] ?
queue_work+0x1a/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603152] [<ffffffff81061dba>] ?
queue_work+0x1a/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603154]
[queue_delayed_work+0x25/0x30] ? queue_delayed_work+0x25/0x30
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603154] [<ffffffff81061e65>] ?
queue_delayed_work+0x25/0x30
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603161]
[mac80211:ieee80211_queue_delayed_work+0x46/0x60] ?
ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603161] [<ffffffffa053d3f6>] ?
ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603165]
[ath9k:ath9k_flush+0x155/0x1d0] ? ath9k_flush+0x155/0x1d0 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603165] [<ffffffffa055f7b5>] ?
ath9k_flush+0x155/0x1d0 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603168]
[mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603168] [<ffffffffa051e272>]
ieee80211_hw_config+0xe2/0x160 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603173]
[mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603173] [<ffffffffa0523a03>]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603178]
[mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603178] [<ffffffffa05237c0>] ?
ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603180]
[process_one_work+0x111/0x390] process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603180] [<ffffffff81062eb1>]
process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603183] [worker_thread+0x162/0x340]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603183] [<ffffffff81063d12>]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603185] [worker_thread+0x0/0x340] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603185] [<ffffffff81063bb0>] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603188] [kthread+0x96/0xa0]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603188] [<ffffffff81068936>]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603193]
[kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603193] [<ffffffff8135eef4>]
kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603195] [kthread+0x0/0xa0] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603195] [<ffffffff810688a0>] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603197]
[kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603197] [<ffffffff8135eef0>] ?
gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603199] ---[ end trace
852186af63bdb712 ]---
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603200]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.603201] pos is 1810403901 index out
of bounds!!! in ath_update_survey_stats
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.668425] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.681273] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.681275] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796837] ath: Chip reset failed
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796839] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796863] ath: Unable to set channel
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796873] ------------[ cut here ]-----
-------
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796889] WARNING: at
drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
[ath9k]()
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796892] Hardware name: N53Jn
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796893] Modules linked in: netconsole
af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
libcrc32c
Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
dm_mod unix [last unloaded: ath5k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796970] Pid: 777, comm: kworker/u:0
Tainted: G W 3.2.0 #1
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796972] Call Trace:
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796981]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796981] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796984]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796984] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796988]
[ath9k:ath_update_survey_stats+0x233/0x260]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796988] [<ffffffffa055e453>]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796992]
[ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.796992] [<ffffffffa0560a45>]
ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797000]
[mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797000] [<ffffffffa051e272>]
ieee80211_hw_config+0xe2/0x160 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797007]
[mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797007] [<ffffffffa0523a03>]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797014]
[mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797014] [<ffffffffa05237c0>] ?
ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797019]
[process_one_work+0x111/0x390] process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797019] [<ffffffff81062eb1>]
process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797023] [worker_thread+0x162/0x340]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797023] [<ffffffff81063d12>]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797026] [worker_thread+0x0/0x340] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797026] [<ffffffff81063bb0>] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797030] [kthread+0x96/0xa0]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797030] [<ffffffff81068936>]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797036]
[kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797036] [<ffffffff8135eef4>]
kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797039] [kthread+0x0/0xa0] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797039] [<ffffffff810688a0>] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797042]
[kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797042] [<ffffffff8135eef0>] ?
gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797044] ---[ end trace
852186af63bdb713 ]---
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797046]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.797047] pos is 1810403901 index out
of bounds!!! in ath_update_survey_stats
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.862420] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.875272] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.875274] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990646] ath: Chip reset failed
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990651] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.990758] ath: Unable to set channel
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991392] ------------[ cut here ]-----
-------
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991408] WARNING: at
drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
[ath9k]()
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991411] Hardware name: N53Jn
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991412] Modules linked in: netconsole
af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
libcrc32c
Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
dm_mod unix [last unloaded: ath5k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991511] Pid: 777, comm: kworker/u:0
Tainted: G W 3.2.0 #1
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991513] Call Trace:
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991521]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991521] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991525]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991525] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991530]
[ath9k:ath_update_survey_stats+0x233/0x260]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991530] [<ffffffffa055e453>]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991535]
[ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991535] [<ffffffffa0560a45>]
ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991544]
[mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991544] [<ffffffffa051e272>]
ieee80211_hw_config+0xe2/0x160 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991551]
[mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991551] [<ffffffffa0523a03>]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991558]
[mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991558] [<ffffffffa05237c0>] ?
ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991563]
[process_one_work+0x111/0x390] process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991563] [<ffffffff81062eb1>]
process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991568] [worker_thread+0x162/0x340]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991568] [<ffffffff81063d12>]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991571] [worker_thread+0x0/0x340] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991571] [<ffffffff81063bb0>] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991575] [kthread+0x96/0xa0]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991575] [<ffffffff81068936>]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991581]
[kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991581] [<ffffffff8135eef4>]
kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991585] [kthread+0x0/0xa0] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991585] [<ffffffff810688a0>] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991588]
[kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991588] [<ffffffff8135eef0>] ?
gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991591] ---[ end trace
852186af63bdb714 ]---
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991592]
Jan 7 00:21:33 401a0bf1 kernel: [ 5162.991593] pos is 1810403901 index out
of bounds!!! in ath_update_survey_stats
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.056922] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.069872] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.069875] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185503] ath: Chip reset failed
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185507] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185579] ath: Unable to set channel
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185584] ------------[ cut here ]-----
-------
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185597] WARNING: at
drivers/net/wireless/ath/ath9k/main.c:195 ath_update_survey_stats+0x233/0x260
[ath9k]()
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185599] Hardware name: N53Jn
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185600] Modules linked in: netconsole
af_packet snd_pcm_oss snd_mixer_oss cls_cgroup uvcvideo videodev
v4l2_compat_ioctl32 cdc_phonet phonet bsd_comp ppp_deflate ppp_async
crc_ccitt ppp_generic slhc cdc_acm rtc_cmos configs kvm_intel kvm atl1c
ide_cd_mod ide_core pktcdvd pata_atiixp ipip tunnel4 ftdi_sio usbserial arc4
ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 rfkill 8139too mii fuse
thermal ac tun usb_storage usb_libusual speedstep_lib cpufreq_powersave
cpufreq_performance loop ipv6 snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc battery power_supply coretemp cpufreq_ondemand acpi_cpufreq
freq_table processor mperf i915 fbcon tileblit font bitblit softcursor
drm_kms_helper drm intel_agp i2c_algo_bit button intel_gtt agpgart video
thermal_sys hwmon ext4 jbd2 crc16 sr_mod cdrom ahci libahci xtkbd ohci_hcd
uhci_hcd ehci_hcd xhci_hcd usbhid hid usbcore usb_common btrfs zlib_deflate
libcrc32c
Jan 7 00:21:33 401a0bf1 kernel: rc32c ext3 jbd mbcache synaptics_i2c
i2c_core sermouse psmouse evdev pcips2 sd_mod crc_t10dif libata scsi_mod
dm_mod unix [last unloaded: ath5k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185664] Pid: 777, comm: kworker/u:0
Tainted: G W 3.2.0 #1
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185666] Call Trace:
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185673]
[warn_slowpath_common+0x7a/0xb0] warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185673] [<ffffffff8104c9ba>]
warn_slowpath_common+0x7a/0xb0
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185675]
[warn_slowpath_null+0x15/0x20] warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185675] [<ffffffff8104ca05>]
warn_slowpath_null+0x15/0x20
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185678]
[ath9k:ath_update_survey_stats+0x233/0x260]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185678] [<ffffffffa055e453>]
ath_update_survey_stats+0x233/0x260 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185682]
[ath9k:ath9k_config+0x115/0x780] ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185682] [<ffffffffa0560a45>]
ath9k_config+0x115/0x780 [ath9k]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185688]
[mac80211:ieee80211_hw_config+0xe2/0x160] ieee80211_hw_config+0xe2/0x160
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185688] [<ffffffffa051e272>]
ieee80211_hw_config+0xe2/0x160 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185693]
[mac80211:ieee80211_scan_work+0x243/0x5c0] ieee80211_scan_work+0x243/0x5c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185693] [<ffffffffa0523a03>]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185697]
[mac80211:ieee80211_scan_work+0x0/0x5c0] ? ieee80211_scan_rx+0x1c0/0x1c0
[mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185697] [<ffffffffa05237c0>] ?
ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185702]
[process_one_work+0x111/0x390] process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185702] [<ffffffff81062eb1>]
process_one_work+0x111/0x390
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185705] [worker_thread+0x162/0x340]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185705] [<ffffffff81063d12>]
worker_thread+0x162/0x340
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185707] [worker_thread+0x0/0x340] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185707] [<ffffffff81063bb0>] ?
manage_workers.clone.26+0x240/0x240
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185710] [kthread+0x96/0xa0]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185710] [<ffffffff81068936>]
kthread+0x96/0xa0
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185715]
[kernel_thread_helper+0x4/0x10] kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185715] [<ffffffff8135eef4>]
kernel_thread_helper+0x4/0x10
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185717] [kthread+0x0/0xa0] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185717] [<ffffffff810688a0>] ?
kthread_worker_fn+0x190/0x190
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185719]
[kernel_thread_helper+0x0/0x10] ? gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185719] [<ffffffff8135eef0>] ?
gs_change+0x13/0x13
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185721] ---[ end trace
852186af63bdb715 ]---
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185722]
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.185723] pos is 1810403901 index out
of bounds!!! in ath_update_survey_stats
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.251027] ath: Failed to stop TX DMA,
queues=0x10f!
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.263892] ath: DMA failed to stop in 10
ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jan 7 00:21:33 401a0bf1 kernel: [ 5163.263894] ath: Could not stop RX, we
could be confusing the DMA engine when we start RX up
Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379438] ath: Chip reset failed
Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379441] ath: Unable to reset channel,
reset status -22
Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379510] ath: Unable to set channel
Jan 7 00:21:34 401a0bf1 kernel: [ 5163.379519] ------------[ cut here ]-----
-------
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-06 14:46 MR
@ 2012-01-06 14:50 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-06 14:50 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > > can a find a fix
> > > > for both of them
> > >
> > > I am building kernel with pos<0 check added...
> >
> > thanks! if it does not works, i have only one more idea(a patch
> > which removes some suspicious code which abuses a pointer any way that
> > has to be fixed properly ). otherwise i need to recreate the issue and
> > capture the stack trace completely, put debug prints. i ran an
> > overnight test but was unable to recreate the issue. later today AN i
> > got a crash accidentally but only once, after that never.
>
> What is a complete stack trace? Maybe I can configure console in some way and
> get the needed information.
just want to make sure , if we get the EIP and the exact line.
ath9k_config+0x115/0x780 points to ath_update_survey_stats
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-06 14:46 MR
2012-01-06 14:50 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-06 14:46 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> > > can a find a fix
> > > for both of them
> >
> > I am building kernel with pos<0 check added...
>
> thanks! if it does not works, i have only one more idea(a patch
> which removes some suspicious code which abuses a pointer any way that
> has to be fixed properly ). otherwise i need to recreate the issue and
> capture the stack trace completely, put debug prints. i ran an
> overnight test but was unable to recreate the issue. later today AN i
> got a crash accidentally but only once, after that never.
What is a complete stack trace? Maybe I can configure console in some way and
get the needed information.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-06 14:35 ` Mohammed Shafi
@ 2012-01-06 14:41 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-06 14:41 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
On Fri, Jan 6, 2012 at 8:05 PM, Mohammed Shafi <shafi.wireless@gmail.com> wrote:
> 2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
>> >:( i had put those warnings to prevent the crash itself and what's causing
>> >it.
>> > may be i had missed that pos can be < 0 in addition to (pos > 37).
>> > i am just looking at those areas of code for some other issue. hope i
>> > can a find a fix
>> > for both of them
>>
>> I am building kernel with pos<0 check added...
>
> thanks! if it does not works, i have only one more idea(a patch
> which removes some suspicious code which abuses a pointer any way that
> has to be fixed properly ). otherwise i need to recreate the issue and
> capture the stack trace completely, put debug prints. i ran an
> overnight test but was unable to recreate the issue. later today AN i
> got a crash accidentally but only once, after that never.
attaching the patch for your reference, but this is not the fix. it
has to be fixed properly.
if it does not helps, then the issue itself is something else i had assumed.
>
>>
>> I hoped for some ad-hoc stress-test recommendation, but I guess this will have
>> to wait.
any test if we can recreate the panic ASAP will be highly helpful. it
will help us narrow down the issue quickly and put more debug
prints/ideas
>>
>>
>
>
>
> --
> shafi
--
shafi
[-- Attachment #2: remove-suspicious-code.patch --]
[-- Type: text/x-diff, Size: 1510 bytes --]
diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c
index e267c92..a39cbdc 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -1629,7 +1629,6 @@ static int ath9k_config(struct ieee80211_hw *hw, u32 changed)
if (changed & IEEE80211_CONF_CHANGE_CHANNEL) {
struct ieee80211_channel *curchan = hw->conf.channel;
- struct ath9k_channel old_chan;
int pos = curchan->hw_value;
int old_pos = -1;
unsigned long flags;
@@ -1645,25 +1644,15 @@ static int ath9k_config(struct ieee80211_hw *hw, u32 changed)
ath_dbg(common, CONFIG, "Set channel: %d MHz type: %d\n",
curchan->center_freq, conf->channel_type);
+ ath9k_cmn_update_ichannel(&sc->sc_ah->channels[pos],
+ curchan, conf->channel_type);
+
/* update survey stats for the old channel before switching */
spin_lock_irqsave(&common->cc_lock, flags);
ath_update_survey_stats(sc);
spin_unlock_irqrestore(&common->cc_lock, flags);
/*
- * Preserve the current channel values, before updating
- * the same channel
- */
- if (old_pos == pos) {
- memcpy(&old_chan, &sc->sc_ah->channels[pos],
- sizeof(struct ath9k_channel));
- ah->curchan = &old_chan;
- }
-
- ath9k_cmn_update_ichannel(&sc->sc_ah->channels[pos],
- curchan, conf->channel_type);
-
- /*
* If the operating channel changes, change the survey in-use flags
* along with it.
* Reset the survey data for the new channel, unless we're switching
^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-06 12:51 MR
@ 2012-01-06 14:35 ` Mohammed Shafi
2012-01-06 14:41 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-06 14:35 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> >:( i had put those warnings to prevent the crash itself and what's causing
> >it.
> > may be i had missed that pos can be < 0 in addition to (pos > 37).
> > i am just looking at those areas of code for some other issue. hope i
> > can a find a fix
> > for both of them
>
> I am building kernel with pos<0 check added...
thanks! if it does not works, i have only one more idea(a patch
which removes some suspicious code which abuses a pointer any way that
has to be fixed properly ). otherwise i need to recreate the issue and
capture the stack trace completely, put debug prints. i ran an
overnight test but was unable to recreate the issue. later today AN i
got a crash accidentally but only once, after that never.
>
> I hoped for some ad-hoc stress-test recommendation, but I guess this will have
> to wait.
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-06 12:51 MR
2012-01-06 14:35 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-06 12:51 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
>:( i had put those warnings to prevent the crash itself and what's causing
>it.
> may be i had missed that pos can be < 0 in addition to (pos > 37).
> i am just looking at those areas of code for some other issue. hope i
> can a find a fix
> for both of them
I am building kernel with pos<0 check added...
I hoped for some ad-hoc stress-test recommendation, but I guess this will have
to wait.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-06 8:01 MR
@ 2012-01-06 9:02 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-06 9:02 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
2012/1/6 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > > > :) no problem. i hope for you can recreate the issue consistently ,
> > > > can you please test with the attached patch and another debug patch.
> >> > please let me know if there is no panic but there are warnings (or)
> >if
> > > > there are no warnings (or) the issue still appears(also the trace
> > > > thanks) , also if you need any help
> > > Should I apply the patch to Linux 3.2-rc7 or 3.2 release?
> >Oh, I see. 3.2 release has this fix already. I will build it with
> debugging
> > patch and report warnings now.
>
> I have some unpleasant news: it looks like it takes slightly longer with the
> fix, but the crash still managed to occur with 3.2 and I lack ESP to check
> for warnings immediately before that. I thought that 8 hours is enough
> testing, heh. It simply took 9 and a half under nigh-ideal conditions
> (stable signal from fixed AP with notebook also steadily in one place).
:( i had put those warnings to prevent the crash itself and what's causing it.
may be i had missed that pos can be < 0 in addition to (pos > 37).
i am just looking at those areas of code for some other issue. hope i
can a find a fix
for both of them
>
> Good news is that I remembered to decrease console font size before the
> crash. So now I could see that the long stack trace was just a decoy to
> ensure that the first Oops scrolls too far up. I now have photos of the
> first one, too.
>
> Process: kworker/u:2 (pid: 1419, threadinfo ffff88013dc38000, task
> ffff8800891020d0)
> Stack:
> ffff88013dc39c10 ffff880136111ae0 ffff880136110460 0000000000000040
> ffff880136114000 0000000000000000 ffff88013dc39d20 ffffffffa0560a35
> 0000000000000001 0000000000000202 ffff8801361140f0 ffff88013ed3ea48
> Call trace:
> ath9k_config+0x115/0x780 [ath9k]
> ? queue_work+0x1a/0x20
> ? queue_delayed_work+0x25/0x30
> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> ? ath9k_flush+0x155/0x1d0 [ath9k]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> ? __schedule+0x2d7/0x7b0
> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> process_one_work+0x111/0x390
>
> Only after this happens "unable to complete kernel paging request" in
> ath_update_survey_stats
> worker_thread+0x162/0x340
> ? manage_workers.clone.26+0x240/0x240
> kthread+0x96/0xa0
> kernel_thread_helper+0x4/0x10
> ? kthread_worker_fn+0x190/0x190
> ? gs_change+0x13/0x13
>
>
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-06 8:10 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-06 8:10 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
>I have some unpleasant news: it looks like it takes slightly longer with
>the
>fix, but the crash still managed to occur with 3.2 and I lack ESP to check
> for warnings immediately before that. I thought that 8 hours is enough
> testing, heh. It simply took 9 and a half under nigh-ideal conditions
> (stable signal from fixed AP with notebook also steadily in one place).
By the way, what could trigger these crashes in "network event sense"? If this
can be reproduced with Ad-Hoc (something like ""Ad-Hoc peer changes ESSID then
changes it back"), I could easily do some stress-testing with a second Linux-
running notebook.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-06 8:01 MR
2012-01-06 9:02 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-06 8:01 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> > > :) no problem. i hope for you can recreate the issue consistently ,
> > > can you please test with the attached patch and another debug patch.
>> > please let me know if there is no panic but there are warnings (or)
>if
> > > there are no warnings (or) the issue still appears(also the trace
> > > thanks) , also if you need any help
> > Should I apply the patch to Linux 3.2-rc7 or 3.2 release?
>Oh, I see. 3.2 release has this fix already. I will build it with
debugging
> patch and report warnings now.
I have some unpleasant news: it looks like it takes slightly longer with the
fix, but the crash still managed to occur with 3.2 and I lack ESP to check
for warnings immediately before that. I thought that 8 hours is enough
testing, heh. It simply took 9 and a half under nigh-ideal conditions
(stable signal from fixed AP with notebook also steadily in one place).
Good news is that I remembered to decrease console font size before the
crash. So now I could see that the long stack trace was just a decoy to
ensure that the first Oops scrolls too far up. I now have photos of the
first one, too.
Process: kworker/u:2 (pid: 1419, threadinfo ffff88013dc38000, task
ffff8800891020d0)
Stack:
ffff88013dc39c10 ffff880136111ae0 ffff880136110460 0000000000000040
ffff880136114000 0000000000000000 ffff88013dc39d20 ffffffffa0560a35
0000000000000001 0000000000000202 ffff8801361140f0 ffff88013ed3ea48
Call trace:
ath9k_config+0x115/0x780 [ath9k]
? queue_work+0x1a/0x20
? queue_delayed_work+0x25/0x30
? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
? ath9k_flush+0x155/0x1d0 [ath9k]
ieee80211_hw_config+0xe2/0x160 [mac80211]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
? __schedule+0x2d7/0x7b0
? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
process_one_work+0x111/0x390
Only after this happens "unable to complete kernel paging request" in
ath_update_survey_stats
worker_thread+0x162/0x340
? manage_workers.clone.26+0x240/0x240
kthread+0x96/0xa0
kernel_thread_helper+0x4/0x10
? kthread_worker_fn+0x190/0x190
? gs_change+0x13/0x13
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
[not found] ` <CAD2nsn3i=HTP6zOEADMx35rOYXDofo7YG+0zCGH36XgZFLfOww@mail.gmail.com>
@ 2012-01-06 7:49 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-06 7:49 UTC (permalink / raw)
To: MR; +Cc: linux-wireless Mailing List, Linux Kernel Mailing List
>> OK, 8 hours with some network activity generated no warnings and didn't make
>> WiFi become unusable as with 3.0. Will test more with AP roaming today.
>
> thanks a lot for testing it. we need to test this more as this issue
> seems to occur after hours of testing.
> please report back if you hit warnings/panic
adding list.
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-05 18:52 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-05 18:52 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> > :) no problem. i hope for you can recreate the issue consistently ,
> > can you please test with the attached patch and another debug patch.
> > please let me know if there is no panic but there are warnings (or) if
> > there are no warnings (or) the issue still appears(also the trace
> > thanks) , also if you need any help
>
> Should I apply the patch to Linux 3.2-rc7 or 3.2 release?
Oh, I see. 3.2 release has this fix already. I will build it with debugging
patch and report warnings now.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-05 16:32 MR
0 siblings, 0 replies; 38+ messages in thread
From: MR @ 2012-01-05 16:32 UTC (permalink / raw)
To: Mohammed Shafi; +Cc: linux-kernel, linux-wireless
> :) no problem. i hope for you can recreate the issue consistently ,
> can you please test with the attached patch and another debug patch.
> please let me know if there is no panic but there are warnings (or) if
> there are no warnings (or) the issue still appears(also the trace
> thanks) , also if you need any help
Should I apply the patch to Linux 3.2-rc7 or 3.2 release?
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-05 6:59 MR
@ 2012-01-05 15:30 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-05 15:30 UTC (permalink / raw)
To: MR; +Cc: John W. Linville, linux-kernel, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 3271 bytes --]
2012/1/5 MR <g7af0ec1e3ea1e7b1@nextmail.ru>:
> > Hi John,
>
> I am the stupid original submitter who only sent this to linux-kernel
> initially.
:) no problem. i hope for you can recreate the issue consistently ,
can you please test with the attached patch and another debug patch.
please let me know if there is no panic but there are warnings (or) if
there are no warnings (or) the issue still appears(also the trace
thanks) , also if you need any help
let me also start the overnight wifi traffic in 3.2-rc7
>
> > we will take a look at this.
> >
> > i can later come up with few debug patches to narrow down the panic.
> > looks like a problem in ath_update_survey_stats(survey pointer). full
> > stack trace will be helpful
> > thanks.
>
> What I have posted is the full call trace. Right above this is the stack
> trace in hex:
>
> Process kworker/u:2 (pid: 6668, threadinfo ffff880027cd4000, task
> ffff880076a38000)
> Stack:
> ffff880027cd5808 ffffffff81064830 ffff880027cd5808 ffff880147c51c80
> ffff880027cd58b8 ffffffff8135a117 ffff880076a38620 0000000000011c80
> 0000000000011c80 ffff880076a38000 0000000000011c80 ffff880027cd5fd8
>
> Currently I have booted Linux 3.0 kernel to check whether the problem is
> already there. Unfortunately, with Linux 3.1 and 3.0 I often get the
> following in dmesg (this is at module load; sometimes the driver just stops
> working - then I get this on reloading the module):
>
> ath9k 0000:03:00.0: enabling device (0000 -> 0002)
> ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> ath9k 0000:03:00.0: setting latency timer to 64
> ath9k 0000:03:00.0: Failed to initialize device
> ath9k 0000:03:00.0: PCI INT A disabled
> ath9k: probe of 0000:03:00.0 failed with error -5
>
> As far as I understood, some similar problem was fixed after Linux 3.1.
>
> > >> My card is (as lspci says):
> > >>
> > >> 03:00.0 Network controller: Atheros Communications Inc. AR9285
> Wireless
> > >> Network Adapter (PCI-Express) (rev 01)
> > >> Subsystem: Device 1a3b:1089
>
> > >> wq_worker_sleeping+0x10/0xa0
> > >> __schedule+0x427/0x7b0
> > >> ? call_rcu_sched+0x10/0x20
> > >> schedule+0x3a/0x50
> > >> do_exit+0x57c/0x840
> > >> ? kmsg_dump+0x45/0xe0
> > >> oops_end+0xa5/0xf0
> > >> no_context+0xf2/0x270
> > >> __bad_area_no_semaphore+0xe/0x10
> > >> do_page_fault+0x2ba/0x450
> > >> ? up+0x2d/0x50
> > >> ? console_unlock+0x1df/0x250
> > >> ? select_task_rq_fair+0x5be/0x970
> > >> page_fault+0x25/0x30
> > >> ? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
> > >> ath9k_config+0x115/0x780 [ath9k]
> > >> ? queue_work+0x1a/0x20
> > >> ? queue_delayed_work+0x25/0x30
> > >> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> > >> ? ath9k_flush+0x155/0x1d0 [ath9k]
> > >> ieee80211_hw_config+0xe2/0x160 [mac80211]
> > >> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> > >> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> > >> process_one_work+0x111/0x390
> > >> worker_thread+0x162/0x340
> > >> manage_workers.clone.26+0x240/0x240
> > >> kthread+0x96/0xa0
> > >> kernel_thread_helper+0x4/0x10
> > >> ? kthread_worker_fn+0x190/0x190
> > >> ? gs_change+0x13/0x13
>
>
--
shafi
[-- Attachment #2: 0001-mac80211-fix-scan-state-machine.patch --]
[-- Type: text/x-diff, Size: 1208 bytes --]
From 509a141e14f794de8fbfe847a3de548ace21d7ec Mon Sep 17 00:00:00 2001
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
Date: Wed, 21 Dec 2011 20:11:35 +0530
Subject: [PATCH v2] mac80211: fix scan state machine
when we run high bandwidth UDP traffic and we trigger a scan, the scan
state machine seems to be looping in SUSPEND->RESUME->DECISION->SUSPEND
and SET_CHANNEL seems to be never called as 'tx_empty' is never true
while running UDP traffic. fix this by settting SET_CHANNEL state when
we get into RESUME state.
Cc: Leela Kella <leela@qca.qualcomm.com>
Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
---
net/mac80211/scan.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/mac80211/scan.c b/net/mac80211/scan.c
index 2c5041c..2908e56 100644
--- a/net/mac80211/scan.c
+++ b/net/mac80211/scan.c
@@ -625,7 +625,7 @@ static void ieee80211_scan_state_resume(struct ieee80211_local *local,
local->leave_oper_channel_time = jiffies;
/* advance to the next channel to be scanned */
- local->next_scan_state = SCAN_DECISION;
+ local->next_scan_state = SCAN_SET_CHANNEL;
}
void ieee80211_scan_work(struct work_struct *work)
--
1.7.0.4
[-- Attachment #3: survey-debug.patch --]
[-- Type: text/x-diff, Size: 706 bytes --]
diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c
index 6e3d838..4f8c905 100644
--- a/drivers/net/wireless/ath/ath9k/main.c
+++ b/drivers/net/wireless/ath/ath9k/main.c
@@ -190,6 +190,19 @@ static int ath_update_survey_stats(struct ath_softc *sc)
if (!ah->curchan)
return -1;
+ /* just to make pos does not exceeds ATH9K_NUM_CHANNELS - 1 */
+ if (pos > 37) {
+ WARN_ON(1);
+ printk("\npos is %d index out of bounds!!! in %s", pos, __func__);
+ return -1;
+ }
+
+ if (!survey) {
+ WARN_ON(1);
+ printk("\nNULL pointer for survey !!! in %s", __func__);
+ return -1;
+ }
+
if (ah->power_mode == ATH9K_PM_AWAKE)
ath_hw_cycle_counters_update(common);
^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
@ 2012-01-05 6:59 MR
2012-01-05 15:30 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-05 6:59 UTC (permalink / raw)
To: Mohammed Shafi, John W. Linville; +Cc: linux-kernel, linux-wireless
> Hi John,
I am the stupid original submitter who only sent this to linux-kernel
initially.
> we will take a look at this.
>
> i can later come up with few debug patches to narrow down the panic.
> looks like a problem in ath_update_survey_stats(survey pointer). full
> stack trace will be helpful
> thanks.
What I have posted is the full call trace. Right above this is the stack
trace in hex:
Process kworker/u:2 (pid: 6668, threadinfo ffff880027cd4000, task
ffff880076a38000)
Stack:
ffff880027cd5808 ffffffff81064830 ffff880027cd5808 ffff880147c51c80
ffff880027cd58b8 ffffffff8135a117 ffff880076a38620 0000000000011c80
0000000000011c80 ffff880076a38000 0000000000011c80 ffff880027cd5fd8
Currently I have booted Linux 3.0 kernel to check whether the problem is
already there. Unfortunately, with Linux 3.1 and 3.0 I often get the
following in dmesg (this is at module load; sometimes the driver just stops
working - then I get this on reloading the module):
ath9k 0000:03:00.0: enabling device (0000 -> 0002)
ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ath9k 0000:03:00.0: setting latency timer to 64
ath9k 0000:03:00.0: Failed to initialize device
ath9k 0000:03:00.0: PCI INT A disabled
ath9k: probe of 0000:03:00.0 failed with error -5
As far as I understood, some similar problem was fixed after Linux 3.1.
> >> My card is (as lspci says):
> >>
> >> 03:00.0 Network controller: Atheros Communications Inc. AR9285
Wireless
> >> Network Adapter (PCI-Express) (rev 01)
> >> Subsystem: Device 1a3b:1089
> >> wq_worker_sleeping+0x10/0xa0
> >> __schedule+0x427/0x7b0
> >> ? call_rcu_sched+0x10/0x20
> >> schedule+0x3a/0x50
> >> do_exit+0x57c/0x840
> >> ? kmsg_dump+0x45/0xe0
> >> oops_end+0xa5/0xf0
> >> no_context+0xf2/0x270
> >> __bad_area_no_semaphore+0xe/0x10
> >> do_page_fault+0x2ba/0x450
> >> ? up+0x2d/0x50
> >> ? console_unlock+0x1df/0x250
> >> ? select_task_rq_fair+0x5be/0x970
> >> page_fault+0x25/0x30
> >> ? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
> >> ath9k_config+0x115/0x780 [ath9k]
> >> ? queue_work+0x1a/0x20
> >> ? queue_delayed_work+0x25/0x30
> >> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> >> ? ath9k_flush+0x155/0x1d0 [ath9k]
> >> ieee80211_hw_config+0xe2/0x160 [mac80211]
> >> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> >> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> >> process_one_work+0x111/0x390
> >> worker_thread+0x162/0x340
> >> manage_workers.clone.26+0x240/0x240
> >> kthread+0x96/0xa0
> >> kernel_thread_helper+0x4/0x10
> >> ? kthread_worker_fn+0x190/0x190
> >> ? gs_change+0x13/0x13
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-04 21:28 ` John W. Linville
@ 2012-01-05 6:29 ` Mohammed Shafi
0 siblings, 0 replies; 38+ messages in thread
From: Mohammed Shafi @ 2012-01-05 6:29 UTC (permalink / raw)
To: John W. Linville; +Cc: MR, linux-kernel, linux-wireless
Hi John,
we will take a look at this.
i can later come up with few debug patches to narrow down the panic.
looks like a problem in ath_update_survey_stats(survey pointer). full
stack trace will be helpful
thanks.
On Thu, Jan 5, 2012 at 2:58 AM, John W. Linville <linville@tuxdriver.com> wrote:
> You probably want to try linux-wireless@vger.kernel.org for maximum exposure...
>
> On Thu, Jan 05, 2012 at 01:18:09AM +0400, MR wrote:
>> Hello.
>>
>> I have noticed a complete crash (forced switch to console and Alt-SysRq-B
>> doesn't work) when I use ath9k driver for my WiFi card. The problem is that
>> the crash occurs after a few hours of use, so blind bissecting doesn't look
>> like a short-term plan.
>>
>> My card is (as lspci says):
>>
>> 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
>> Network Adapter (PCI-Express) (rev 01)
>> Subsystem: Device 1a3b:1089
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> Stepping- SERR- FastB2B- DisINTx-
>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> <TAbort- <MAbort- >SERR- <PERR- INTx-
>> Latency: 0, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 17
>> Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
>>
>> I use an Asus N53JN notebook, if that matters.
>>
>> I have photos of two instances of the crash. The backtrace goes as follows (I
>> typed this in, so maybe there is a typo somewhere - I hope there is none,
>> though):
>>
>> wq_worker_sleeping+0x10/0xa0
>> __schedule+0x427/0x7b0
>> ? call_rcu_sched+0x10/0x20
>> schedule+0x3a/0x50
>> do_exit+0x57c/0x840
>> ? kmsg_dump+0x45/0xe0
>> oops_end+0xa5/0xf0
>> no_context+0xf2/0x270
>> __bad_area_no_semaphore+0xe/0x10
>> do_page_fault+0x2ba/0x450
>> ? up+0x2d/0x50
>> ? console_unlock+0x1df/0x250
>> ? select_task_rq_fair+0x5be/0x970
>> page_fault+0x25/0x30
>> ? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
>> ath9k_config+0x115/0x780 [ath9k]
>> ? queue_work+0x1a/0x20
>> ? queue_delayed_work+0x25/0x30
>> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
>> ? ath9k_flush+0x155/0x1d0 [ath9k]
>> ieee80211_hw_config+0xe2/0x160 [mac80211]
>> ieee80211_scan_work+0x243/0x5c0 [mac80211]
>> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
>> process_one_work+0x111/0x390
>> worker_thread+0x162/0x340
>> manage_workers.clone.26+0x240/0x240
>> kthread+0x96/0xa0
>> kernel_thread_helper+0x4/0x10
>> ? kthread_worker_fn+0x190/0x190
>> ? gs_change+0x13/0x13
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
shafi
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: ath9k crash 3.2-rc7
2012-01-04 21:18 MR
@ 2012-01-04 21:28 ` John W. Linville
2012-01-05 6:29 ` Mohammed Shafi
0 siblings, 1 reply; 38+ messages in thread
From: John W. Linville @ 2012-01-04 21:28 UTC (permalink / raw)
To: MR; +Cc: linux-kernel, linux-wireless
You probably want to try linux-wireless@vger.kernel.org for maximum exposure...
On Thu, Jan 05, 2012 at 01:18:09AM +0400, MR wrote:
> Hello.
>
> I have noticed a complete crash (forced switch to console and Alt-SysRq-B
> doesn't work) when I use ath9k driver for my WiFi card. The problem is that
> the crash occurs after a few hours of use, so blind bissecting doesn't look
> like a short-term plan.
>
> My card is (as lspci says):
>
> 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
> Network Adapter (PCI-Express) (rev 01)
> Subsystem: Device 1a3b:1089
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 17
> Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
>
> I use an Asus N53JN notebook, if that matters.
>
> I have photos of two instances of the crash. The backtrace goes as follows (I
> typed this in, so maybe there is a typo somewhere - I hope there is none,
> though):
>
> wq_worker_sleeping+0x10/0xa0
> __schedule+0x427/0x7b0
> ? call_rcu_sched+0x10/0x20
> schedule+0x3a/0x50
> do_exit+0x57c/0x840
> ? kmsg_dump+0x45/0xe0
> oops_end+0xa5/0xf0
> no_context+0xf2/0x270
> __bad_area_no_semaphore+0xe/0x10
> do_page_fault+0x2ba/0x450
> ? up+0x2d/0x50
> ? console_unlock+0x1df/0x250
> ? select_task_rq_fair+0x5be/0x970
> page_fault+0x25/0x30
> ? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
> ath9k_config+0x115/0x780 [ath9k]
> ? queue_work+0x1a/0x20
> ? queue_delayed_work+0x25/0x30
> ? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
> ? ath9k_flush+0x155/0x1d0 [ath9k]
> ieee80211_hw_config+0xe2/0x160 [mac80211]
> ieee80211_scan_work+0x243/0x5c0 [mac80211]
> ? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
> process_one_work+0x111/0x390
> worker_thread+0x162/0x340
> manage_workers.clone.26+0x240/0x240
> kthread+0x96/0xa0
> kernel_thread_helper+0x4/0x10
> ? kthread_worker_fn+0x190/0x190
> ? gs_change+0x13/0x13
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 38+ messages in thread
* ath9k crash 3.2-rc7
@ 2012-01-04 21:18 MR
2012-01-04 21:28 ` John W. Linville
0 siblings, 1 reply; 38+ messages in thread
From: MR @ 2012-01-04 21:18 UTC (permalink / raw)
To: linux-kernel
Hello.
I have noticed a complete crash (forced switch to console and Alt-SysRq-B
doesn't work) when I use ath9k driver for my WiFi card. The problem is that
the crash occurs after a few hours of use, so blind bissecting doesn't look
like a short-term plan.
My card is (as lspci says):
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless
Network Adapter (PCI-Express) (rev 01)
Subsystem: Device 1a3b:1089
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at d7400000 (64-bit, non-prefetchable) [size=64K]
I use an Asus N53JN notebook, if that matters.
I have photos of two instances of the crash. The backtrace goes as follows (I
typed this in, so maybe there is a typo somewhere - I hope there is none,
though):
wq_worker_sleeping+0x10/0xa0
__schedule+0x427/0x7b0
? call_rcu_sched+0x10/0x20
schedule+0x3a/0x50
do_exit+0x57c/0x840
? kmsg_dump+0x45/0xe0
oops_end+0xa5/0xf0
no_context+0xf2/0x270
__bad_area_no_semaphore+0xe/0x10
do_page_fault+0x2ba/0x450
? up+0x2d/0x50
? console_unlock+0x1df/0x250
? select_task_rq_fair+0x5be/0x970
page_fault+0x25/0x30
? ath_update_survey_stats+0xb7/0x1c0 [ath9k]
ath9k_config+0x115/0x780 [ath9k]
? queue_work+0x1a/0x20
? queue_delayed_work+0x25/0x30
? ieee80211_queue_delayed_work+0x46/0x60 [mac80211]
? ath9k_flush+0x155/0x1d0 [ath9k]
ieee80211_hw_config+0xe2/0x160 [mac80211]
ieee80211_scan_work+0x243/0x5c0 [mac80211]
? ieee80211_scan_rx+0x1c0/0x1c0 [mac80211]
process_one_work+0x111/0x390
worker_thread+0x162/0x340
manage_workers.clone.26+0x240/0x240
kthread+0x96/0xa0
kernel_thread_helper+0x4/0x10
? kthread_worker_fn+0x190/0x190
? gs_change+0x13/0x13
^ permalink raw reply [flat|nested] 38+ messages in thread
end of thread, other threads:[~2012-01-26 22:19 UTC | newest]
Thread overview: 38+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-26 22:19 ath9k crash 3.2-rc7 MR
-- strict thread matches above, loose matches on Subject: below --
2012-01-20 4:42 MR
2012-01-20 5:16 ` Mohammed Shafi
2012-01-18 17:30 MR
2012-01-17 18:53 MR
2012-01-18 5:32 ` Mohammed Shafi
2012-01-16 15:52 MR
2012-01-12 18:04 MR
2012-01-11 17:20 MR
2012-01-12 6:06 ` Mohammed Shafi
2012-01-10 18:14 MR
2012-01-11 15:26 ` Mohammed Shafi
2012-01-09 11:11 MR
2012-01-09 7:40 MR
2012-01-09 7:57 ` Mohammed Shafi
2012-01-09 7:05 MR
2012-01-09 7:30 ` Mohammed Shafi
2012-01-08 7:19 MR
2012-01-09 5:11 ` Mohammed Shafi
2012-01-07 12:11 MR
2012-01-06 20:55 MR
2012-01-07 11:48 ` Mohammed Shafi
2012-01-06 14:46 MR
2012-01-06 14:50 ` Mohammed Shafi
2012-01-06 12:51 MR
2012-01-06 14:35 ` Mohammed Shafi
2012-01-06 14:41 ` Mohammed Shafi
2012-01-06 8:10 MR
2012-01-06 8:01 MR
2012-01-06 9:02 ` Mohammed Shafi
[not found] <NEXT-4f069dda9267d2.27061318@nextmail.ru>
[not found] ` <CAD2nsn3i=HTP6zOEADMx35rOYXDofo7YG+0zCGH36XgZFLfOww@mail.gmail.com>
2012-01-06 7:49 ` Mohammed Shafi
2012-01-05 18:52 MR
2012-01-05 16:32 MR
2012-01-05 6:59 MR
2012-01-05 15:30 ` Mohammed Shafi
2012-01-04 21:18 MR
2012-01-04 21:28 ` John W. Linville
2012-01-05 6:29 ` Mohammed Shafi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).