Bug 215074 - [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs
Summary: [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs
Status: Closed Unable to Reproduce
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 11.0-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-wireless mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-05 16:53 UTC by c.kworr
Modified: 2017-03-31 16:42 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description c.kworr 2016-12-05 16:53:11 UTC
Hi all.

LOR's:

<probably unrelated)
Dec  5 03:33:50 limbo kernel: lock order reversal:
Dec  5 03:33:50 limbo kernel: 1st 0xffffffff818f4b80 pf rulesets (pf rulesets) @ /usr/src/sys/modules/pf/../../netpfil/pf/pf.c:5879
Dec  5 03:33:50 limbo kernel: 2nd 0xffffffff80d4ece8 pcbinfohash (pcbinfohash) @ /usr/src/sys/netinet/in_pcb.c:1957
Dec  5 03:33:50 limbo kernel: stack backtrace:
Dec  5 03:33:50 limbo kernel: #0 0xffffffff8040c240 at witness_debugger+0x70
Dec  5 03:33:50 limbo kernel: #1 0xffffffff8040c134 at witness_checkorder+0xe54
Dec  5 03:33:50 limbo kernel: #2 0xffffffff803a9667 at __rw_rlock+0xa7
Dec  5 03:33:50 limbo kernel: #3 0xffffffff804d548f at in_pcblookup_hash+0x3f
Dec  5 03:33:50 limbo kernel: #4 0xffffffff818c65e5 at pf_socket_lookup+0xe5
Dec  5 03:33:50 limbo kernel: #5 0xffffffff818ccbc7 at pf_test_rule+0x1817
Dec  5 03:33:50 limbo kernel: #6 0xffffffff818c8254 at pf_test+0x18f4
Dec  5 03:33:50 limbo kernel: #7 0xffffffff818db5dd at pf_check_out+0x1d
Dec  5 03:33:50 limbo kernel: #8 0xffffffff804ba47b at pfil_run_hooks+0x8b
Dec  5 03:33:50 limbo kernel: #9 0xffffffff804d79b5 at ip_tryforward+0x295
Dec  5 03:33:50 limbo kernel: #10 0xffffffff804d9f7f at ip_input+0x35f
Dec  5 03:33:50 limbo kernel: #11 0xffffffff804b9330 at netisr_dispatch_src+0x80
Dec  5 03:33:50 limbo kernel: #12 0xffffffff804a4b6a at ether_demux+0x14a
Dec  5 03:33:50 limbo kernel: #13 0xffffffff804a5960 at ether_nh_input+0x340
Dec  5 03:33:50 limbo kernel: #14 0xffffffff804b9330 at netisr_dispatch_src+0x80
Dec  5 03:33:50 limbo kernel: #15 0xffffffff804a4ed2 at ether_input+0x62
Dec  5 03:33:50 limbo kernel: #16 0xffffffff817dffa5 at re_rxeof+0x5c5
Dec  5 03:33:50 limbo kernel: #17 0xffffffff817dd5ea at re_intr_msi+0xca

Dec  5 03:34:26 limbo kernel: lock order reversal:
Dec  5 03:34:26 limbo kernel: 1st 0xfffffe0006d613f8 ath0 (ath0) @ /usr/src/sys/modules/ath/../../dev/ath/if_ath.c:6141
Dec  5 03:34:26 limbo kernel: 2nd 0xfffffe0006d608b0 ath0_node_lock (ath0_node_lock) @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_node.c:1848
Dec  5 03:34:26 limbo kernel: stack backtrace:
Dec  5 03:34:26 limbo kernel: #0 0xffffffff8040c240 at witness_debugger+0x70
Dec  5 03:34:26 limbo kernel: #1 0xffffffff8040c134 at witness_checkorder+0xe54
Dec  5 03:34:26 limbo kernel: #2 0xffffffff803941b4 at __mtx_lock_flags+0xa4
Dec  5 03:34:26 limbo kernel: #3 0xffffffff8169d7d2 at ieee80211_node_delucastkey+0x52
Dec  5 03:34:26 limbo kernel: #4 0xffffffff8169a9e5 at node_free+0x25
Dec  5 03:34:26 limbo kernel: #5 0xffffffff816a3631 at ieee80211_tx_complete+0xa1
Dec  5 03:34:26 limbo kernel: #6 0xffffffff816deb02 at ath_tx_draintxq+0x22
Dec  5 03:34:26 limbo kernel: #7 0xffffffff816df04f at ath_legacy_tx_drain+0x1df
Dec  5 03:34:26 limbo kernel: #8 0xffffffff816dc01b at ath_stop+0x15b
Dec  5 03:34:26 limbo kernel: #9 0xffffffff816d922c at ath_parent+0x13c
Dec  5 03:34:26 limbo kernel: #10 0xffffffff803ffd5c at taskqueue_run_locked+0x13c
Dec  5 03:34:26 limbo kernel: #11 0xffffffff804009c8 at taskqueue_thread_loop+0x88
Dec  5 03:34:26 limbo kernel: #12 0xffffffff80376394 at fork_exit+0x84
Dec  5 03:34:26 limbo kernel: #13 0xffffffff8063f43e at fork_trampoline+0xe
Dec  5 03:36:49 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:37:39 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:03 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:38:26 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:42:29 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4)
Dec  5 03:43:04 limbo kernel: lock order reversal:
Dec  5 03:43:04 limbo kernel: 1st 0xfffffe0006d61498 ath0 TX lock (ath0 TX lock) @ /usr/src/sys/modules/ath/../../dev/ath/if_ath_tx.c:2354
Dec  5 03:43:04 limbo kernel: 2nd 0xfffffe0006d5f020 ath0_com_lock (ath0_com_lock) @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_power.c:300
Dec  5 03:43:04 limbo kernel: stack backtrace:
Dec  5 03:43:04 limbo kernel: #0 0xffffffff8040c240 at witness_debugger+0x70
Dec  5 03:43:04 limbo kernel: #1 0xffffffff8040c134 at witness_checkorder+0xe54
Dec  5 03:43:04 limbo kernel: #2 0xffffffff803941b4 at __mtx_lock_flags+0xa4
Dec  5 03:43:04 limbo kernel: #3 0xffffffff816a3d24 at ieee80211_set_tim+0x74
Dec  5 03:43:04 limbo kernel: #4 0xffffffff816e8df4 at ath_raw_xmit+0x1024
Dec  5 03:43:04 limbo kernel: #5 0xffffffff816a0121 at ieee80211_send_nulldata+0x2f1
Dec  5 03:43:04 limbo kernel: #6 0xffffffff8169dadf at ieee80211_iterate_nodes+0x8f
Dec  5 03:43:04 limbo kernel: #7 0xffffffff8169a7fd at ieee80211_node_timeout+0x3d
Dec  5 03:43:04 limbo kernel: #8 0xffffffff803c403c at softclock_call_cc+0x19c
Dec  5 03:43:04 limbo kernel: #9 0xffffffff803c4437 at softclock+0x47
Dec  5 03:43:04 limbo kernel: #10 0xffffffff80378c46 at intr_event_execute_handlers+0x96
Dec  5 03:43:04 limbo kernel: #11 0xffffffff803792c6 at ithread_loop+0xa6
Dec  5 03:43:04 limbo kernel: #12 0xffffffff80376394 at fork_exit+0x84
Dec  5 03:43:04 limbo kernel: #13 0xffffffff8063f43e at fork_trampoline+0xe

