https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667
--- Comment #3 from Seb <s.d.j.belc...@gmail.com> --- Turns out TrueNAS does not output crash-dumps in the way I was expecting, I've has another 9 kernel panics since my last comment but all produced only text-dumps. I *think* I've got it setup to do a core-dump next crash now using sysctl to override the text-dump pending flag... so hopefully will have a vmcore for you soon. The panic string has been different the last few times: Dump header from device: /dev/ada1p3 Architecture: amd64 Architecture Version: 4 Dump Length: 1751040 Blocksize: 512 Compression: none Dumptime: Sun Nov 1 08:33:26 2020 Hostname: nas.lan Magic: FreeBSD Text Dump Version String: FreeBSD 12.2-RC3 7c4ec6ff02c(HEAD) TRUENAS Panic String: Bad tailq NEXT(0xffffffff82134d98->tqh_last) != NULL Dump Parity: 3497888606 Bounds: 3 Dump Status: good Another TrueNAS user is reporting similar issues and believes it may be related to the Intel 10Gb 'ix' drivers. Is that a possibility? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
