aboutsummaryrefslogtreecommitdiff
path: root/sys/modules/syscons/dragon/(public-mirror)
diff options
context:
space:
mode:
authorKevin Bowling <kbowling@FreeBSD.org>2026-09-14 23:51:01 +0000
committerKevin Bowling <kbowling@FreeBSD.org>2026-09-15 02:07:11 +0000
commitf589d1fc36cebcc298eb708bf5eae57bd1d491d7 (patch)
tree9941f6db5d5bd174a69c8ec863f0d42454cc927e /sys/modules/syscons/dragon/(public-mirror)
parent9ea7beb173b8b5c77663ee0f86b32cc76f20357f (diff)
ixv: Recover E610 Hyper-V carrier without the PCI link queryHEADmain
Current Windows PF drivers do not emulate the E610 link-status query at PCI configuration offset 0x209. The installed Intel ixw 1.8.54.0 driver returns zero even with the physical port connected, leaving the VF at no carrier after an otherwise successful hn handoff. When the query returns zero, use VFLINKS for carrier only. Its speed field is not the negotiated E610 line rate: the tested 1 Gb/s port reports the default 10 Gb/s encoding. Publish an unknown speed instead, including in the verbose link-up diagnostic, and document this fallback. Keep nonzero PCI results authoritative and reject all-ones reads. Other Hyper-V families and the native E610 mailbox path are unchanged. A zero result cannot distinguish an unsupported query from a down link; in either case this fallback relies on the legacy carrier indication. The connected and disconnected ports reported VFLINKS.UP set and clear, respectively, while both returned zero from the PCI query. MFC after: 2 weeks Sponsored by: BBOX.io
Diffstat (limited to 'sys/modules/syscons/dragon/(public-mirror)')
0 files changed, 0 insertions, 0 deletions