(probably unrelated)
Dec  5 16:33:20 limbo kernel: lock order reversal:
Dec  5 16:33:20 limbo kernel: 1st 0xfffff80104299040 filedesc structure (filedesc structure) @ /usr/src/sys/kern/kern_descrip.c:1229
Dec  5 16:33:20 limbo kernel: 2nd 0xfffff803a0a917c8 zfs (zfs) @ /usr/src/sys/kern/vfs_subr.c:4911
Dec  5 16:33:20 limbo kernel: stack backtrace:
Dec  5 16:33:20 limbo kernel: #0 0xffffffff8040c240 at witness_debugger+0x70
Dec  5 16:33:20 limbo kernel: #1 0xffffffff8040c134 at witness_checkorder+0xe54
Dec  5 16:33:20 limbo kernel: #2 0xffffffff8038ae62 at __lockmgr_args+0x4c2
Dec  5 16:33:20 limbo kernel: #3 0xffffffff8045b86c at vop_stdlock+0x3c
Dec  5 16:33:20 limbo kernel: #4 0xffffffff806d62b0 at VOP_LOCK1_APV+0xe0
Dec  5 16:33:20 limbo kernel: #5 0xffffffff8047cd0a at _vn_lock+0x9a
Dec  5 16:33:20 limbo kernel: #6 0xffffffff8036c18e at knlist_remove_kq+0x7e
Dec  5 16:33:20 limbo kernel: #7 0xffffffff804738f8 at filt_vfsdetach+0x28
Dec  5 16:33:20 limbo kernel: #8 0xffffffff8036cbb7 at knote_fdclose+0xc7
Dec  5 16:33:20 limbo kernel: #9 0xffffffff80360615 at closefp+0x65
Dec  5 16:33:20 limbo kernel: #10 0xffffffff8065f774 at amd64_syscall+0x314
Dec  5 16:33:20 limbo kernel: #11 0xffffffff8063f1eb at Xfast_syscall+0xfb

And then out of nowhere:

http://limbo.b1t.name/incoming/photo725633020013422580.jpg

Thanks in advance.
Comment 1 Adrian Chadd freebsd_committer 2016-12-05 17:15:38 UTC
hi,

stuck beacons are because of AR9227, and I still need to figure that out ;(

we know about the LORs between the wifi drivers and stack; we're slowly chipping away at them.
Comment 2 Adrian Chadd freebsd_committer 2016-12-05 17:15:58 UTC
(please file a separate bug for "AR9227 stuck beacon after running a while"; as those need to get addressed still!)
Comment 3 c.kworr 2017-03-31 16:42:47 UTC
doesn't happen anymore.