From: Paolo Bonzini <pbonzini@redhat.com>
To: Bug 1334397 <1334397@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1334397] [NEW] cmos RTC alarms no longer wake system from suspend
Date: Thu, 26 Jun 2014 09:02:48 +0200 [thread overview]
Message-ID: <53ABC598.1050908@redhat.com> (raw)
In-Reply-To: <53AB2D0C.6020803@redhat.com>
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
next prev parent reply other threads:[~2014-06-26 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 18:39 [Qemu-devel] [Bug 1334397] [NEW] cmos RTC alarms no longer wake system from suspend John Stultz
2014-06-25 20:11 ` Paolo Bonzini
2014-06-26 7:02 ` Paolo Bonzini [this message]
2014-06-26 10:01 ` Paolo Bonzini
2014-06-26 10:02 ` [Qemu-devel] [Bug 1334397] " Paolo Bonzini
2014-06-26 16:16 ` John Stultz
2014-06-26 16:56 ` John Stultz
2017-07-21 14:32 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ABC598.1050908@redhat.com \
--to=pbonzini@redhat.com \
--cc=1334397@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.