LOR if_addr_lock/ifnet_rw

2014-12-10 Thread Mateusz Kwiatkowski 

Hi,

I got that LOR few minutes ago:

lock order reversal:
 1st 0xf800094f4990 if_addr_lock (if_addr_lock) @ 
/usr/src/sys/netinet/igmp.c:1716

 2nd 0x818800d0 ifnet_rw (ifnet_rw) @ /usr/src/sys/net/if.c:243
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
0xfe01dd5964b0

kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe01dd596560
witness_checkorder() at witness_checkorder+0xdad/frame 0xfe01dd5965f0
__rw_rlock() at __rw_rlock+0x9a/frame 0xfe01dd596690
ifnet_byindex() at ifnet_byindex+0x22/frame 0xfe01dd5966b0
igmp_intr() at igmp_intr+0x1f/frame 0xfe01dd596730
netisr_dispatch_src() at netisr_dispatch_src+0x86/frame 0xfe01dd5967a0
igmp_v1v2_queue_report() at igmp_v1v2_queue_report+0x186/frame 
0xfe01dd5967e0

igmp_fasttimo() at igmp_fasttimo+0x3ee/frame 0xfe01dd5968c0
pffasttimo() at pffasttimo+0x54/frame 0xfe01dd5968f0
softclock_call_cc() at softclock_call_cc+0x19c/frame 0xfe01dd5969d0
softclock() at softclock+0x47/frame 0xfe01dd5969f0
intr_event_execute_handlers() at intr_event_execute_handlers+0x93/frame 
0xfe01dd596a30

ithread_loop() at ithread_loop+0xa6/frame 0xfe01dd596a70
fork_exit() at fork_exit+0x84/frame 0xfe01dd596ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe01dd596ab0
--- trap 0, rip = 0, rsp = 0xfe01dd596b70, rbp = 0 ---

It caused lost of connectivity for a minute.
Other info:
FreeBSD darkstar 11.0-CURRENT FreeBSD 11.0-CURRENT #3 r274373: Tue Nov 
11 14:23:38 CET 2014 root@darkstar:/usr/obj/usr/src/sys/GENERIC  amd64


iwn0: RF switch: radio enabled
iwn0: iwn_read_firmware: ucode rev=0x12a80601
iwn0: iwn_read_firmware: ucode rev=0x12a80601
iwn0: iwn_read_firmware: ucode rev=0x12a80601
iwn0: Intel(R) Centrino(R) Wireless-N 2200 BGN mem 
0xf2c0-0xf2c01fff irq 17 at device 0.0 on pci3

iwn0: iwn_read_firmware: ucode rev=0x12a80601

--
Kind Regards,
Mateusz Kwiatkowski

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Mergemaster and bootpool on CURRENT

2014-11-02 Thread Mateusz Kwiatkowski 

Hi,

I've just updated to r273910 and this behavior of mergemaster -Fi 
confused me:


The installed file /boot has the type symbolic link but the new 
version has the type directory


/boot is symlink, indeed:

# ls -ld /boot lrwxr-xr-x 1 root wheel 13 Sep 3 03:37 /boot - 
bootpool/boot


# zfs list NAME USED AVAIL REFER MOUNTPOINT
bootpool 978M 990M 977M /bootpool

Shouldn't mergemaster ignore it? This is ZFS on eli setup from 
bsdinstall (don't remember which version).


# zpool status -v
  pool: bootpool
 state: ONLINE
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
bootpoolONLINE   0 0 0
  ada0p2ONLINE   0 0 0

errors: No known data errors

  pool: zroot
 state: ONLINE
  scan: none requested
config:

NAME  STATE READ WRITE CKSUM
zroot ONLINE   0 0 0
  ada0p4.eli  ONLINE   0 0 0

errors: No known data errors

--
Regards,
Mateusz Kwiatkowski

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org