Re: LOR in iwi with new 802.11 work

Stefan Ehmann wrote:
> After the system is up for about 5 minutes, I see this LOR. Haven't seen it 
> posted yet.
> 
> Stefan
> 
> lock order reversal:
>  1st 0xc2e4700c ieee80211com (802.11 com lock) 
> _at_ /usr/src/sys/net80211/ieee80211_scan.c:523
>  2nd 0xc2e48400 iwi0 (network driver) 
> _at_ /usr/src/sys/modules/iwi/../../dev/iwi/if_iwi.c:1908
> KDB: stack backtrace:
> db_trace_self_wrapper(c0a39fdb,d2ce68f0,c077bb0e,c0a3c481,c2e48400,...) at 
> db_trace_self_wrapper+0x26
> kdb_backtrace(c0a3c481,c2e48400,c2e360f0,c0cc6a0c,c0cc650a,...) at 
> kdb_backtrace+0x29
> witness_checkorder(c2e48400,9,c0cc650a,774,80246,...) at 
> witness_checkorder+0x6de
> _mtx_lock_flags(c2e48400,0,c0cc650a,774,c0a55e6d,...) at _mtx_lock_flags+0xbc
> iwi_start(c2e38000,cf,c2fb8600,c2e47004) at iwi_start+0xae
> if_start(c2e38000,0,c0a4702d,17e,d2ce6a1c,...) at if_start+0x89
> ieee80211_send_nulldata(c3396000,38,c0a3bb59,6cc,c2e4700c) at 
> ieee80211_send_nulldata+0x1f4
> ieee80211_sta_pwrsave(c2e47004,1,20b,360,c2e3d000,...) at 
> ieee80211_sta_pwrsave+0x212
> scan_restart(c2e3d000,c2e47004,c0a47b0e,20b,450,...) at scan_restart+0x96
> ieee80211_bg_scan(c2e47004,c2ea3034,8,f5,c0b8e1a0,...) at 
> ieee80211_bg_scan+0x102
> ieee80211_recv_mgmt(c2e47004,c2e60e00,c3396000,80,4b,...) at 
> ieee80211_recv_mgmt+0xdaf
> ieee80211_input(c2e47004,c2e60e00,c3396000,4b,0,...) at ieee80211_input+0x142b
> iwi_intr(c2e47000,0,c0a3421e,471,c2c0a0e4,...) at iwi_intr+0x541
> ithread_loop(c2ceb940,d2ce6d38,c0a33f92,316,c2c3c804,...) at 
> ithread_loop+0x1b5
> fork_exit(c0729ea0,c2ceb940,d2ce6d38) at fork_exit+0xb8
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0, eip = 0, esp = 0xd2ce6d70, ebp = 0 ---

Yes, known and can safely be ignored.

	Sam