https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c96 --- Comment #96 from Felix Miata <mrmazda@earthlink.net> 2012-07-10 23:36:29 UTC --- I just did a zypper dup (with kernel locked) on host m7ncd last zypper dup'd on 29 June, without first rereading from comment 93 here. I rebooted, experienced the problem, then reread from comment 93, and found finding UTC set on last line of /etc/adjtime. I changed that to LOCAL, ran mkinitrd, rebooted, and did not experience the problem, nor when I installed the newer 3.4.4 kernel and rebooted again. So, this begs a previously unasked question: How/When/Where/Why is /etc/adjtime getting left uncreated or set to UTC on systems where the clock as never been set to UTC, and has never had "Hardware Clock Set To UTC" checked in YaST during installation or after? On this host, there is no /etc/adjtime on the 11.4 & 12.1 partitions. Next boots on other 11.4, 12.1 & 12.2 hosts I'll have to look first at /etc/adjtime before doing anything else, and correcting where necessary before evaluating if this bug is occurring. -- 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.