[Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110"

[Ian Campbell <ijc@xxxxxxxxxxxxxx>]

(copying xen-devel, full logs are at bugs.debian.org/748052, this is
Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian
Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was
with though, Wheezy's 3.2 or Jessie's 3.13)

On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote:
> Here are some results with (now) the latest BIOS version 41. (was
> version 35)
> This is a fresh new install of Debian "Testing" non production server.
> Just wanted to run some test domU's.
> Changing USB ports, no effect. I even tried a different USB keyboard.
>  :)
> No PS2 ports on Motherboard.

> Booting into NONXEN:

> root@xen-3:~# dmesg 
[...]
> Booting into XEN:
> (Did I do this correctly?)

You did in the follow up.

> root@xen-3:~# xl dmesg
[...]
> root@xen-3:~# dmesg
[...]

I've attached these as x (xen dom0 Linux dmesg) and nx (non-xen Linux
dmesg) for easy diffing (I also stripped the kernel timestamps off to
reduce the noise). I also attached xdmesg (Xen's own dmesg) from your
next mail.

The interesting difference seems to be that the dom0 dmesg under Xen
contains:
        ehci-pci 0000:00:1d.0: can't setup: -110
        ehci-pci 0000:00:1d.0: USB bus 2 deregistered
        ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -110
        ehci-pci: probe of 0000:00:1d.0 failed with error -110
        
and since it doesn't see the controller it doesn't see the devices on
that controller. There is another controller but given that it contains
"American Megatrends, Inc. Virtual Keyboard and Mouse" I expect it is an
imaginary firmware one and hence not much use.

There is also a smattering of
xen: registering gsi 20 triggering 0 polarity 1
Already setup the GSI :20
(four times for GSI16, once for 20 and twice for 22). The contents
of /proc/interrupts under native might tell you what those other
interrupts are...

So it seems like dom0 is unable to (correctly) bind to some hardware
interrupts. I wonder if these messages from Xen's dmesg are relevant.
(XEN) Not enabling x2APIC: depends on iommu_supports_eim.
(XEN) I/O virtualisation disabled
(XEN) Enabled directed EOI with ioapic_ack_old on!

Ian.

Attachment: x
Description: Text document

Attachment: nx
Description: Text document

Attachment: xdmesg
Description: Text document

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