https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276051
--- Comment #1 from Kurt Jaeger <p...@freebsd.org> --- Another crash during a poudriere jail -c -j 150 -a amd64 -b -m src=/usr/src -S /usr/src run, this time with another cause: panic: Bad link elm 0xfffff804781f9b20 prev->next != elm KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe02e4bf8a70 vpanic() at vpanic+0x131/frame 0xfffffe02e4bf8ba0 panic() at panic+0x43/frame 0xfffffe02e4bf8c00 pmap_remove_pages() at pmap_remove_pages+0x117c/frame 0xfffffe02e4bf8d50 vmspace_exit() at vmspace_exit+0x7d/frame 0xfffffe02e4bf8d80 exit1() at exit1+0x533/frame 0xfffffe02e4bf8df0 sys_exit() at sys_exit+0xd/frame 0xfffffe02e4bf8e00 amd64_syscall() at amd64_syscall+0x153/frame 0xfffffe02e4bf8f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe02e4bf8f30 --- syscall (1, FreeBSD ELF64, exit), rip = 0x82cd9e47a, rsp = 0x82822f408, rbp = 0x82822f420 --- KDB: enter: panic This time this ddb script was active to catch more of the system state in the msgbuf: ddb script kdb.enter.panic='textdump set; capture on; show allpcpu; bt; ps; alltrace; show alllocks; textdump dump; reset' See https://people.freebsd.org/~pi/20240101-crash-bad-link -- You are receiving this mail because: You are the assignee for the bug.
