Re: [Xen-devel] Xen4.2 S3 regression?

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 15.08.12 at 15:11, Ben Guthro <ben@xxxxxxxxxx> wrote:
> On Wed, Aug 15, 2012 at 8:58 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>> On 15.08.12 at 14:32, Ben Guthro <ben@xxxxxxxxxx> wrote:
>>> This was encouraging, so I tried the same change against the tree
>>> tip...unfortunately that didn't go as well.
>>>
>>> tip + evtchn_move_pirqs() removal:
>>> did not resume from the first suspend.
>>
>> Any logs of this (i.e. indications of what's going wrong - still
>> the same AHCI not working, but else apparently fine)?
> 
> This is a bit strange, in that the observed behavior changes when I am
> logging to the serial connection.
> 
> When I am logging to serial, the failure is the same as before -
> The first suspend / resume works -
> The second fails with AHCI not working

And this is with and/or without the evtchn_move_pirqs() calls
removed? Otherwise, this might allow us at least debugging
that part of the problem.

> However, when I am not logging to serial - the system goes down, but
> never comes back up. I cannot ssh in, and no graphics are displayed on
> the screen. My only recourse is to hard power cycle the machine.
> 
> This, of course makes collecting logs difficult.

Did you try whether anything would make it out to the screen
when you allow Xen to continue to access the video buffer even
post-boot? Quite possibly for this it would be advantageous (or
even required, as I don't think the video mode would get restored
after coming back out of S3) to also only use a (simpler) text mode
console (requiring that you have this up on the screen when you
invoke S3, i.e. you'd have to switch away from or not make use of
the GUI). That would be "vga=text-80x25,keep" on the Xen
command line (while 80x50 or 80x60 would allow for more output
to remain visible, even those modes would - I think - need code
to be added to get restored during resume from S3).

Jan


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