From nobody Sun Aug 29 08:37:12 2021 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EAC8F17A2E5C for ; Sun, 29 Aug 2021 08:37:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gy6JW68MHz58jJ for ; Sun, 29 Aug 2021 08:37:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 7CB33216BA for ; Sun, 29 Aug 2021 08:37:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Subject: Re: Panic after update: stable/12-n233561-42cb78bdd49 - n233682-a436245ccf1 To: stable@freebsd.org References: From: Andriy Gapon Message-ID: <6bdfe94a-1777-8267-b9f5-ccd55da3b8ce@FreeBSD.org> Date: Sun, 29 Aug 2021 11:37:12 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.13.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-ThisMailContainsUnwantedMimeParts: N On 29/08/2021 06:54, David Wolfskill wrote: > The core.txt.0 file claims that the backtrace is: > > panic: vm_fault: fault on nofault entry, addr: 0xfffffe10384e2000 > cpuid = 7 > time = 1630206013 > KDB: stack backtrace: > #0 0xffffffff80bebfc5 at kdb_backtrace+0x65 > #1 0xffffffff80ba017b at vpanic+0x17b > #2 0xffffffff80b9fff3 at panic+0x43 > #3 0xffffffff80f5be62 at vm_fault+0x24f2 > #4 0xffffffff80f59850 at vm_fault_trap+0x60 > #5 0xffffffff8104fb4c at trap_pfault+0x19c > #6 0xffffffff8104f046 at trap+0x286 > #7 0xffffffff81026eb8 at calltrap+0x8 > Uptime: 2m18s As far as I can tell, the stack trace shows only what was called _after_ the trap / fault. So, the interesting part is missing. -- Andriy Gapon