NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



On Wed, May 25, 2022 at 10:30:02AM +0000, Frank Kardel wrote:
> The following reply was made to PR kern/55667; it has been noted by GNATS.
> 
> From: Frank Kardel <kardel%netbsd.org@localhost>
> To: gnats-bugs%netbsd.org@localhost, jdolecek%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
>  netbsd-bugs%netbsd.org@localhost
> Cc: 
> Subject: Re: kern/55667 (regression: XEN3_DOM0 fails to boot on)
> Date: Wed, 25 May 2022 12:29:10 +0200
> 
>  I tried the updated version, but on this machine MSI-X cannot be registered.
>  
>  [     1.571349] ixg0 at pci16 dev 0 function 0: Intel(R) PRO/10GbE 
>  PCI-Express Network Driver, Version - 4.0.1-k
>  [     1.571468] ixg0: clearing prefetchable bit
>  [     1.571814] ixg0: device X550
>  [     1.843714] 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
>  [     1.867853] ixg0: PBA number 020C08-0F8
>  [>>> 1.867964] xen_map_msix_pirq bus 69 devfn 0x0 (0 0) count 5 map 0 fail
>  [>>> 1.867984] ixg0: autoconfiguration error: failed to allocate MSI-X 
>  interrupt
>  [>>> 1.868988] xen_map_msi_pirq bus 69 devfn 0x0 (0 0) entry_nr 0 fail
>  [     1.869006] xen_pic_to_gsi ioapic pin 31 gsi 119 allocated 119

Both msi-x and msi failing, that's strange.
Can you boot xen-debug.gz with apic_verbosity=debug acpi=verbose
and post the result here (although I'm not sure it will tell much about
msi/msi-x).

Also a dmesg from a recent GENERIC could be interesting.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index