Subject: PROBLEM: Suspend corrupts bios clock since 2.6.21
From: Andreas Steffan <a.steffan@deas-online.de>
To: linux-pm@lists.linux-foundation.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, pavel@suse.cz,
       linux-kernel@vger.kernel.org
Content-Type: text/plain
Date: Sun, 26 Aug 2007 20:31:00 +0200
Message-Id: <1188153060.14603.31.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1376
Lines: 37

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.
--
regards 
Andreas

+-----------------------------------------------------------+
Andreas Steffan              email: a.steffan@deas-online.de
Hamburg, Germany             mobil: +49179 3903615
+-----------------------------------------------------------+

In theory, practice and theory are the same, but in practice
they are different -- Larry McVoy

-
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/