From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: dom0 USB failing with "ehci-pci: probe of
 0000:00:1d.0 failed with error -110"
Date: Fri, 16 May 2014 11:14:58 +0100
Message-ID: <5375E522.7090008@citrix.com>
References: <20140513155528.2659.84403.reportbug@xen-3> < >
	<1400084844.26934.6.camel@kazak.uk.xensource.com> < >
	<fc.011fc823e66acb533b9aca005d0d88ff.e66acb56@estone.ca> < >
	<1400148065.4386.11.camel@kazak.uk.xensource.com>
	<1400149218.4386.24.camel@kazak.uk.xensource.com>
	<fc.011fc823e66acbd03b9aca005d0d88ff.e66acbd5@estone.ca>
	<1400230692.5390.18.camel@kazak.uk.xensource.com>
	<5375FFAE0200007800012F90@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5375FFAE0200007800012F90@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: 748052@bugs.debian.org, xen-devel <xen-devel@lists.xen.org>, Mike Egglestone <mike@estone.ca>, Ian Campbell <ijc@hellion.org.uk>
List-Id: xen-devel@lists.xenproject.org

On 16/05/14 11:08, Jan Beulich wrote:
>>>> On 16.05.14 at 10:58, <ijc@hellion.org.uk> 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