[lkml]   [2006]   [Jun]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: CONFIG_PM_TRACE corrupts RTC
On Mon, 26 Jun 2006 08:52:57 -0700 (PDT)
Linus Torvalds <> wrote:

> On Sun, 25 Jun 2006, Andrew Morton wrote:
> >
> > On a Sony Vaio, after a suspend-to-disk and a resume, `hwclock' says
> >
> > The Hardware Clock registers contain values that are either invalid
> > (e.g. 50th day of month) or beyond the range we can handle (e.g. Year
> > 2095).
> >
> > and after a reboot the machine takes a trip back to 1969. Setting
> > CONFIG_PM_TRACE=n prevents this.
> That's how it works. It's by design. The RTC is where the trace events are
> stored, since that's the only piece of hw that reliably survives a reboot.

Oh, I thought it found some spare space in there somehow.

Making it `default y' was a bit unfriendly. How's about `default n' and
`depends on EMBEDDED'?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-26 18:16    [W:0.069 / U:2.320 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site