Willem Jan Withagen wrote this message on Mon, Feb 23, 2015 at 12:55 +0100:> Came home last night to find out that my ZFS fileserver has rebooted.... > > Dmesg is loaded with sonewconn messages.... > And after a while the system thinks it is enough... > --- > Panic String: deadlkres: possible deadlock detected for > 0xfffff800133f9000, blocked for 1800789 ticks > ----[...]> FreeBSD 10.1-STABLE #101 r276583: Sat Jan 3 06:51:10 CET 2015 > root at zfs.digiware.nl:/home/obj/amd64/usr/srcs/src10/src/sys/ZFS amd64 > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512Upgrade your kernel: https://svnweb.freebsd.org/base?view=revision&revision=278800 This change will probably fix your panic... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."
On 25-2-2015 01:43, John-Mark Gurney wrote:> Willem Jan Withagen wrote this message on Mon, Feb 23, 2015 at 12:55 +0100: >> Came home last night to find out that my ZFS fileserver has rebooted.... >> >> Dmesg is loaded with sonewconn messages.... >> And after a while the system thinks it is enough... >> --- >> Panic String: deadlkres: possible deadlock detected for >> 0xfffff800133f9000, blocked for 1800789 ticks >> ---- > > [...] > >> FreeBSD 10.1-STABLE #101 r276583: Sat Jan 3 06:51:10 CET 2015 >> root at zfs.digiware.nl:/home/obj/amd64/usr/srcs/src10/src/sys/ZFS amd64 >> FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 > > Upgrade your kernel: > https://svnweb.freebsd.org/base?view=revision&revision=278800 > > This change will probably fix your panic... >Hi John-Marck, Thanx for the info. I upgraded after last Monday when I saw the crash: 10.1-STABLE FreeBSD 10.1-STABLE #152 r279218: Tue Feb 24 01:07:14 So that is well beyond you revision. I have not seen the messages after that. Just out of curiosity: Is this in the aftermath of the big debate about the callout restructuring? Thanx, --WjW