From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot) Date: Thu, 31 Dec 2015 15:27:23 -0500 Message-ID: <87lh8amkic.fsf@netris.org> References: <87ege42bg6.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42046) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFDEb-0005mj-Vo for bug-guix@gnu.org; Fri, 01 Jan 2016 22:52:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFDEY-00041k-OL for bug-guix@gnu.org; Fri, 01 Jan 2016 22:52:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:46009) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFDEY-00041f-LJ for bug-guix@gnu.org; Fri, 01 Jan 2016 22:52:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aFDEY-0005v7-DG for bug-guix@gnu.org; Fri, 01 Jan 2016 22:52:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ege42bg6.fsf@dustycloud.org> (Christopher Allan Webber's message of "Wed, 30 Dec 2015 09:24:49 -0600") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Christopher Allan Webber Cc: 22274@debbugs.gnu.org Christopher Allan Webber writes: > I recently installed GuixSD on the laptop I got fresh from Minifree. I > was happy to see how much worked, but I've noticed a bug that occurs in > GuixSD but not in Debian. > > In Debian I can set the hardware clock (with `hwclock -w`) and if I > reboot back into Debian again, I still have the same hardware clock. > > If I reboot into GuixSD, at some point in the boot process it resets my > hardware clock to 1970! If I reboot into Debian again after that, it's > 1970 there also. Very strange. FWIW, I've used Libreboot X60 and X200 laptops running GuixSD quite extensively -- they are my primary development machines -- and I've never seen anything like this. One possibility that comes to mind is that perhaps your hardware clock battery is dead, and that sometimes Debian is able to hide that fact by setting the date via NTP or something. Can you try running "hwclock -r" after a cold boot into Debian and see what it says? > Any idea what could be causing this? I noticed that if I rebooted it > at the time that it asked me for a passphrase to decrypt /home/ that it > didn't reset the clock, though maybe I should test that again. If you're sharing /home between Debian and GuixSD, I wonder if going back and forth between two different versions of GNOME while sharing the data in dot-files/directories is causing a problem? This in turn makes me wonder if the clock is truly being reset during the GuixSD boot process, or if it might be happening during login to your desktop environment. Please try the following: * Cold boot into Debian. * Set the hardware clock (hwclock -w). * Read the hardware clock to verify that it works (hwclock -r). * Reboot into GuixSD. * Log in to a text console as root and check both the system clock (date) and the hardware clock (hwclock -r). Thanks, Mark