Control: tags -1 + moreinfo Hello Martin-Éric Racine.
I strongly doubt there's a bug in hwclock based on your description. All other similar cases I've looked into have always resulted in a local misconfiguration being the culprit. It's likely your system somehow messes up keeping track of the difference between UTC and local timezone. The time in the RTC can be set to either and the RTC does not keep track of the timezone itself. (Which would explain your 3 hour offset.) Please check the contents of your /etc/adjtime for starters. Please followup with checking the configuration of any time source you have that updates the RTC on your system. On Mon, Jun 27, 2016 at 03:30:03PM +0300, Martin-Éric Racine wrote: > Package: util-linux > Version: 2.28-5 > Severity: important > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Whenever rebooting this host, the RTC time is 3 hours ahead of what it > should be. This wasn't the case when using whatever is currently in > Debian/stable. > [...] > Init: systemd (via /run/systemd/system) [...] Given you're using systemd you're not even running hwclock during your boot. Please see 'systemctl status hwclock.service'. Please read up on the RTC handling strategy usually deployed when using systemd. Please read the information already provided in misc bug reports filed by people requesting to emulate the old strategy used by sysvinit. Some useful sources of information might be: https://wiki.archlinux.org/index.php/time https://www.freedesktop.org/software/systemd/man/timedatectl.html https://www.freedesktop.org/wiki/Software/systemd/timedated/ https://wiki.archlinux.org/index.php/systemd-timesyncd Please also let me remind you that the debian bug tracking system is not a support forum. My time is very limited and it's not possible for me to both do debian development and user support on my spare time. Please look for help elsewhere if you're not interested in paying for a support contract from me. If you're actually identified a *bug* please feel free to share your information about what the symptoms are, what's causing it and maybe even supply a tested fix for the problem. Regards, Andreas Henriksson
