Re: Xen4.2 S3 regression?

[Keir Fraser <keir@xen.org>]

On 27/09/2012 08:38, "Jan Beulich" <JBeulich@suse.com> wrote:

>> [   37.420030] PM: Restoring platform NVS memory
>> (XEN) microcode: collect_cpu_info for CPU0
>> (XEN) microcode: collect_cpu_info : sig=0x10676, pf=0x80, rev=0x60c
>> (XEN) microcode: collect_cpu_info for CPU1
>> (XEN) microcode: collect_cpu_info : sig=0x10676, pf=0x80, rev=0x60f
> 
> And in the end we see that both cores run on different revisions.
> 
> The mixup of Xen and Dom0 messages puzzles me too - in my
> understanding, all APs should be brought back up before
> domains get unpaused.

Ah, of course! This makes a nonsense of my explanation of the observed crash
in _csched_cpu_pick -- dom0 cannot be running while Aps are still being
brought back online, because domains are not unpaused until all CPUs are
back online.

So it's a mystery again. :)

 -- Keir

> Is that perhaps part of your problem
> with pinned vCPU-s? Or is the mixup not indicative of things
> actually happening in parallel?
> 
> Jan
> 
>> [   37.431008] Enabling non-boot CPUs ...
>> [   37.434851] installing Xen timer for CPU 1
>> [   37.439031] cpu 1 spinlock event irq 279
>> [   37.327214] Disabled fast string operations
>> [   37.458040] CPU1 is up
>> [   37.465417] ACPI: Waking up from system sleep state S3
> 
> 
>