https://bugzilla.novell.com/show_bug.cgi?id=738476 https://bugzilla.novell.com/show_bug.cgi?id=738476#c0 Summary: Till last December 20th, 2011, openSuSE 12.1, fails in recognize correctly the date/time, because takes this information literally from the BIOS clock, without consider that there is a difference between that provided by the BIOS and the real one, in UTC. Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: publio.escipion.el.africano@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Till last December 20th, 2011, openSuSE 12.1, fails in recognize correctly the date/time, because takes this information literally from the BIOS' clock, without consider that there is a difference between that provided by the BIOS and the real one, in UTC. So, SO complaints of the timestamp of the filesystems is in the future, because, according the BIOS' clock, "now" is the past. System halts. &c. This issue is coincidentally with the incapacity so synchronize at boot the time with a public time server (NTP). However, as SO fails on local clock, it has to correct the time provided by it to acquire the real time. openSuSE 12.1 till December 20th, 2011, is not correcting the clock with the time difference that my time zone establishes over the BIOS' clock. That happens, coincidentally, after I applied several patches at December 20th, 2011, one of which was SuSEfirewall2-3.6.282. I do not know if it is the reason, but I provide you what I have noticed. Perhaps the real issue is in package timezone, and some other problem that involves the recent unsuccessful synchronization through NTP is triggering the present one. Reproducible: Always Steps to Reproduce: 1.Boot the SO. 2. 3. Actual Results: SO complains at boot that filesystems' timestamps are in the future and provides a "now" time in the past, and halts. Expected Results: At least, that SO corrects the data from BIOS' clock to set it in UTC considering my time zone, so time be set at present. Although SO can not synchronize to NTP server, when it failed over local clock, it must correct the data provided by the BIOS if the SO was set in UTC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.