Date: Tue, 9 Apr 2024 19:02:11 +0200 From: FreeBSD User <freebsd@walstatt-de.de> To: Gleb Smirnoff <glebius@freebsd.org> Cc: current@freebsd.org, David Wolfskill <david@catwhisker.org> Subject: Re: Panic after update main-n269202-4e7aa03b7076 -> n269230-f6f67f58c19d Message-ID: <20240409190238.32f2be63@thor.intern.walstatt.dynvpn.de> In-Reply-To: <ZhVqaV9hJaq3zeor@cell.glebi.us> References: <ZhUqu8nXeQK9T2nH@albert.catwhisker.org> <ZhVqaV9hJaq3zeor@cell.glebi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Tue, 9 Apr 2024 09:18:49 -0700
Gleb Smirnoff <glebius@freebsd.org> schrieb:
> On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote:
> D> --- trap 0xc, rip = 0xffffffff80b208c5, rsp = 0xfffffe048c204920, rbp = 0xfffffe
> D> 048c204960 ---
> D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame 0xfffffe048c204960
> D> clnt_vc_create() at clnt_vc_create+0x4f4/frame 0xfffffe048c204ab0
> D> local_rpcb() at local_rpcb+0x11b/frame 0xfffffe048c204b50
> D> rpcb_unset() at rpcb_unset+0x24/frame 0xfffffe048c204bb0
> D> svc_tp_create() at svc_tp_create+0xee/frame 0xfffffe048c204c90
> D> sys_nlm_syscall() at sys_nlm_syscall+0x3d0/frame 0xfffffe048c204e00
> D> amd64_syscall() at amd64_syscall+0x158/frame 0xfffffe048c204f30
> D> fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe048c204f30
> D> --- syscall (154, FreeBSD ELF64, nlm_syscall), rip = 0x3f00a2dfd2a, rsp = 0x3f00
> D> 96f7168, rbp = 0x3f0096f7230 ---
> D> KDB: enter: panic
> D> [ thread pid 1208 tid 101107 ]
> D> Stopped at kdb_enter+0x33: movq $0,0x104eb92(%rip)
> D> db>
>
> This should be fixed by just pushed e205fd318a296ffdb7392486cdcec7f660fcffcf.
>
> Sorry for that!
>
Hello all.
The crash is still present on the most recent checked out sources as of minutes ago.
I just checked out on HEAD the latest commits (see below, just for the record and to prevent
being wrong here).
[...]
commit 841cf52595b6a6b98e266b63e54a7cf6fb6ca73e (HEAD -> main, origin/main, origin/HEAD)
Author: Alan Cox <alc@FreeBSD.org>
Date: Mon Apr 8 00:05:27 2024 -0500
arm64 pmap: Add ATTR_CONTIGUOUS support [Part 2]
Create ATTR_CONTIGUOUS mappings in pmap_enter_object(). As a result,
when the base page size is 4 KB, the read-only data and text sections
of large (2 MB+) executables, e.g., clang, can be mapped using 64 KB
pages. Similarly, when the base page size is 16 KB, the read-only
data section of large executables can be mapped using 2 MB pages.
Rename pmap_enter_2mpage(). Given that we have grown support for 16 KB
base pages, we should no longer include page sizes that may vary, e.g.,
2mpage, in pmap function names. Requested by: andrew
Co-authored-by: Eliot Solomon <ehs3@rice.edu>
Differential Revision: https://reviews.freebsd.org/D44575
commit e205fd318a296ffdb7392486cdcec7f660fcffcf
Author: Gleb Smirnoff <glebius@FreeBSD.org>
Date: Tue Apr 9 09:16:52 2024 -0700
rpc: use new macros to lock socket buffers
Fixes: d80a97def9a1db6f07f5d2e68f7ad62b27918947
commit cb20a74ca06381e96c41cb4495d633710cc6cb79
Author: Stephen J. Kiernan <stevek@FreeBSD.org>
Date: Wed Apr 3 17:04:57 2024 -0400
--
O. Hartmann
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240409190238.32f2be63>