From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Ben Guthro <ben@guthro.net>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2.0 Release Plan / TODO
Date: Thu, 6 Sep 2012 17:45:23 +0300 [thread overview]
Message-ID: <20120906144523.GX8912@reaktio.net> (raw)
In-Reply-To: <CAOvdn6WU=haz48S=ok3M8mAovuag4wQtaj2dhGmJvVfrqK3rJg@mail.gmail.com>
On Thu, Sep 06, 2012 at 10:35:44AM -0400, Ben Guthro wrote:
> I may have claimed success on this second one too soon. Subsequent
> tests, and expansion to other systems shows S3 still to be a problem
> on these laptops.
>
> Being a laptop, without a serial port, of course makes this more
> difficult to debug.
> I'll continue to look into it.
>
You probably know this already but here goes anyway..
you could use an expresscard serial card, or if the laptop has Intel vPro (AMT),
then it has a Serial Over LAN (SOL) port, which can be used for Xen debugging/logging.
-- Pasi
> On Thu, Sep 6, 2012 at 9:40 AM, Ben Guthro <ben@guthro.net> wrote:
> > Good news on this front, as well - it seems to fix the "blinky power
> > button" failure, as well.
> >
> >
> > On Thu, Sep 6, 2012 at 8:55 AM, Ben Guthro <ben@guthro.net> wrote:
> >> FWIW, I ran this through 100 suspend / resume cycles successfully, on
> >> the machine where I could only do one before.
> >>
> >> I'm still waiting for a laptop to free up that exhibited the other S3
> >> failure where it went to sleep, but just pulsed the power LED when
> >> asked to wake up.
> >> I'm cautiously hopeful this fixes that problem, as well.
> >>
> >> Ben
> >>
> >> On Thu, Sep 6, 2012 at 8:36 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>>>> On 03.09.12 at 11:42, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >>>> hypervisor, nice to have:
> >>>>
> >>>> * S3 regression(s?) reported by Ben Guthro (Ben & Jan Beulich)
> >>>
> >>> So it looks like we got this nailed down (actually requiring two
> >>> fixes). Would it be intended to still get these in before the
> >>> release, or leave them for 4.3/4.2.1?
> >>>
> >>> Jan
> >>>
> >>> NB: I also found an unrelated issue earlier today where a
> >>> hypercall would return success when it actually failed, but I
> >>> won't even bother sending that out if the fixes needed here
> >>> aren't to be considered, as that's clearly minor compared to
> >>> the regression here.
> >>>
> >>>
> >>> _______________________________________________
> >>> Xen-devel mailing list
> >>> Xen-devel@lists.xen.org
> >>> http://lists.xen.org/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-09-06 14:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 9:42 Xen 4.2.0 Release Plan / TODO Ian Campbell
2012-09-03 10:45 ` Jan Beulich
2012-09-04 7:06 ` [Xen-users] " Mark van Dijk
2012-09-04 7:31 ` Ian Campbell
2012-09-04 8:37 ` Mark van Dijk
2012-09-04 8:51 ` Ian Campbell
2012-09-04 7:34 ` Casey DeLorme
2012-09-05 2:51 ` Pasi Kärkkäinen
2012-09-05 8:34 ` Ian Campbell
2012-09-05 8:39 ` Pasi Kärkkäinen
2012-09-05 9:24 ` Ian Campbell
2012-09-05 8:51 ` Sander Eikelenboom
2012-09-05 9:15 ` Ian Campbell
2012-09-05 12:29 ` [Xen-users] " Mark van Dijk
2012-09-05 15:29 ` Pasi Kärkkäinen
2012-09-05 17:53 ` [Xen-users] " Mark van Dijk
2012-09-05 20:31 ` Matt Wilson
2012-09-05 17:57 ` Ian Campbell
2012-09-06 12:36 ` Jan Beulich
2012-09-06 12:55 ` Ben Guthro
2012-09-06 13:40 ` Ben Guthro
2012-09-06 14:35 ` Ben Guthro
2012-09-06 14:45 ` Pasi Kärkkäinen [this message]
2012-09-06 14:47 ` Ben Guthro
2012-09-06 14:52 ` Pasi Kärkkäinen
2012-09-06 15:03 ` 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=20120906144523.GX8912@reaktio.net \
--to=pasik@iki.fi \
--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.