public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Andreas Steffan <a.steffan@deas-online.de>,
	linux-pm@lists.linux-foundation.org, pavel@suse.cz,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Suspend corrupts bios clock since 2.6.21
Date: Mon, 27 Aug 2007 00:45:08 +0200	[thread overview]
Message-ID: <200708270045.09050.rjw@sisk.pl> (raw)
In-Reply-To: <46D1D6D1.5040203@shaw.ca>

On Sunday, 26 August 2007 21:38, Robert Hancock wrote:
> Andreas Steffan wrote:
> > Hallo everybody,
> > 
> > I am running fedora core 7 on my Dell latitude D810 notebook (BIOS
> > rev A05).
> > 
> > Since 2.6.21 I found that suspending (to disk and to ram) corrupts
> > the bios clock most of the time (not always). The corruption is
> > happening during suspend. When I enter the system bios right after
> > I switch the system back on, I find the bios clock is set to a time
> > far in the future (many years). I guess that problem is related to
> > the clock changes that where introduced with 2.6.21.
> > 
> > Please let me know if you want me to provide further information to
> > get this problem fixed.
> > 
> > If there is a known quirk to work around this problem, I would
> > really appreciate a hint.
> > 
> > PS: I have not yet tried 2.6.22.4-65.fc7, but the latest 2.6.22 kernel
> > before showed the same behaviour for me.
> 
> Please check if PM_TRACE is enabled in your kernel configuration. It 
> will do this intentionally.

Yes, but only if you have "1" in /sys/power/pm_trace ...

Greetings,
Rafael

  reply	other threads:[~2007-08-26 22:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.Hms7k1HwOwCbv7cPqUWGLhT5uyk@ifi.uio.no>
2007-08-26 19:38 ` PROBLEM: Suspend corrupts bios clock since 2.6.21 Robert Hancock
2007-08-26 22:45   ` Rafael J. Wysocki [this message]
2007-08-28  7:04     ` Andreas Steffan
2007-09-11 16:50     ` Pavel Machek
2007-08-26 18:31 Andreas Steffan

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=200708270045.09050.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.steffan@deas-online.de \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@suse.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