Hi All,
Just wanted a sanity check before filing a PR.  I am running r290688 and
am seeing a LOR being triggered in the mpr(4) device:

$ uname -ar
FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r290688: Wed Nov 11
21:28:26 PST 2015     root@srd0013:/usr/obj/usr/src/sys/GENERIC  amd64

<dmesg snip>
lock order reversal:
 1st 0xfffff8000d26bc60 CAM device lock (CAM device lock) @
 2nd 0xfffffe00012811c0 MPR lock (MPR lock) @
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
witness_checkorder() at witness_checkorder+0xe79/frame 0xfffffe04608ee910
__mtx_lock_flags() at __mtx_lock_flags+0xa4/frame 0xfffffe04608ee960
xpt_action_default() at xpt_action_default+0xb6c/frame 0xfffffe04608ee9b0
scsi_scan_bus() at scsi_scan_bus+0x1d5/frame 0xfffffe04608eea20
xpt_scanner_thread() at xpt_scanner_thread+0x15c/frame 0xfffffe04608eea70
fork_exit() at fork_exit+0x84/frame 0xfffffe04608eeab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe04608eeab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

I can file a PR for this as a quick search on my end didn't return any
bugs related to this.  Checking here first to make sure this isn't
already known/expected behavior.


Pete Wright
twitter => @nomadlogicLA

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to