From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39865)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X03i2-0008LQ-Rn
	for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:03:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X03ht-0005G5-RO
	for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:03:02 -0400
Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:60725)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1X03ht-0005Fy-J0
	for qemu-devel@nongnu.org; Thu, 26 Jun 2014 03:02:53 -0400
Received: by mail-wi0-f182.google.com with SMTP id bs8so417665wib.15
	for <qemu-devel@nongnu.org>; Thu, 26 Jun 2014 00:02:52 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <53ABC598.1050908@redhat.com>
Date: Thu, 26 Jun 2014 09:02:48 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <20140625183928.7492.77861.malonedeb@chaenomeles.canonical.com>	<20140625183928.7492.77861.malonedeb@chaenomeles.canonical.com>
	<53AB2D0C.6020803@redhat.com>
In-Reply-To: <53AB2D0C.6020803@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Bug 1334397] [NEW] cmos RTC alarms no longer wake
 system from suspend
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bug 1334397 <1334397@bugs.launchpad.net>, qemu-devel@nongnu.org

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