Re: [Xen-devel] Xen 4.2.0 Release Plan / TODO

[Ben Guthro <ben@xxxxxxxxxx>]

On Thu, Sep 6, 2012 at 10:45 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> 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.

This particular machine has neither.
I'll look around for an alternate.



Ben

>
> -- Pasi
>
>> On Thu, Sep 6, 2012 at 9:40 AM, Ben Guthro <ben@xxxxxxxxxx> 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@xxxxxxxxxx> 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@xxxxxxxx> wrote:
>> >>>>>> On 03.09.12 at 11:42, Ian Campbell <Ian.Campbell@xxxxxxxxxx> 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@xxxxxxxxxxxxx
>> >>> http://lists.xen.org/xen-devel
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel

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