Re: kern/55667 (regression: XEN3_DOM0 fails to boot on)

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR kern/55667; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: Frank Kardel <kardel%netbsd.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, jdolecek%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/55667 (regression: XEN3_DOM0 fails to boot on)
Date: Tue, 24 May 2022 18:12:54 +0200

 On Mon, May 23, 2022 at 03:57:38PM +0200, Frank Kardel wrote:
 > In 9.99.55 ixg(4) works with ioapic (I am running that now) from
 > /var/run/dmesg.boot:
 > 
 > ixg0 at pci16 dev 0 function 0: Intel(R) PRO/10GbE PCI-Express Network
 > Driver, Version - 4.0.1-k
 > ixg0: clearing prefetchable bit
 > ixg0: device X550
 > ixg0: NVM Image Version 1.93, PHY FW Revision 2.0b ID 0xb, NVM Map version
 > 1.93, OEM NVM Image version 0.04, ETrackID 80000aee
 > ixg0: interrupting at ioapic3 pin 31
 > ixg0: Ethernet address ac:1f:6b:f5:bc:cc
 > ixg0: PHY OUI 0x00aa00, model 0x0022, rev. 0
 > ixg0: PCI Express Bus: Speed 8.0GT/s Width x4
 > ixg0: feature cap 0x17a0<TEMP_SENSOR,LEGACY_TX,FDIR,MSI,MSIX,LEGACY_IRQ>
 > ixg0: feature ena 0x1020<TEMP_SENSOR,LEGACY_IRQ>
 > ixg1 at pci16 dev 0 function 1: Intel(R) PRO/10GbE PCI-Express Network
 > Driver, Version - 4.0.1-k
 > ixg1: clearing prefetchable bit
 > ixg1: device X550
 > ixg1: NVM Image Version 1.93, PHY FW Revision 2.0b ID 0xb, NVM Map version
 > 1.93, OEM NVM Image version 0.04, ETrackID 80000aee
 > ixg1: interrupting at ioapic3 pin 30
 > ixg1: Ethernet address ac:1f:6b:f5:bc:cd
 > ixg1: PHY OUI 0x00aa00, model 0x0022, rev. 0
 > ixg1: PCI Express Bus: Speed 8.0GT/s Width x4
 > ixg1: feature cap 0x17a0<TEMP_SENSOR,LEGACY_TX,FDIR,MSI,MSIX,LEGACY_IRQ>
 > ixg1: feature ena 0x1020<TEMP_SENSOR,LEGACY_IRQ>
 > 
 > Looks like something broke there. It is certainly not a hardware limitation
 > but rather a
 > driver/interrut subsystem bug.
 
 Yes; I suspect a driver bug as other devices works in legacy mode.
 But I think it's outside the scope of this PR.
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --