Re: ipw(4) freeze CURRENT

From: Denis Shaposhnikov <dsh_at_vlink.ru>
Date: Sun, 18 Mar 2007 16:11:05 +0300
On 03/18/07 14:06, Lukas Ertl wrote:

> Could you try the attached patch?

Thank you! I've tried it and it fixes

ipw0: link state changed to UP
lock order reversal:
  1st 0xc1d8db50 ipw0 (network driver) _at_ 
/var/FreeBSD/src/sys/modules/ipw/../../dev/ipw/if_ipw.c:1208
  2nd 0xc06c94ac udp (udp) _at_ /var/FreeBSD/src/sys/netinet/udp_usrreq.c:296
KDB: stack backtrace:
db_trace_self_wrapper(c0611a83) at db_trace_self_wrapper+0x25
kdb_backtrace(0,ffffffff,c0689810,c068acd8,c0646844,...) at 
kdb_backtrace+0x29
witness_checkorder(c06c94ac,9,c061fb61,128) at witness_checkorder+0x586
_mtx_lock_flags(c06c94ac,0,c061fb61,128) at _mtx_lock_flags+0x84
udp_input(c1d98b00,14,c0669380,200a8c0,0,...) at udp_input+0x1e5
ip_input(c1d98b00) at ip_input+0x5c9
netisr_dispatch(2,c1d98b00,0,c1d81c00,c1dc0800,...) at netisr_dispatch+0x58
ether_demux(c1d81c00,c1d98b00,c1d59800,c1d98b00,cc493be0,...) at 
ether_demux+0x28a
ether_input(c1d81c00,c1d98b00,c1d8d004,c1d81c00,c1d59800,...) at 
ether_input+0x21e
ieee80211_deliver_data(c1d98b00,79,cc493c30,c078c2e0,cc493c10,...) at 
ieee80211_deliver_data+0x74
ieee80211_input(c1d8d004,c1d98b00,c1d59800,3a,0,...) at 
ieee80211_input+0x9ee
ipw_intr(c1d8d000) at ipw_intr+0x44f
ithread_execute_handlers(c1d4a480,c1ccd880) at 
ithread_execute_handlers+0x121
ithread_loop(c1d407e0,cc493d38) at ithread_loop+0x66
fork_exit(c049b5ec,c1d407e0,cc493d38) at fork_exit+0xac
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xcc493d70, ebp = 0 ---

which show me unpatched version of ipw(4). What about stability, I can 
say it still works. I'll watch for it and post a report on the next weekend.

-- 
DSS5-RIPE DSS-RIPN 2:550/5068_at_fidonet 2:550/5069_at_fidonet
xmpp:dsh_at_vlink.ru mailto:dsh_at_vlink.ru http://neva.vlink.ru/~dsh/
Received on Sun Mar 18 2007 - 12:11:07 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:06 UTC