Re: main cadd2ca217 doesn't boot

On Sat, May 25, 2024 at 5:47 PM Tomoaki AOKI wrote: > > On Sun, 26 May 2024 00:21:31 +0100 > Nuno Teixeira wrote: > > > Hello, > > > > Just upgraded to latest main at cadd2ca217 > > > > Boot menu shows up and then it stops earlier around: > > .. > > FreeBSD clang version ... > > > > No crash dump

Re: main cadd2ca217 doesn't boot

On Sun, 26 May 2024 00:21:31 +0100 Nuno Teixeira wrote: > Hello, > > Just upgraded to latest main at cadd2ca217 > > Boot menu shows up and then it stops earlier around: > .. > FreeBSD clang version ... > > No crash dump. > > Thanks, > > -- > Nuno Teixeira > FreeBSD UNIX: Web: https://F

main cadd2ca217 doesn't boot

Hello, Just upgraded to latest main at cadd2ca217 Boot menu shows up and then it stops earlier around: .. FreeBSD clang version ... No crash dump. Thanks, -- Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org

Re: panic: lock "tmpfsni" 0xfffff80721307090 already initialized

On Sat, May 25, 2024 at 1:32 AM Alexander Leidinger wrote: > > Hi, > > [123095] panic: lock "tmpfsni" 0xf80721307090 already initialized > [123095] cpuid = 8 > [123095] time = 1716597585 > [123095] KDB: stack backtrace: > [123095] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0

Re: _mtx_lock_sleep: recursed on non-recursive mutex CAM device lock @ /..../sys/cam/nvme/nvme_da.c:469

Am 2024-05-22 22:45, schrieb Alexander Leidinger: Am 2024-05-22 20:53, schrieb Warner Losh: First order: Looks like we're trying to schedule a trim, but that fails due to a malloc issue. So then, since it's a malloc issue, we wind up trying to automatically reschedule this I/O, which recurs

panic: lock "tmpfsni" 0xfffff80721307090 already initialized

Hi, [123095] panic: lock "tmpfsni" 0xf80721307090 already initialized [123095] cpuid = 8 [123095] time = 1716597585 [123095] KDB: stack backtrace: [123095] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe08285c9690 [123095] vpanic() at vpanic+0x13f/frame 0xfe08285c97