-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2017-11-06 at 21:29 -0500, Felix Miata wrote:
Oliver Neukum composed on 2017-11-06 09:25 (UTC+0100):
Thanks for your helpful reply!
Felix Miata composed:
Booted ~8 year old Dell (BIOS) PC to Grub menu prior to 2AM.
I guess we can assume that this issue does not depend on hardware.
Local time reverted to 1AM at 2AM before I proceeded with a Grub selection.
Which time zone? RTC running at local time or UTC?
Local, as all machines on LAN over which any choice is possible.
:-?
Selected 42.3 in Grub and proceeded to boot.
Logged in only after more than an hour passed, after 3AM local standard time.
Firstly, bugzilla may be a better forum to file this bug, although I admit you hit a pretty unusual bug.
If there even is a bug here.
Secondly, could you fiddle with your RTC to reproduce the issue? If we can test for this issue only once a year we have a problem.
I'm at a loss to imagine how to include any NTP server component, if it's relevant, which I would not expect given that most of the Internet and probably all public NTP servers run on UTC.
OTOH, I'm having brainlock over when to boot vis a vis when to change the RTC and in which direction. Maybe this needs to wait until I can better concentrate, not too easy lately.
I think you may have some confusion about time. NTP always serves UTC time, here and the other side the globe, inside your house and outside. There is no choice about this. Linux always uses internally UTC time⁽¹⁾. There is no choice about this. Linux filesystems also use UTC time, AFAIK. Linux displays to the user the time in the time zone he requests, by calculation from the UTC time and tables. Where there is choice is on the RTC time chip. This is a little CMOS chip with a dedicated battery which keeps a clock, with the purpose of setting the computer clock with correct time when it boots, without asking you or internet. This CMOS chip also holds the BIOS configuration in a little RAM, backed with that same battery. This RTC clock can hold UTC time or Local time⁽²⁾, in which case Linux has to calculate the UTC time from it and tables. The calculation is of course different at DST change: has DST already happened, or not? Impossible to know. Thus if your RTC clock holds Local time and you happened to boot the computer just in that interval it is impossible to handle correctly (the clock time that happened twice that night). A time related bug at that instant can not be handled, would be WONTFIX. Having the RTC time keep local time is not justified currently, unless you keep obsolete operating systems. Yes, Windows can keep there UTC time since Windows 7, with a little registry change⁽³⁾. Using Local time causes untold number of problems, and IIRC openSUSE devs have given up on handling it, understandably. (1) actually some other time name, but not relevant. (2) or any arbitrary time (3) https://en.opensuse.org/SDB:Configuring_the_clock#Other_OS - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloBvdcACgkQtTMYHG2NR9VGqQCcCkiL7fKYkIRYMKxH0qRbQf7v tZMAn3IWJQ0Hh/ufX3U8J4cvLQyEBRBy =gaPt -----END PGP SIGNATURE-----