From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot) Date: Sun, 03 Jan 2016 21:37:08 -0600 Message-ID: <87k2nqypw1.fsf@dustycloud.org> References: <87ege42bg6.fsf@dustycloud.org> <87lh8amkic.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60403) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG5vX-0002a3-29 for bug-guix@gnu.org; Mon, 04 Jan 2016 09:16:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aG5vW-0002sT-4q for bug-guix@gnu.org; Mon, 04 Jan 2016 09:16:03 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:49013) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG5vW-0002sO-15 for bug-guix@gnu.org; Mon, 04 Jan 2016 09:16:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aG5vV-0003Qy-T8 for bug-guix@gnu.org; Mon, 04 Jan 2016 09:16:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87lh8amkic.fsf@netris.org> 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: Mark H Weaver Cc: 22274@debbugs.gnu.org Mark H Weaver writes: > 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? Yes it isn't the battery. I've also verified that this happens on my friend Aeva's minifree x200 w/ Libreboot + Guix. More on that in my next email. >> 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 I've done this and I ran into problems still. However, I think I figured out the source of them... I suspect there were two problems. I'll detail in my reply to Ludovic.