Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jun 2024 15:53:06 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 279738] Hyper-V: Kernel panic: acquiring blockable sleep lock with spinlock or critical section held
Message-ID:  <bug-279738-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279738

            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=3D251453&action=
=3Dedit
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 virtual=
ized
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.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279738-227>