https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288722

--- Comment #29 from John Kennedy <[email protected]> ---
(In reply to Dag-Erling Smørgrav from comment #28)
I tried with 15.0-PRERELEASE FreeBSD 15.0-PRERELEASE #83
main-n279546-96bd22f2bd80, so yours plus 3 patches that were touching on pf and
icmp, but had issues on poudriere cleanup when I hit CTRL-C.  I've had failures
on poudriere start and cleanup in the past, so that isn't a change for me.

I do have debugging turned on, AFAIK (pretty default, haven't disabled it):

# sysctl debug.kdb.available
debug.kdb.available: ddb

...
[00:00:30] Error: Signal SIGINT caught, cleaning up and exiting
[15x-master] [2025-08-11_16h26m58s] [sigint] Queued: 44 Built: 0  Failed: 0 
Skipped: 0  Ignored: 0  Fetched: 0  Tobuild: 44  Time: 00:00:22
[00:00:30] Logs:
/usr/local/poudriere/data/logs/bulk/15x-master/2025-08-11_16h26m58s
[00:00:30] Cleaning up
[00:00:30] Unmounting file systems
panic: VERIFY3U(BP_GET_BIRTH(bp), ==, BP_GET_BIRTH(&found->le_bp)) failed
(1594640 == 1594639)

cpuid = 5
time = 1754954849
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00e9a159c0
vpanic() at vpanic+0x136/frame 0xfffffe00e9a15af0
spl_panic() at spl_panic+0x3a/frame 0xfffffe00e9a15b50
dsl_livelist_iterate() at dsl_livelist_iterate+0x2f5/frame 0xfffffe00e9a15c30
bpobj_iterate_blkptrs() at bpobj_iterate_blkptrs+0x24c/frame 0xfffffe00e9a15ce0
bpobj_iterate_impl() at bpobj_iterate_impl+0x171/frame 0xfffffe00e9a15d70
dsl_process_sub_livelist() at dsl_process_sub_livelist+0x5c/frame
0xfffffe00e9a15df0
spa_livelist_delete_cb() at spa_livelist_delete_cb+0x122/frame
0xfffffe00e9a15ea0
zthr_procedure() at zthr_procedure+0xa5/frame 0xfffffe00e9a15ef0
fork_exit() at fork_exit+0x82/frame 0xfffffe00e9a15f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00e9a15f30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 5 tid 100322 ]
Stopped at      kdb_enter+0x33: movq    $0,0x1233342(%rip)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to