From: Ben Guthro <ben.guthro@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ben Guthro <ben@guthro.net>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: S3 is broken again in xen-unstable
Date: Tue, 7 May 2013 05:18:45 -0400 [thread overview]
Message-ID: <-2313368536701448454@unknownmsgid> (raw)
In-Reply-To: <26100746.41126.1367916036066.JavaMail.mobile-sync@vcin11>
On May 7, 2013, at 4:40 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 07.05.13 at 10:34, Pasi Kärkkäinen<pasik@iki.fi> wrote:
>> On Fri, Apr 26, 2013 at 07:41:07PM -0400, Ben Guthro wrote:
>>> Then, also the ns16550 change.
>>> While strictly not necessary to fix S3 in the normal path, it does fix
>>> a bug that can lead to S3 not working if you
>>> a. have one of these SuperIO controllers on the LPC bus.
>>> b. have serial enabled.
>> http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;hn96c186d23873597896051b0
>> 43cfeb119c4a7d5
>>
>> Jan: I think this ns16550 patch should be backported to 4.2 branch aswell..
>
> Yeah, as being secondary I left this off until we know that this
> really is the only thing known to break resume (i.e. I saw no point
> in backporting this when in the end S3 still wouldn't work anyway).
>
> Ben - am I right in understanding your earlier summary in this
> thread to mean that the 4.2 branch, according to your testing,
> is now is such a state?
>
Yea, S3 works on the 4.2.3 branch without this patch. This fixes a
specific corner case on some machines with the SuperIO hardware.
next prev parent reply other threads:[~2013-05-07 9:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 12:00 S3 is broken again in xen-unstable Ben Guthro
2013-04-25 17:02 ` Ben Guthro
2013-04-26 8:10 ` Ian Campbell
2013-04-26 12:19 ` Ben Guthro
2013-04-26 13:17 ` Ian Campbell
2013-04-26 14:10 ` Ben Guthro
2013-04-26 14:32 ` Ian Campbell
2013-05-21 18:29 ` Ben Guthro
2013-05-21 18:52 ` Pasi Kärkkäinen
2013-05-01 11:01 ` Ian Jackson
2013-05-01 12:03 ` Ben Guthro
2013-04-29 11:03 ` George Dunlap
[not found] ` <CAOvdn6VXNDKjxyJmMQNdTSaXu-f3_FYgwg_2LunG6fYpMw+ywQ@mail.gmail.com>
2013-04-30 9:00 ` George Dunlap
2013-04-26 20:47 ` Pasi Kärkkäinen
2013-04-26 23:41 ` Ben Guthro
2013-05-07 8:34 ` Pasi Kärkkäinen
2013-05-07 8:40 ` Jan Beulich
[not found] ` <26100746.41126.1367916036066.JavaMail.mobile-sync@vcin11>
2013-05-07 9:18 ` Ben Guthro [this message]
2013-04-29 8:45 ` Jan Beulich
2013-04-29 10:24 ` Ben Guthro
2013-04-29 10:55 ` George Dunlap
2013-04-29 11:07 ` 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=-2313368536701448454@unknownmsgid \
--to=ben.guthro@gmail.com \
--cc=JBeulich@suse.com \
--cc=ben@guthro.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.