Skip to contentSkip to conversation

CONFIG_PM_TRACE corrupts RTC

DISCUSSION Andrew Morton 3 participants 5 messages Jun 26, 2006 – Jun 27, 2006

lore
Share & tools
lore
#0 lore raw

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.

#1 lore raw
Quoted 9 lines · Andrew Morton

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.

The help-text says:

This enables some cheesy code to save the last PM event point in the RTC across reboots, so that you can debug a machine that just hangs during suspend (or more commonly, during resume).

Heh.

Linus

#2 lore raw
Quoted 8 lines · On Mon, 26 Jun 2006 08:52:57 -0700 (PDT) Linus Torvalds <[email protected]>…
Quoted 7 lines · Andrew Morton

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).

Quoted 5 lines
Quoted 2 lines

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'?

#3 lore raw
Quoted 2 lines · Andrew Morton

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

I really tried. The fact is, the RTC chips have at least 114 bytes of NVRAM available in them, and most have more. Sadly, while from a hw standpoint it's non-volatile, the firmware I was testing with cleared it all (including the extended banks etc).

Quoted 2 lines

Making it default y' was a bit unfriendly. How's about default n' and `depends on EMBEDDED'?

We can certainly make it 'default n', and perhaps hide it behind EXPERIMENTAL (it's not really, but hey..). Not EMBEDDED, though, this is literally meant to help random people who have a dead machine on suspend be able to just turn this on, test suspend, and then when suspend causes a dead machine, just turn off power and reboot immediately again, and it will tell you which device was the last one to go through the resume cycle.

Linus

#4 lore raw
Quoted 14 lines · Linus Torvalds
Quoted 2 lines · Andrew Morton

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

I really tried. The fact is, the RTC chips have at least 114 bytes of NVRAM available in them, and most have more. Sadly, while from a hw standpoint it's non-volatile, the firmware I was testing with cleared it all (including the extended banks etc).

Quoted 2 lines

Making it default y' was a bit unfriendly. How's about default n' and `depends on EMBEDDED'?

Quoted 7 lines

We can certainly make it 'default n', and perhaps hide it behind EXPERIMENTAL (it's not really, but hey..). Not EMBEDDED, though, this is literally meant to help random people who have a dead machine on suspend be able to just turn this on, test suspend, and then when suspend causes a dead machine, just turn off power and reboot immediately again, and it will tell you which device was the last one to go through the resume cycle.

This should probably be hidden in kernel debugging submenu... or perhaps even out of the config system. It is only useful if you hack the .c code, anyway, no?
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html