[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708270045.09050.rjw@sisk.pl>
Date: Mon, 27 Aug 2007 00:45:08 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Robert Hancock <hancockr@...w.ca>
Cc: Andreas Steffan <a.steffan@...s-online.de>,
linux-pm@...ts.linux-foundation.org, pavel@...e.cz,
linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Suspend corrupts bios clock since 2.6.21
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists