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

Re: [Xen-devel] Xen 4.4 trunk: device [xxxx:yyyy] has invalid IRQ; check vendor BIOS



On 2013-11-25 20:16, Mark Hurenkamp wrote:

Looking at the output of dmesg, there is a clear hint of what might be
wrong; it lists several (>10) of the following messages:
[    3.957006] pcieport 0000:00:01.0: device [8086:0d01] has invalid
IRQ; check vendor BIOS
[    3.957018] pcieport 0000:00:01.0: can't find IRQ for PCI INT A;
please try using pci=biosirq

Additionally, i found some more strangeness in the dmesg output:
[ 3.725793] pci 0000:06:00.0: BAR 15: can't assign mem pref (size 0x200000) [ 3.725796] pci 0000:06:04.0: BAR 14: can't assign mem (size 0x200000)
Also repeating several times for multiple devices.
Could this be related to the problems i see?

This while booting the same kernel (3.13-rc1) without xen works fine.

I'm not sure where this problem originates, the suggestion to use
'pci=biosirq' (which i also tried adding to the kernel commandline to
no avail) seems to indicate that the Bios (or in this case EFI, or
Xen?) is not setting up the proper interrupts for these devices. Note
that I'm not using boot-camp, I'm booting xen.efi directly from
refind.

Is there anything i can do to remedy this? I've built Xen from
(recent) trunk, and would be happy to help debug/analyse this problem,
just don't know quite where to start...

I can provide dmesg; xl dmesg, or lspci output if so desired, just let
me know what is of interest.


Warm regards,
Mark.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.