From mboxrd@z Thu Jan 1 00:00:00 1970 From: "M. Ivanov" Subject: Re: About Xen bridged pci devices and suspend/resume for the X10SAE motherboard (SuperMicro) Date: Fri, 14 Aug 2015 17:08:32 +0300 Message-ID: <1439561312.7011.26.camel@gmail.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> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0493774188330053738==" Return-path: In-Reply-To: <20150813194906.GA25713@l.oracle.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: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0493774188330053738== Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-yljG2dCQxwsqQIMnI+2v" --=-yljG2dCQxwsqQIMnI+2v Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2015-08-13 at 15:49 -0400, Konrad Rzeszutek Wilk wrote: > On Mon, Aug 10, 2015 at 09:21:35PM +0300, M. Ivanov wrote: > > On Mon, 2015-08-10 at 10:47 -0400, Konrad Rzeszutek Wilk wrote: > > > On Mon, Aug 10, 2015 at 05:14:28PM +0300, M. Ivanov wrote: > > > > On Mon, 2015-08-10 at 09:58 -0400, Konrad Rzeszutek Wilk wrote: > > > > > On Mon, Aug 10, 2015 at 02:11:38AM +0300, M. Ivanov wrote: > > > > > > Hello, > > > > > >=20 > > > > > > excuse me for bothering you, but I've read an old thread on a m= ailing > > > > > > list about X10SAE compatibility.=20 > > > > > > http://lists.xen.org/archives/html/xen-devel/2014-02/msg02111.h= tml > > > > >=20 > > > > > CC-ing Xen devel. > > > > > >=20 > > > > > > Currently I own this board and am trying to use it with Xen and= be able > > > > > > to suspend and resume. > > > > > >=20 > > > > > > But I am getting errors from the USB 3 Renesas controller about= parity > > > > > > in my bios event log, and my system hangs on resume, > > > > > > so I was wondering if that is connected to the bridge(tundra) y= ou've > > > > > > mentioned. > > > > >=20 > > > > > Did you update the BIOS to the latest version? > > > > Will updating to version 3 solve my issue? > > > > Can you do a suspend/resume on your X10SAE? > > >=20 > > > It did work at some point. I will find out when I am at home later to= day. > > >=20 > > Looking forward to your reply and am really thankful for your time, > > so far I've tried changing many of the settings in the bios, > > fiddling with Xen's kernel params, > > blacklisting the xhci driver, doing a xl detach. > >=20 > > The only thing I haven't done yet is updating the bios, > > but Supermicro's support couldn't give me a changelog: > >=20 > > "The primary objective for ver3.0 BIOS release is to support Intel > > Broadwell CPUs" > > "We do not know if BIOS update will fix the issue you are seeing as we > > never tested it with Xen." >=20 > I did test it remotely and it did something very odd. It suspended and th= en > immediately resumed with tons of VT-d errors!? >=20 > I will try again but be actually right by it. Thanks for your effort, Can you suggest a way for me to log what is happening? Since my machine just hangs up and I don't get a picture on the screen. Or when I do(sometimes) - it's just a cursor,(on a black screen with nothing else,no errors shown) and the machine doesn't react to any key combinations. On a side note: I did try updating the bios, but got some really strange result. The first time I got checksums about everything OK, (erase,flash,verify), but then it said - FDT is locked! And I am at least 90% sure I've enabled reflash in=20 the BIOS setup prior to flashing. So I've restarted but didn't clear the CMOS(through the jumper on the board). And it said Bios v 3.0 in the setup, then I also did the Reset to optmized defaults. Tried suspending and couldn't resume like always. But perhaps currently my BIOS is in a broken/corrupted state. After that I've tried reflashing the bios again. But this time -=20 after the messages about Erasing,Flashing,Verifying: it just froze. I didn't get any message about FDT, restarting or whatsoever. So I rebooted and it seems to work like before, says version 3.0 in the BIOS setup. I wonder if I should try clearing the CMOS and flashing again. > > > > > >=20 > > > > > > I will be very glad if you could share any information regardin= g this > > > > > > matter.=20 > > > > > >=20 > > > > > > Best regards, > > > > > > M. Ivanov > > > > >=20 > > > > >=20 > > > >=20 > > >=20 > > >=20 > >=20 >=20 >=20 --=-yljG2dCQxwsqQIMnI+2v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCgAGBQJVzfZgAAoJEExnsX0sda0odKQH/i5DZk+bjvGL8rBlsLqxBvDY pOYPQk5mMvKx0wlSQTyaq7Kg/bavBnx6ZdqPKHO3sakEEj77sQmTnziLoNm/nTwk 6ux5BaNErdrO998VdHfyWTHa+f2HYXo00Yeg+mkDpdDEUIrKlcR4ZkZOaJEsjKt5 DzRODmsmhaDOHfMuEWIa25EN/9s5mR7do0fXQlA96kfmpTLUYJhnkT0G2w6wX4To z0/myxrRrWDsfz/I9v9T/AX9PrC8yS64vM+5OuKKa9pVmNsK4NueC3swFuY9QAzm mSXZIvHmfUJWkjlSkmNqkCan0pVYgGKdhmdnXM0kqU9prPxHHI8SgySdYb5MeMI= =5zv5 -----END PGP SIGNATURE----- --=-yljG2dCQxwsqQIMnI+2v-- --===============0493774188330053738== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0493774188330053738==--