From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.18-rc4 (and earlier): CMOS clock corruption during suspend to disk on i386
Date: Wed, 9 Aug 2006 22:01:42 +0200 [thread overview]
Message-ID: <200608092201.42885.rjw@sisk.pl> (raw)
In-Reply-To: <20060809123052.GB3808@elf.ucw.cz>
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. ;-)
Rafael
next prev parent reply other threads:[~2006-08-09 20:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 12:26 2.6.18-rc4 (and earlier): CMOS clock corruption during suspend to disk on i386 Rafael J. Wysocki
2006-08-09 12:30 ` Pavel Machek
2006-08-09 20:01 ` Rafael J. Wysocki [this message]
2006-08-09 20:12 ` Andrew Morton
2006-08-09 20:51 ` Rafael J. Wysocki
2006-08-10 0:12 ` Pavel Machek
2006-08-10 12:15 ` Rafael J. Wysocki
2006-08-10 20:51 ` Rafael J. Wysocki
2006-08-12 19:08 ` Jesse Brandeburg
2006-08-12 19:11 ` Rafael J. Wysocki
2006-08-13 22:33 ` Pavel Machek
2006-08-14 8:41 ` Rafael J. Wysocki
2006-08-13 22:33 ` Pavel Machek
2006-08-09 17:44 ` john stultz
2006-08-09 20:04 ` Rafael J. Wysocki
2006-08-09 20:13 ` john stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608092201.42885.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox