[Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 14 Jun 2024 15:53:06 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279738 Bug ID: 279738 Summary: Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: gbe@FreeBSD.org Created attachment 251453 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251453&action=edit Kernel Panic On a recent current @fbff6d54da146e98ec2ce4ebfbb86339d4f9fa21 I see the attached kernel panic very early at boot. I can't provide a crash dump only a screenshot of the panic. It's a virtualized system on Hyper-V with two cores and 2048 MB RAM. UFS is the main filesystem and ZFS is only used for /usr/lib/debug space, if the matters. Latest working kernel is from the 7th of June. -- You are receiving this mail because: You are the assignee for the bug.