From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: dom0 USB failing with "ehci-pci: probe of
 0000:00:1d.0 faile
Date: Wed, 21 May 2014 09:32:02 +0100
Message-ID: <537C80A20200007800014650@mail.emea.novell.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> < >
	<1400254316.30069.5.camel@kazak.uk.xensource.com> < >
	<537651060200007800013382@mail.emea.novell.com> < >
	<fc.011fc823e66acc853b9aca005d0d88ff.e66acc88@estone.ca>
	<1400490091.32311.16.camel@kazak.uk.xensource.com>
	<fc.011fc823e66acdde3b9aca005d0d88ff.e66acde1@estone.ca>
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: <fc.011fc823e66acdde3b9aca005d0d88ff.e66acde1@estone.ca>
Content-Disposition: inline
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: Mike Egglestone <mike@estone.ca>
Cc: 748052@bugs.debian.org, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

>>> On 20.05.14 at 18:25, <mike@estone.ca> wrote:
> I've added iommu=debug to the XEN CMD Line under grub.
> Attached is the xl dmesg log and system dmesg.

Okay, this at least clarifies there is a (relatively big) RMRR. There is
a change to the handling of these among the ones that'll become
4.3.3 - mind giving
http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=6c63041428cc348bcb2887afabd606bc4bd5523f
a try on top of your 4.3.2 (or trying the tip of the stable-4.3 branch)?

> What else did I miss that could be useful info?

At least the resolution of these addresses

(XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa
(XEN) traps.c:3061: GPF (0000): ffff82c4c0186a91 -> ffff82c4c0218daa

into (symbol,offset) pairs, so we can at least make a first guess at
whether these are in any way related to your problem.

Jan