xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ross Philipson <ross.philipson@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Mike Egglestone <mike@estone.ca>,
	Ian Campbell <ijc@hellion.org.uk>
Cc: "748052@bugs.debian.org" <748052@bugs.debian.org>,
	xen-devel <xen-devel@lists.xen.org>
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	[thread overview]
Message-ID: <5376252D.2030401@citrix.com> (raw)
In-Reply-To: <5375FFAE0200007800012F90@mail.emea.novell.com>

On 05/16/2014 06:08 AM, 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.

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

  parent reply	other threads:[~2014-05-16 14:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140513155528.2659.84403.reportbug@xen-3>
     [not found] ` <1400084844.26934.6.camel@kazak.uk.xensource.com>
     [not found]   ` <fc.011fc823e66acb533b9aca005d0d88ff.e66acb56@estone.ca>
     [not found]     ` <1400148065.4386.11.camel@kazak.uk.xensource.com>
     [not found]       ` <1400149218.4386.24.camel@kazak.uk.xensource.com>
     [not found]         ` <fc.011fc823e66acbd03b9aca005d0d88ff.e66acbd5@estone.ca>
2014-05-16  8:58           ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Ian Campbell
2014-05-16 10:08             ` Jan Beulich
2014-05-16 10:14               ` Andrew Cooper
2014-05-16 14:48               ` Ross Philipson [this message]
2014-05-16 15:18                 ` Jan Beulich
2014-05-16 15:31               ` Ian Campbell
2014-05-16 15:51                 ` Jan Beulich
2014-05-16 16:04                   ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile Mike Egglestone
     [not found]                   ` <fc.011fc823e66acc6f3b9aca005d0d88ff.e66acc76@estone.ca>
2014-05-19 10:56                     ` Jan Beulich
2014-05-16 15:55                 ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Jan Beulich
2014-05-16 17:05                   ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile Mike Egglestone
     [not found]                   ` <fc.011fc823e66acc853b9aca005d0d88ff.e66acc88@estone.ca>
2014-05-19  9:01                     ` Ian Campbell
     [not found]                     ` <1400490091.32311.16.camel@kazak.uk.xensource.com>
2014-05-20 16:25                       ` Mike Egglestone
     [not found]                       ` <fc.011fc823e66acdde3b9aca005d0d88ff.e66acde1@estone.ca>
2014-05-21  8:32                         ` Jan Beulich
2014-05-22 17:19                           ` Mike Egglestone
     [not found]                           ` <fc.011fc823e66aced13b9aca005d0d88ff.e66aced4@estone.ca>
2014-05-23  7:52                             ` Jan Beulich
     [not found]                             ` <537F1A700200007800015391@mail.emea.novell.com>
2014-05-23  9:21                               ` Ian Campbell
2014-05-23  9:35                                 ` Jan Beulich
2014-05-23 10:08                                   ` Ian Campbell
2014-05-23 10:14                                     ` Jan Beulich
2014-05-23 18:53                                 ` Mike Egglestone
2014-05-23 20:00                                 ` Mike Egglestone
2014-05-21 17:44                 ` Mike Egglestone
     [not found]                 ` <fc.011fc823e66ace343b9aca005d0d88ff.e66ace35@estone.ca>
2014-05-21 18:42                   ` Ian Campbell
     [not found] <CAG8B0OzB1tuVRyOi0PHTXmW4D_HmUzsaRUpR3uacuTiSts_yhQ@mail.gmail.com>
     [not found] ` <CAG8B0OzdUfvqT+o1yCDrRJ2pd=0i7rGfFVth+hHc+0drNiNedg@mail.gmail.com>
     [not found]   ` <56C59FAF02000078000D38E8@prv-mh.provo.novell.com>
2016-02-19  8:30     ` dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110" Robin Lee
2016-02-19 11:47       ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5376252D.2030401@citrix.com \
    --to=ross.philipson@citrix.com \
    --cc=748052@bugs.debian.org \
    --cc=JBeulich@suse.com \
    --cc=ijc@hellion.org.uk \
    --cc=mike@estone.ca \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).