[Bug 252375] kernel panic during reboot "softdep_waitidle: work added after flush"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 23 Feb 2025 20:34:56 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252375
Lexi Winter <lexi@hemlock.eden.le-fay.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|Overcome By Events |---
Status|Closed |New
CC| |lexi@hemlock.eden.le-fay.or
| |g
--- Comment #5 from Lexi Winter <lexi@hemlock.eden.le-fay.org> ---
i recently saw this on 15.0 as of ~ 1 week ago.
Feb 23 02:10:40 amaryllis syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 0 0 done
All buffers synced.
panic: softdep_waitidle: work added after flush
cpuid = 0
time = 1740276653
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe004b09a9d0
vpanic() at vpanic+0x136/frame 0xfffffe004b09ab00
panic() at panic+0x43/frame 0xfffffe004b09ab60
softdep_flushfiles() at softdep_flushfiles+0x475/frame 0xfffffe004b09ac00
ffs_unmount() at ffs_unmount+0x66/frame 0xfffffe004b09ac80
dounmount() at dounmount+0x649/frame 0xfffffe004b09acf0
vfs_unmountall() at vfs_unmountall+0x6a/frame 0xfffffe004b09ad20
bufshutdown() at bufshutdown+0x32c/frame 0xfffffe004b09ad70
kern_reboot() at kern_reboot+0x703/frame 0xfffffe004b09adb0
sys_reboot() at sys_reboot+0x396/frame 0xfffffe004b09ae00
amd64_syscall() at amd64_syscall+0x15a/frame 0xfffffe004b09af30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe004b09af30
--- syscall (55, FreeBSD ELF64, reboot), rip = 0x28db3a, rsp = 0x8209651a8, rbp
= 0x820965290 ---
KDB: enter: panic
[ thread pid 1 tid 100002 ]
Stopped at kdb_enter+0x33: movq $0,0x1052682(%rip)
db>
unfortunately this VM has no swap space, so i couldn't get a dump, and i
haven't managed to reproduce it, but the problem still seems to be present.
--
You are receiving this mail because:
You are the assignee for the bug.