[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen4.2 S3 regression?
>>> On 20.09.12 at 22:30, Ben Guthro <ben@xxxxxxxxxx> wrote: > On Thu, Sep 20, 2012 at 8:56 AM, Ben Guthro <ben@xxxxxxxxxx> wrote: > [ 32.145824] ACPI: Preparing to enter system sleep state S3 > [ 32.600118] PM: Saving platform NVS memory > [ 32.671666] Disabling non-boot CPUs ... > (XEN) Preparing system for ACPI S3 state. > (XEN) Disabling non-boot CPUs ... > (XEN) Bringing CPU1 down > (XEN) Disabling CPU1 > (XEN) Disabled CPU1 > (XEN) play_dead: CPU1 > (XEN) cpu_exit_clear: CPU1 > (XEN) cpu_uninit: CPU1 > (XEN) CPU1 dead So how about inserting printout of cpu_initialized here ... > (XEN) Entering ACPI S3 state. > (XEN) Finishing wakeup from ACPI S3 state. > (XEN) Enabling non-boot CPUs ... ... and here? Plus adding "cpuinfo" to the Xen command line, which would allow us to see whether CPU1 gets into cpu_init() twice. Perhaps tracking cpu_state throughout the below sequence might also be useful. > (XEN) Bringing CPU1 up > (XEN) Setting warm reset code and vector. > (XEN) Asserting INIT. > (XEN) Waiting for send to finish... > (XEN) +Deasserting INIT. > (XEN) Waiting for send to finish... > (XEN) +#startup loops: 2. > (XEN) Sending STARTUP #1. > (XEN) After apic_write. > (XEN) CPU#1 already initialized! > (XEN) Startup point 1. > (XEN) Waiting for send to finish... > (XEN) +Sending STARTUP #2. > (XEN) After apic_write. > (XEN) Startup point 1. > (XEN) Waiting for send to finish... > (XEN) +After Startup. > (XEN) After Callout 1. > (XEN) Stuck ?? > (XEN) cpu_exit_clear: CPU1 > (XEN) cpu_uninit: CPU1 > (XEN) __cpu_up - do_boot_cpu error > (XEN) cpu_up CPU1 CPU not up > (XEN) cpu_up CPU1 fail > (XEN) Error taking CPU1 up: -5 > [ 32.780055] ACPI: Low-level resume complete > [ 32.780055] PM: Restoring platform NVS memory > [ 32.780055] Enabling non-boot CPUs ... > > then it crashes. > > It seems that it is always falling through into the "else" clause of > the do_boot_cpu() function when attempting to bring it back up, seemingly > stuck in CPU_STATE_CALLOUT > > > Any ideas as to what might be causing it to get stuck in that state? That's because CPU1 is stuck in cpu_init() (in the infinite loop after printing "CPU#1 already initialized!"), as Keir pointed out yesterday. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |