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

            Bug ID: 298645
           Summary: panic: VERIFY3B(link->list_next == ((void *)0), ==,
                    link->list_prev == ((void *)0)) failed (0 == 1)
           Product: Base System
           Version: 16.0-CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 274875
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=274875&action=edit
photo of monitor with panic crash info

This happens about once a day. The machine is an older and slower unit
and normally very stable. It just does what it does, which is not much
other than giving me access to a serial port.

Tue Sep 15 18:55:52 UTC 2026

FreeBSD/amd64 (callisto) (ttyv0)

login: Sep 15 18:57:18 callisto su[3340]: admsys to root on /dev/pts/0
panic: VERIFY3B(link->list_next == ((void *)0), ==, link->list_prev == ((void
*)0)) failed (0 == 1)

cpuid = 0
time = 1789614258
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x36/frame 0xffffff0067a9cb80
vpanic() at vpanic+0x149/frame 0xffffff0067a9ccb0
spl_panic() at spl_panic+0x3a/frame 0xffffff0067a9cd10
list_link_active() at list_link_active+0x60/frame 0xffffff0067a9cd30
dnode_dest() at dnode_dest+0x89/frame 0xffffff0067a9cd60
uma_zfree_arg() at uma_zfree_arg+0xaa/frame 0xffffff0067a9cdb0
dnode_destroy() at dnode_destroy+0x1b1/frame 0xffffff0067a9cdf0
dnode_buf_evict_async() at dnode_buf_evict_async+0x68/frame 0xffffff0067a9ce30
taskqueue_run_locked() at taskqueue_run_locked+0x1eb/frame 0xffffff0067a9cec0
taskqueue_thread_loop() at taskqueue_thread_loop+0xd3/frame 0xffffff0067a9cef0
fork_exit() at fork_exit+0x82/frame 0xffffff0067a9cf30
fork_trampoline() at fork_trampoline+0xe/frame 0xffffff0067a9cf30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic
[ thread pid 7 tid 100137 ]
Stopped at      kdb_enter+0x33: movq    $0,0x117cdb2(%rip)
db> 

Not sure what other info I can provide. This was taken from a photo
of the monitor and done by hand where I think I managed to get it
all correct.

Happens every day more or less.


-- 
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken

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

Reply via email to