From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rafal Wojtczuk <rafal@invisiblethingslab.com>
Subject: S3 sleep in dom0 breaks dom0<->domU wallclock
	synchronization
Date: Thu, 1 Jul 2010 05:04:31 +0200
Message-ID: <20100701030431.GB1431@email>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hello,
xen-3.4.3 x86_64, dom0 2.6.34-9.xenlinux as dom0,
2.6.32.14-1.2.105.pvops0 in PV domU. /proc/sys/xen/independent_wallclock is
0.
After resume from S3 sleep in dom0, the wall clock in domU is
desynchronized from dom0's one (the delta is the length of S3 sleep). It
does not seem that adj_timex is in progress (the delta is constant in time).

Is it a known issue ? If so, could someone point me to a solution ?
Regards,
Rafal Wojtczuk