Date: Wed, 9 Aug 2006 13:12:32 -0700
From: Andrew Morton <akpm@osdl.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>,
       Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: 2.6.18-rc4 (and earlier): CMOS clock corruption during suspend
 to disk on i386
Message-Id: <20060809131232.75a260e1.akpm@osdl.org>
In-Reply-To: <200608092201.42885.rjw@sisk.pl>
References: <200608091426.31762.rjw@sisk.pl>
	<20060809123052.GB3808@elf.ucw.cz>
	<200608092201.42885.rjw@sisk.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1106
Lines: 27

On Wed, 9 Aug 2006 22:01:42 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Wednesday 09 August 2006 14:30, Pavel Machek wrote:
> > Hi!
> > > 
> > > 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).
> > > 
> > > Unfortunately, I have no more time to debug it further right now.
> > 
> > Do you have Linus' "please corrupt my cmos for debuggin" hack enabled?
> 
> Well, I know nothing about that. ;-)
> 

CONFIG_PM_TRACE=y will scrog your CMOS clock each time you suspend.
-
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/