Unexpected reboot after ctld run into trouble.

[Willem Jan Withagen]

Hi,

Found the following in my logs:
Losts of
----
(0:4:0/0): Task Action: LUN Reset
(0:4:0/0): CTL Status: Command Completed Successfully
sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in
queue awaiting acceptance (740688 occurrences)
(0:4:0/0): Task Action: LUN Reset
(0:4:0/0): CTL Status: Command Completed Successfully
sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in
queue awaiting acceptance (713721 occurrences)
(0:4:0/0): Task Action: LUN Reset
(0:4:0/0): CTL Status: Command Completed Successfully
sonewconn: pcb 0xfffff8004e69e930: Listen queue overflow: 8 already in
queue awaiting acceptance (691776 occurrences)
----

Which then ends in:
----
panic: deadlkres: possible deadlock detected for 0xfffff8001ee94920,
blocked for 1801009 ticks


cpuid = 1
Uptime: 14d13h13m47s
Dumping 7557 out of 8175
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%Table 'FACP' at
0xcfedbcf8
----

The system is running ZFS with ZFS-on-root:
FreeBSD zfs.digiware.nl 10.1-STABLE FreeBSD 10.1-STABLE #221 r282282:
Fri May  1 06:51:41 CEST 2015

This could stem from the fact that I woke up my Win8 PC which has a
iscsi volume mounted. It is used to store security cam captures on and
does have somewhat bigger traffic on it.

Suggestions or question to look at are welcom.

--WjW


I do have a core in /var/crash, but will need some guidance to retreive
stuff from it.