Date: Tue, 9 Feb 2021 07:41:03 -0700 From: Alan Somers <asomers@freebsd.org> To: Santiago Martinez <sm@codenetworks.net> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: Current - kernel dump while plasma loading. Message-ID: <CAOtMX2hKF%2BH-m0O4=yciNFvbfWLcYo0JjbisycnOpTxyKDnKxw@mail.gmail.com> In-Reply-To: <c57bf707-dce5-fb8c-5221-072892bd9e19@codenetworks.net> References: <c57bf707-dce5-fb8c-5221-072892bd9e19@codenetworks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 9, 2021 at 3:52 AM Santiago Martinez <sm@codenetworks.net> wrote: > Hi there, this morning i did the usual git pull and make.. > > After reboot and loading the desktop (while starting plasma with drm), i > get a kernel dump. > > This was ok until this morning... > > This is the info: > > root@tucho:/var/crash # cat info.last > Dump header from device: /dev/ada0p2 > Architecture: amd64 > Architecture Version: 2 > Dump Length: 1381969920 > Blocksize: 512 > Compression: none > Dumptime: 2021-02-09 10:24:21 +0000 > Hostname: tucho > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 14.0-CURRENT #5 main-n244705-504ebd612ec6: Tue > Feb 9 10:20:32 GMT 2021 > root@tucho:/usr/obj/usr/src/amd64.amd64/sys/TUCHO > Panic String: VERIFY(avl_find(tree, new_node, &where) == NULL) failed > > Dump Parity: 2603051126 > Bounds: 6 > Dump Status: good > > > Best regards. > > Santi > I can tell you why it was "fine" until this morning. It's because ZFS assertions weren't actually enabled until last night. So this isn't a newly introduced ZFS bug, just a newly noticed one. Could you please post the full stack trace? -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2hKF%2BH-m0O4=yciNFvbfWLcYo0JjbisycnOpTxyKDnKxw>