From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ross Philipson Subject: Re: dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Date: Fri, 16 May 2014 10:48:13 -0400 Message-ID: <5376252D.2030401@citrix.com> References: <20140513155528.2659.84403.reportbug@xen-3> < > <1400084844.26934.6.camel@kazak.uk.xensource.com> < > < > <1400148065.4386.11.camel@kazak.uk.xensource.com> <1400149218.4386.24.camel@kazak.uk.xensource.com> <1400230692.5390.18.camel@kazak.uk.xensource.com> <5375FFAE0200007800012F90@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5375FFAE0200007800012F90@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Mike Egglestone , Ian Campbell Cc: "748052@bugs.debian.org" <748052@bugs.debian.org>, xen-devel List-Id: xen-devel@lists.xenproject.org On 05/16/2014 06:08 AM, Jan Beulich wrote: >>>> On 16.05.14 at 10:58, 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. Doesn't Xen hide the DMAR from dom0 on purpose? I think it renames it to XMAR IIRC. > 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)? > > And finally, looking at the IRQ usage, this > > [ 2.087722] xen: registering gsi 22 triggering 0 polarity 1 > [ 2.087731] xen: --> pirq=22 -> irq=22 (gsi=22) > [ 2.100161] xen: registering gsi 20 triggering 0 polarity 1 > [ 2.100166] xen: --> pirq=20 -> irq=20 (gsi=20) > > happens rather early - it's not clear to me in which context that is. > And there's no problem with GSI 22 used by the other EHCI HC, so > a fundamental question is what other device(s) is/are using GSI 20 > (not visible from the non-Xen kernel log). > > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2014.0.4577 / Virus Database: 3950/7484 - Release Date: 05/12/14 > -- Ross Philipson