[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 277538] panic: vm_page_assert_unbusied: busy_lock owned by me"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 06 Mar 2024 20:17:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277538
Bug ID: 277538
Summary: panic: vm_page_assert_unbusied: busy_lock owned by me
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: jfc@mit.edu
Rebooting after removing a swap device caused a panic
panic: vm_page_assert_unbusied: page 0xffffa000e7d451e0 busy_lock 0xd6ba02c2
owned by me (0xffff0000d6ba02c0) @ /usr/src/sys/vm/vm_object.c:897
Longer version:
I unplugged a USB drive from an arm64 SBC (RockPro64). It contained the swap
device so the system was not happy. I plugged it back in but the system did
not understand that the device I plugged in was the same device I removed. I
could not "swapoff" to get the data off the drive. I rebooted and got the
panic above.
I am running a recent 15.0-CURRENT based on
c6a6ec85a70314b8270e25a06e77e2e7c95c7055.
No crash dump. The kernel debugger hung when I asked it to dump. It probably
could not figure out where to dump. Here is the text on the console:
[unplugged swap device]
# swapinfo
Device 1K-blocks Used Avail Capacity
/dev/#C:0xb2 8069120 26852 8042268 0%
[plugged device back in]
# swapinfo
Device 1K-blocks Used Avail Capacity
/dev/#C:0xb2 8069120 26852 8042268 0%
root@variegatus:~ # reboot
Mar 6 20:03:25 variegatus reboot[80617]: rebooted by root
swap_pager: I/O error - pagein failed; blkno 3033084,size 4096, error 6
vm_fault: pager read error, pid 50404 (sshd)
swap_pager: I/O error - pagein failed; blkno 3033109,size 4096, error 6
vm_fault: pager read error, pid 50402 (sshd)
swap_pager: I/O error - pagein failed; blkno 2793364,size 8192, error 6
swap_pager: I/O error - pagein failed; blkno 2793378,size 8192, error 6
swap_pager: I/O error - pagein failed; blkno 2793340,size 8192, error 6
vm_fault: pager read error, pid 2600 (getty)
vm_fault: pager read error, pid 2602 (getty)
swap_pager: I/O error - pagein failed; blkno 2797106,size 8192, error 6
swap_pager: I/O error - pagein failed; blkno 2793206,size 8192, error 6
swap_pager: I/O error - pagein failed; blkno 2793359,size 20480, error 6
vm_fault: pager read error, pid 87805 (sshd)
vm_fault: pager read error, pid 2599 (getty)
vm_fault: pager read error, pid 2601 (getty)
vm_fault: pager read error, pid 2600 (getty)
panic: vm_page_assert_unbusied: page 0xffffa000e7d451e0 busy_lock 0xd6ba02c2
owned by me (0xffff0000d6ba02c0) @ /usr/src/sys/vm/vm_object.c:897
cpuid = 4
time = 1709755406
KDB: stack backtrace:
db_trace_self() at db_trace_self
db_trace_self_wrapper() at db_trace_self_wrapper+0x38
vpanic() at vpanic+0x1a8
panic() at panic+0x48
vm_object_terminate() at vm_object_terminate+0x2a4
vm_object_deallocate() at vm_object_deallocate+0x2cc
vm_map_process_deferred() at vm_map_process_deferred+0xa8
vm_map_remove() at vm_map_remove+0xc8
vmspace_exit() at vmspace_exit+0x138
exit1() at exit1+0x4e8
sigexit() at sigexit+0x154
postsig() at postsig+0x11c
ast_sig() at ast_sig+0x128
ast_handler() at ast_handler+0xc8
ast() at ast+0x24
handle_el0_sync() at handle_el0_sync+0x6c
--- exception, esr 0x56000000
KDB: enter: panic
[ thread pid 87805 tid 100300 ]
--
You are receiving this mail because:
You are the assignee for the bug.