Date: Sun, 1 Sep 2019 15:50:15 +0200 From: Guido Falsi <madpilot@FreeBSD.org> To: Evilham <contact@evilham.com> Cc: current@freebsd.org, fs@FreeBSD.org Subject: Re: panic: No vop_need_inactive Message-ID: <67cc0491-2b4a-f166-7319-c6dce0bfee9d@FreeBSD.org> In-Reply-To: <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/09/19 15:25, Evilham wrote: > > FWIW: I am not 100% sure I it's the same panic, I am missing a cable ATM > to get a full dump, but I do think they sound very similar. I'm not using serial communications to get dumps, not necessary anymore. You can have the kernel debugger output this information to disk (in /var/crash) using the "textdump dump" command. You can also usse the capture buffer in ddb to perform other operations and have the screen output saved in a buffer. This is all documented in ddb(4) and textdump(4) (regarding the crash it has been reported as fixed in a later commit) -- Guido Falsi <madpilot@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67cc0491-2b4a-f166-7319-c6dce0bfee9d>