xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "M. Ivanov" <mihail.ivanov93@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: About Xen bridged pci devices and suspend/resume for the X10SAE motherboard
Date: Mon, 10 Aug 2015 21:21:35 +0300	[thread overview]
Message-ID: <1439230895.425.22.camel@gmail.com> (raw)
In-Reply-To: <20150810144735.GI11826@l.oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 1846 bytes --]

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,
> > > > 
> > > > excuse me for bothering you, but I've read an old thread on a mailing
> > > > list about X10SAE compatibility. 
> > > > http://lists.xen.org/archives/html/xen-devel/2014-02/msg02111.html
> > > 
> > > CC-ing Xen devel.
> > > > 
> > > > Currently I own this board and am trying to use it with Xen and be able
> > > > to suspend and resume.
> > > > 
> > > > 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) you've
> > > > mentioned.
> > > 
> > > 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?
> 
> It did work at some point. I will find out when I am at home later today.
> 
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.

The only thing I haven't done yet is updating the bios,
but Supermicro's support couldn't give me a changelog:

"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."
> > > > 
> > > > I will be very glad if you could share any information regarding this
> > > > matter. 
> > > > 
> > > > Best regards,
> > > > M. Ivanov
> > > 
> > > 
> > 
> 
> 


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-08-10 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1439161898.27696.190.camel@gmail.com>
2015-08-10 13:58 ` About Xen bridged pci devices and suspend/resume for the X10SAE motherboard Konrad Rzeszutek Wilk
2015-08-10 14:14   ` M. Ivanov
2015-08-10 14:47     ` Konrad Rzeszutek Wilk
2015-08-10 18:21       ` M. Ivanov [this message]
2015-08-13 19:49         ` About Xen bridged pci devices and suspend/resume for the X10SAE motherboard (SuperMicro) Konrad Rzeszutek Wilk
2015-08-14 14:08           ` M. Ivanov
2015-08-14 16:15             ` Konrad Rzeszutek Wilk
2015-08-14 22:08               ` M. Ivanov
2015-11-04  0:49               ` M. Ivanov
2015-11-04 21:06                 ` Konrad Rzeszutek Wilk
2015-11-04 22:28                   ` M. Ivanov

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=1439230895.425.22.camel@gmail.com \
    --to=mihail.ivanov93@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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).