[Bug 252445] recent 12.2-STABLE panics on ESXi 4.1.0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Jan 5 19:46:56 UTC 2021


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

            Bug ID: 252445
           Summary: recent 12.2-STABLE panics on ESXi 4.1.0
           Product: Base System
           Version: 12.2-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: zarychtam at plan-b.pwste.edu.pl

Created attachment 221304
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=221304&action=edit
core.txt

After upgrade to the most recent 12.2-STABLE system installed on ESXi panicked
with:

[9] vmci0: <VMware Virtual Machine Communication Interface> port 0x1080-0x10bf
irq 16 at device 7.7 on pci0
<3>[9] vmci: Could not map: BAR1
<3>[9] vmci: Failed to map PCI BARs.
<4>[9] vmci: Failed to unsubscribe to event (type=0) with subscriber
(ID=0xffffffff).
[9] device_attach: vmci0 attach returned 6
[9] vmci0: <VMware Virtual Machine Communication Interface> port 0x1080-0x10bf
irq 16 at device 7.7 on pci0
<3>[9] vmci: Could not map: BAR1
<3>[9] vmci: Failed to map PCI BARs.
[9] 
[9] 
[9] Fatal trap 12: page fault while in kernel mode
[9] cpuid = 3; apic id = 03
[9] fault virtual address       = 0x410
[9] fault code          = supervisor read data, page not present
[9] instruction pointer = 0x20:0xffffffff80b822a6
[9] stack pointer               = 0x28:0xfffffe0035170600
[9] frame pointer               = 0x28:0xfffffe0035170680
[9] code segment                = base 0x0, limit 0xfffff, type 0x1b
[9]                     = DPL 0, pres 1, long 1, def32 0, gran 1
[9] processor eflags    = interrupt enabled, resume, IOPL = 0
[9] current process             = 198 (devctl)
[9] trap number         = 12
[9] panic: page fault

The kernel from 12.2-STABLE r367922 build in November 2020 works fine.

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


More information about the freebsd-bugs mailing list