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

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 16/05/14 11:08, Jan Beulich wrote:
>>>> On 16.05.14 at 10:58, <ijc@xxxxxxxxxxxxxx> wrote:
>> 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!
> The last one certainly isn't, and the first two shouldn't (albeit the
> non-Xen kernel is running in x2APIC mode). That difference is likely
> because the Xen and non-Xen boots are with differing BIOS
> configurations, or on different machines: The non-Xen boot shows
> a DMAR ACPI table, while the Xen one doesn't. Or wait, no, the
> hypervisor and kernel-under-Xen logs differ in that respect too. We
> clearly need a consistent set of logs.
>
> The one clearly odd thing in the hypervisor logs are these two lines
>
> (XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa
> (XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa
>
> Can at least the left side address please be associated back with a
> symbol (with the help of xen-syms perhaps)?

As this is a debug message anyway, it would be sensible for the extable
handler to print %pS of the left hand address.  It would avoid needing
to refer back to xen-syms in cases like this.

~Andrew

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