Date: Mon, 02 Nov 2020 21:13:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2) Message-ID: <bug-250667-227-nIzKZp2oSu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250667-227@https.bugs.freebsd.org/bugzilla/> References: <bug-250667-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250667 --- Comment #3 from Seb <s.d.j.belcher@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 u= sing sysctl to override the text-dump pending flag... so hopefully will have a vmcore for you soon.=20 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) !=3D NULL Dump Parity: 3497888606 Bounds: 3 Dump Status: good Another TrueNAS user is reporting similar issues and believes it may be rel= ated to the Intel 10Gb 'ix' drivers. Is that a possibility? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250667-227-nIzKZp2oSu>