[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev)

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 241639
           Summary: Fatal trap 12: page fault ... current process = 0
                    (vmbusdev)
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: michael.adm at gmail.com

Created attachment 208757
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208757&action=edit
Attachment 1 (Network adapter)

Fatal trap 12: page fault ... current process = 0 (vmbusdev)

This applies to these OS versions:
FreeBSD-11.2 RELEASE amd64
FreeBSD-11.3 RELEASE-amd64
FreeBSD-11.3 STABLE amd64 20191025 r354051
FreeBSD-12.0 RELEASE amd64
FreeBSD-12.1 RC1 amd64
FreeBSD-12.1 RC2 amd64
FreeBSD-12.1 STABLE amd64 20191025 r354051
FreeBSD-13.0 CURRENT amd64 20191025 r354057

For all these OSs, this bug is the same.

Hypervisor: Windows 2019 server Hyper-V (all update and drivers are the
latest).
VM: Hyper-V generation V2.
Network adapter: Mellanox ConnectiX-3 EN 10G SR-IOV enabled, (Attachment 1).

All VM-OSs were installed under the same conditions, (Attachment 2):
mem: 6GB, HDD: 127GB;
FS: Auto (ZFS) Guided Root-on-ZFS, (Attachment 3);
ZFS: GPT (BIOS+UEFI), (Attachment 4);
LAN: one HV-V2 network adapter, (Attachment 2);

When we enable SR-IOV on the port, (Attachment 5),
and load the Mellanox driver in the OS
  root at frw03v2:~ # kldload mlx4en
everything works without problems as it should.
Status of network connection is OK (Support SR-IOV active), (Attachment 6).
Add to /boot/loader.conf to automatically load the ConnectiX-3 driver
  mlx4en_load="YES"
and reboot VM-OS.
Result - Fatal trap on loading stage (Attachment 7-11).

As a temporary solution to this problem,
the pfSense community suggested this:
in /boot/loader.conf add
  kern.cam.boot_delay="10000"
Indeed, all versions of the FreeBSD OS will now boot OK
(with parameter kern.cam.boot_delay="10000"
in the configuration file /boot/loader.conf),
but where is the guarantee that this focus
makes the system stable under load?
And yet, this focus stops working when
parameter kern.cam.boot_delay is less than 1000.
For example, if kern.cam.boot_delay="500",
then when booting the system - the same Fatal trap.

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