Re: clockevents: fix resume logic

Thomas Gleixner
2007-09-11T19:52:18Z

On Tue, 2007-09-11 at 11:44 -0700, Andrew Morton wrote:
> > > there doesn't seem to be a lot of difference in the time handling, except
> > > there are large changes in when things happen in the bootup sequence.
> >
> > The question is whether the system goes into C2 with the patch applied.
> >
> > Can you please provide the output of /proc/acpi/processor/CPU0/power for
> > both the bad and the good one ?
> >
>
> good:
>
> sony:/home/akpm> cat /proc/acpi/processor/CPU0/power
> active state: C0
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 8000 usec
> states:
> C1: type[C1] promotion[--] demotion[--] latency[001] usage[00000000] duration[00000000000000000000]
> C2: type[C2] promotion[--] demotion[--] latency[001] usage[00000000] duration[00000000000000000000]
>
> bad:
>
> sony:/home/akpm> cat /proc/acpi/processor/CPU0/power
> active state: C2
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 8000 usec
> states:
> C1: type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] duration[00000000000000000000]
> *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[00008316] duration[00000000000170717293]

Ok, here we are. The bad one uses C2 which stops the local apic on the
VAIO. I suspect we end up in the suspend/resume with going into C2
without the broadcast active.

Can you try to get the output of SysRq-Q during the "it needs help from
keyboard" period ?

tglx