CONFIG_PM_TRACE corrupts RTC

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: CONFIG_PM_TRACE corrupts RTC
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Re: [Alsa-devel] all-modular snd-aoa
• Next by Date: Re: 2.6.17-mm2 -- drivers/built-in.o: In function `is_pci_dock_device':acpiphp_glue.c:(.text+0x12364): undefined reference to `is_dock_device'
• Previous by thread: PROBLEM: crashes of 2.4.31 kernel (oops included)
• Next by thread: Re: CONFIG_PM_TRACE corrupts RTC
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]