From owner-freebsd-fs@freebsd.org Sun Sep 1 13:50:17 2019 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D3C59DAB97 for ; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Lvjj5G76z4L66 for ; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id B104CDAB93; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) Delivered-To: fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AF6B3DAB91; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lvjj2yvzz4L63; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from marvin.madpilot.net (host193-122-dynamic.17-87-r.retail.telecomitalia.it [87.17.122.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id D35F51C046; Sun, 1 Sep 2019 13:50:16 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Subject: Re: panic: No vop_need_inactive To: Evilham Cc: current@freebsd.org, fs@FreeBSD.org References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> From: Guido Falsi Message-ID: <67cc0491-2b4a-f166-7319-c6dce0bfee9d@FreeBSD.org> Date: Sun, 1 Sep 2019 15:50:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:50:17 -0000 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