From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Xen 4.2.0 Release Plan / TODO Date: Thu, 6 Sep 2012 17:45:23 +0300 Message-ID: <20120906144523.GX8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <5048B4DF0200007800099554@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ben Guthro Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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 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 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 wrote: > >>>>>> On 03.09.12 at 11:42, Ian Campbell 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