[Bug 234341] accessing hn0 when running CURRENT under Hyper-V on Windows 10 Pro crashes the machine

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 234341
           Summary: accessing hn0 when running CURRENT under Hyper-V on
                    Windows 10 Pro crashes the machine
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: d8zNeCFG at aon.at

Scenario 1:
- Running CURRENT (r341726) under Hyper-V on Windows 10 Professional
- Using legacy networking in Hyper-V
- loading if_de in boot/loader.conf

Result 1:
- Working fine.

Scenario 2:
- Running CURRENT (r341726) under Hyper-V on Windows 10 Professional
- Using virtualized networking in Hyper-V
- loading hv_netvsc, hv_storvsc, hv_utils, hv_vmbus in boot/loader.conf

Result 2:
- Sending single packets across hn0 works (single-user, using ping)
- When accessing hn0 with a little higher load, the machine crashes (Hyper-V
reverts to nun-running state)
- No core dump etc.

Scenario 3:
- Running openSUSE 15.0 under Hyper-V on Windows 10 Professional
- Using virtualized networking in Hyper-V

Result 3:
- Working fine.

For the FreeBSD kernel configuration, I have a few settings which might
influence the crash in result 2:
options         DEVICE_POLLING          # helped with some old hardware
options         NO_ADAPTIVE_MUTEXES     # helps with running in VirtualBox
options         NO_ADAPTIVE_RWLOCKS     # ...
options         NO_ADAPTIVE_SX          # ...

Could any of these be the reason for the issue I see? Anything else I should
look out for?

-- Martin

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