From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: About Xen bridged pci devices and suspend/resume for the X10SAE motherboard (SuperMicro) Date: Wed, 4 Nov 2015 16:06:06 -0500 Message-ID: <20151104210606.GB16253@char.us.oracle.com> References: <1439161898.27696.190.camel@gmail.com> <20150810135836.GB11826@l.oracle.com> <1439216068.425.11.camel@gmail.com> <20150810144735.GI11826@l.oracle.com> <1439230895.425.22.camel@gmail.com> <20150813194906.GA25713@l.oracle.com> <1439561312.7011.26.camel@gmail.com> <20150814161556.GA5802@l.oracle.com> <1446598151.4224.33.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1446598151.4224.33.camel@gmail.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: "M. Ivanov" Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Nov 04, 2015 at 02:49:11AM +0200, M. Ivanov wrote: > Hello, > > I've experimented with my X10SAE and I think the problem with being > unable to resume after suspending to RAM has something to do with the > PCI Bridge violating the spec by trying to DMA from another address, > since I got a DMAR error about DMA access on address 05:00.0(but in the > bios event log it says Bus06), also the Tundra PCI Bridge is on address > 04:00.0. (so like your case with address 7 and 8, but mine's 4 and 5), > btw adding a PCI-E vga seems to change the addresses. > > When I disable IOMMU+Xen it works fine, so I mostly sure it's that. > Though I've tried running just Linux with the iommu param on and I > didn't get an error when sleeping/resuming. But I haven't tried doing a > pass-through with it > > I've read in a previous thread about a patch of yours for the X10SAE > problem. Which version of Xen can I use it on?(I am currently tinkering > with 4.4.3-RELEASE). Oh my I can't remember. > > Also I take it - I need to use hack.c to tell xen to create the fake > device,(in my case 05:00.0) and to link it with 04:00.0? But how do I > get that file to compile? Since I don't have a makefile/etc. for it. So.. that motherboard is a pain to work with. I found after numerous emails to their technical support that the PCI chipset is not capable of dealing with VT-d. That is PCI passhtrough of any PCI devices - nada. > > Also, can't I just disable the PCI Tundra bridge somehow? And what about > phantom pci and the pciback-hide? Can they help? That would be nice. > > I've read about problems regarding the Asmedia controller, so I've > disabled it from the bios, but that didn't help at all. Lets take one problem at a time. The current issue you are seeing is suspend/resume right? That is you just booted Xen + Linux and ran 'pm-suspend'. And the motherboard did not resume from there? But it works OK with Linux? Is AMT enabled on your setup? > > > As for my Xen crash log > > DMAR:[DMA Write] Request device [05:00.0] fault addr Can't remember it > DMAR:[fault reason 02] Present bit in context entry is clear > > Here is my tree: > > 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM > Controller (rev 06) > 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor PCI Express x16 Controller (rev 06) > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 > Processor Integrated Graphics Controller (rev 06) > 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor HD Audio Controller (rev 06) > 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USB xHCI (rev 05) > 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series > Chipset Family MEI Controller #1 (rev 04) > 00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series > Chipset Family KT Controller (rev 04) > 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection > I217-LM (rev 05) > 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #2 (rev 05) > 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset > High Definition Audio Controller (rev 05) > 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #1 (rev d5) > 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #4 (rev d5) > 00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #6 (rev d5) > 00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #7 (rev d5) > 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #1 (rev 05) > 00:1f.0 ISA bridge: Intel Corporation C226 Series Chipset Family Server > Advanced SKU LPC Controller (rev 05) > 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset > Family 6-port SATA Controller 1 [AHCI mode] (rev 05) > 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family > SMBus Controller (rev 05) > 00:1f.6 Signal processing controller: Intel Corporation 8 Series Chipset > Family Thermal Management Controller (rev 05) > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Cayman PRO [Radeon HD 6950] > 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] > 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network > Connection (rev 03) > 04:00.0 PCI bridge: Tundra Semiconductor Corp. Device 8113 (rev 01) > 05:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A > IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] > 06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host > Controller (rev 02) > >