Bug#828746: hwclock: RTC to wrong offset after reboot

2020-05-04 Thread Andrei POPESCU
Control: tags -1 moreinfo [not trimming to preserve context for -doc] On Ma, 28 iun 16, 03:41:34, Martin-Éric Racine wrote: > 2016-06-27 23:34 GMT+03:00 Andreas Henriksson : > > Control: tags -1 + moreinfo > > > > Please check the contents of your /etc/adjtime for starters. > > UTC as expected.

Bug#828746: hwclock: RTC to wrong offset after reboot

2016-06-27 Thread Martin-Éric Racine
2016-06-27 23:34 GMT+03:00 Andreas Henriksson : > Control: tags -1 + moreinfo > > Please check the contents of your /etc/adjtime for starters. UTC as expected. > Given you're using systemd you're not even running hwclock during your > boot. Please see 'systemctl status

Bug#828746: hwclock: RTC to wrong offset after reboot

2016-06-27 Thread Andreas Henriksson
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

Bug#828746: hwclock: RTC to wrong offset after reboot

2016-06-27 Thread Martin-Éric Racine
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. - -- System Information: Debian