Date: Fri, 3 Jul 2015 15:07:34 +0200
From: vinc...@vinc17.net
When I run hwclock --systohc manually before the reboot, the clock
is OK after reboot. So, this seems to be a systemd bug. I've reported:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790974
Michael, since I've seen you
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
Date: Fri, 3 Jul 2015 15:07:34 +0200
From: vinc...@vinc17.net
When I run hwclock --systohc manually before the reboot, the clock
is OK after reboot. So, this seems to be a systemd bug. I've reported:
Date: Fri, 3 Jul 2015 15:38:02 +0200
From: bi...@debian.org
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
Date: Fri, 3 Jul 2015 15:07:34 +0200
From: vinc...@vinc17.net
When I run hwclock --systohc manually before the reboot, the clock
is OK after reboot. So, this seems to be a systemd
On 2015-07-01 02:24:14 +0200, Vincent Lefevre wrote:
On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
Is your cmos battery still providing power?
The machine is new, so it should. The machine was also constantly on
AC power.
Either that or your hardware clock could be broken or very
On Friday 03 July 2015 14:18:50 Arno Schuring wrote:
Date: Fri, 3 Jul 2015 15:07:34 +0200
From: vinc...@vinc17.net
When I run hwclock --systohc manually before the reboot, the clock
is OK after reboot. So, this seems to be a systemd bug. I've reported:
On 2015-07-03 15:38:02 +0200, Michael Biebl wrote:
In short, your ntp client should ensure that the clock is synced to RTC
(google for ntp 11 min mode sync if you want to know more). For that
we enable timesyncd by default in systemd.
Thanks for the information, but the documentation shouldn't
On Friday 03 July 2015 14:38:02 Michael Biebl wrote:
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
Date: Fri, 3 Jul 2015 15:07:34 +0200
From: vinc...@vinc17.net
When I run hwclock --systohc manually before the reboot, the clock
is OK after reboot. So, this seems to be a systemd bug.
On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
Is your cmos battery still providing power?
The machine is new, so it should. The machine was also constantly on
AC power.
Either that or your hardware clock could be broken or very
inaccurate.
If it loses 15 seconds just the time of a reboot,
On 30/06/15 05:52 PM, Vincent Lefevre wrote:
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the peer messages (ntp
engine ready means that this is just after a reboot). What is the
cause? Which part of the software is responsible
9 matches
Mail list logo