[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3

>>> On 31.12.12 at 13:51, Ben Guthro <ben.guthro@xxxxxxxxx> wrote:
> My current suspicion is irq delivery, because of the following messages I
> see on the console on the way down:
> (XEN) Preparing system for ACPI S3 state.
> (XEN) Disabling non-boot CPUs ...
> (XEN) Broke affinity for irq 1
> (XEN) Broke affinity for irq 9
> (XEN) Broke affinity for irq 12
> (XEN) Broke affinity for irq 26
> (XEN) Broke affinity for irq 30
> (XEN) Broke affinity for irq 1
> (XEN) Broke affinity for irq 1
> (XEN) Entering ACPI S3 state.

No, that's normal behavior. But you ought to be able to verify by
pinning Dom0's vCPU 0 to pCPU 0, and within Dom0 setting the
affinities of all interrupts to CPU 0 - that should make all of these
messages go away.

> Jan - any suggestions on how to procede with this? FWIW, Xen 4.0.y suspends
> on this machine reliably.

With two scheduler related changesets having got spotted as
problematic by now (23255:1f95b55ef427 and 23269:d67e4d12723f,
albeit the latter not really scheduler specific), I'm really very much
hoping for George to have an idea, the more that ...


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.