Arch Linux

kruegsch

Member

Registered: 2011-12-25

Posts: 2

Broken RTC after a long suspend to RAM session

I'm facing a strange problem. After a clean boot I put my notebook to suspend to RAM for several hours. After I waked it up I had a wrong time and date. I corrected the settings but it boots now with an call trace and strange time and date values.

I have a dual boot configuration with windows, that is affected, too. I use Systemd, thus both systems use UTC time. I used the kernel version 3.2RC7 but the current arch kernel throws the same error.
My machine is a Sony Vaio SE with intel HM67 chipset and Intel Core-i7 (sandy bridge) CPU.

What I did so far:

* I've tried to set the time in both operation systems via ntp and manually. A Ntp update and "hwclock -u -w" do exactly what I expect: "hwclock -r" shows the correct date. I have no adjust file!

* I can set the correct date in the BIOS (Insyde H2O, Rev3.5) but the OSs will mess it up.

* I tried a CMOS reset - no luck

My logs in short:
*Normal boot:

...
Dec 24 11:33:33 localhost kernel: [    0.000000] NR_IRQS:4352 nr_irqs:712 16
Dec 24 11:33:33 localhost kernel: [    0.000000] Extended CMOS year: 2000
...
Dec 24 11:33:33 localhost kernel: [    0.424861] RTC time: 10:33:30, date: 12/24/11

*Suspend-to-RAM

...
Dec 24 11:35:41 localhost kernel: [  131.992508] PM: Syncing filesystems ... done.
Dec 24 11:35:41 localhost kernel: [  131.993527] PM: Preparing system for mem sleep
Jan  1 03:11:55 localhost kernel: [  132.262015] Freezing user space processes ... (elapsed 0.01 seconds) done.
Jan  1 03:11:55 localhost kernel: [  132.272911] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Jan  1 03:11:55 localhost kernel: [  132.283894] PM: Entering mem sleep
...
Jan  1 03:11:55 localhost kernel: [  133.483186] Disabling non-boot CPUs ...
Jan  1 03:11:55 localhost kernel: [  133.484797] CPU 1 is now offline
Jan  1 03:11:55 localhost kernel: [  133.485589] Broke affinity for irq 47
Jan  1 03:11:55 localhost kernel: [  133.486604] CPU 2 is now offline
Jan  1 03:11:55 localhost kernel: [  133.488089] CPU 3 is now offline
Jan  1 03:11:55 localhost kernel: [  133.488261] ------------[ cut here ]------------
Jan  1 03:11:55 localhost kernel: [  133.488268] WARNING: at arch/x86/kernel/rtc.c:136 mach_get_cmos_time+0x18a/0x1a0()
Jan  1 03:11:55 localhost kernel: [  133.488269] Hardware name: VPCSE1V9E
Jan  1 03:11:55 localhost kernel: [  133.488271] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek tpm_infineon sr_mod cdrom snd_hda_intel snd_hda_codec snd_pcm r8169 snd_timer iwlwifi snd rts_pstor(C) soundcore snd_page_alloc tpm_tis tpm tpm_bios
Jan  1 03:11:55 localhost kernel: [  133.488286] Pid: 2590, comm: pm-suspend Tainted: G         C   3.2.0-rc7NSY+ #1
Jan  1 03:11:55 localhost kernel: [  133.488288] Call Trace:
Jan  1 03:11:55 localhost kernel: [  133.488293]  [<ffffffff8103b1db>] ? warn_slowpath_common+0x7b/0xc0
Jan  1 03:11:55 localhost kernel: [  133.488296]  [<ffffffff8100a2ba>] ? mach_get_cmos_time+0x18a/0x1a0
Jan  1 03:11:55 localhost kernel: [  133.488298]  [<ffffffff8100a2fa>] ? read_persistent_clock+0xa/0x20
Jan  1 03:11:55 localhost kernel: [  133.488301]  [<ffffffff8105f0e4>] ? timekeeping_suspend+0x14/0x110
Jan  1 03:11:55 localhost kernel: [  133.488304]  [<ffffffff812a9b05>] ? syscore_suspend+0x45/0x130
Jan  1 03:11:55 localhost kernel: [  133.488306]  [<ffffffff81072249>] ? suspend_devices_and_enter+0x199/0x210
Jan  1 03:11:55 localhost kernel: [  133.488308]  [<ffffffff8107241b>] ? enter_state+0x15b/0x180
Jan  1 03:11:55 localhost kernel: [  133.488309]  [<ffffffff8107129a>] ? state_store+0xca/0x140
Jan  1 03:11:55 localhost kernel: [  133.488312]  [<ffffffff8113b182>] ? sysfs_write_file+0xd2/0x160
Jan  1 03:11:55 localhost kernel: [  133.488315]  [<ffffffff810ded4a>] ? vfs_write+0xaa/0x170
Jan  1 03:11:55 localhost kernel: [  133.488316]  [<ffffffff810df057>] ? sys_write+0x47/0x90
Jan  1 03:11:55 localhost kernel: [  133.488320]  [<ffffffff814c9faf>] ? page_fault+0x1f/0x30
Jan  1 03:11:55 localhost kernel: [  133.488321]  [<ffffffff814ca3bb>] ? system_call_fastpath+0x16/0x1b
Jan  1 03:11:55 localhost kernel: [  133.488323] ---[ end trace e5f1bbacc96540b6 ]---
Jan  1 03:11:55 localhost kernel: [  133.488324] Extended CMOS year: 2000

* After a reboot

...
Jan  1 01:00:07 localhost kernel: [    0.000000] NR_IRQS:4352 nr_irqs:712 16
Jan  1 01:00:07 localhost kernel: [    0.000000] ------------[ cut here ]------------
Jan  1 01:00:07 localhost kernel: [    0.000000] WARNING: at arch/x86/kernel/rtc.c:136 mach_get_cmos_time+0x18a/0x1a0()
Jan  1 01:00:07 localhost kernel: [    0.000000] Hardware name: VPCSE1V9E
Jan  1 01:00:07 localhost kernel: [    0.000000] Modules linked in:
Jan  1 01:00:07 localhost kernel: [    0.000000] Pid: 0, comm: swapper/0 Not tainted 3.2.0-rc7NSY+ #1
Jan  1 01:00:07 localhost kernel: [    0.000000] Call Trace:
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff8103b2ab>] ? warn_slowpath_common+0x7b/0xc0
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff8100a2da>] ? mach_get_cmos_time+0x18a/0x1a0
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff8100a31a>] ? read_persistent_clock+0xa/0x20
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff816b0a36>] ? timekeeping_init+0xe/0xe4
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff814a98af>] ? register_cpu_notifier+0x1f/0x30
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff816afbd6>] ? softirq_init+0x8f/0xb6
Jan  1 01:00:07 localhost kernel: [    0.000000]  [<ffffffff816a09a8>] ? start_kernel+0x229/0x30e
Jan  1 01:00:07 localhost kernel: [    0.000000] ---[ end trace a7919e7f17c0a725 ]---
Jan  1 01:00:07 localhost kernel: [    0.000000] Extended CMOS year: 2000
...
Jan  1 01:00:07 localhost kernel: [    0.427846] RTC time:  0:00:03, date: 01/01/10

Long log: http://pastebin.com/gagmgM9a

Any suggestions?

kruegsch

Member

Registered: 2011-12-25

Posts: 2

Re: Broken RTC after a long suspend to RAM session

UPDATE
I removed the BIOS battery, waited five minutes and set the time and date in BIOS. Everythings works fine now. Seems that this small buttons isn't for CMOS reset, but disassemble the whole notebook isn't fun.