From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.18-rc4 (and earlier): CMOS clock corruption during suspend to disk on i386
Date: Wed, 9 Aug 2006 22:04:13 +0200
User-Agent: KMail/1.9.3
Cc: LKML <linux-kernel@vger.kernel.org>,
       Linux ACPI <linux-acpi@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
       Andrew Morton <akpm@osdl.org>
References: <200608091426.31762.rjw@sisk.pl> <1155145440.5418.21.camel@localhost.localdomain>
In-Reply-To: <1155145440.5418.21.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200608092204.13711.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 21

On Wednesday 09 August 2006 19:44, john stultz wrote:
> On Wed, 2006-08-09 at 14:26 +0200, Rafael J. Wysocki wrote:
> > It looks like the CMOS clock gets corrupted during the suspend to disk
> > on i386.  I've observed this on 2 different boxes.  Moreover, one of them is
> > AMD64-based and the x86_64 kernel doesn't have this problem on it.
> > 
> > Also, I've done some tests that indicate the corruption doesn't occur before
> > saving the suspend image.  It rather happens when the box is powered off
> > or rebooted (tested both cases).
> 
> Hmmm. Could you better describe the corruption you're seeing? 

After I do "echo disk > /sys/power/state" and the system suspends, the
CMOS clock settings, as visible via the BIOS setup, are more or less random.

Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/