Re: [Qemu-devel] [Bug 1334397] [NEW] cmos RTC alarms no longer wake system from suspend

[Paolo Bonzini]

Il 25/06/2014 22:11, Paolo Bonzini ha scritto:
> The only way to have the CMOS updated is from the guest, so the guest is
> resumed.  The "RTC wakeup!" also is just before setting the
> RT_CLOCK_STATUS field in the ACPI PM1A event status register.
> 
> However, I can reproduce that the system looks indeed like it's crashed
> and I don't see neither the resumption nor the printf from the
> sigalarm() function.  This is on kernel 3.11.10.
> 
> Also, I see that register C (the current interrupt) is always read as zero.
> 
> Right now I don't have an older QEMU, but I'll look at it tomorrow.

Try running with "-qmp stdio" and, at the prompt, type:

{'execute':'qmp_capabilities'}

With 1.7.0 I see:

{"timestamp": {"seconds": 1403765768, "microseconds": 655089}, "event": 
"SUSPEND"}
{"timestamp": {"seconds": 1403765782, "microseconds": 239222}, "event": 
"WAKEUP"}

and then it hangs.

With 2.0.0 I see:

{"timestamp": {"seconds": 1403765911, "microseconds": 941161}, "event": 
"SUSPEND"}
{"timestamp": {"seconds": 1403765925, "microseconds": 295253}, "event": 
"WAKEUP"}
{"timestamp": {"seconds": 1403765926, "microseconds": 839634}, "event": 
"SUSPEND"}
{"timestamp": {"seconds": 1403765940, "microseconds": 294228}, "event": 
"WAKEUP"}
{"timestamp": {"seconds": 1403765941, "microseconds": 759962}, "event": 
"SUSPEND"}
{"timestamp": {"seconds": 1403765955, "microseconds": 295250}, "event": 
"WAKEUP"}

So it seems like it's doing things correctly.

Can you try doing this?

Paolo