mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [2.6.21] BUG: clocksource_watchdog isn't reset after resume
@ 2007-04-29 16:20 Indan Zupancic
  2007-04-29 19:25 ` Thomas Gleixner
  0 siblings, 1 reply; 4+ messages in thread
From: Indan Zupancic @ 2007-04-29 16:20 UTC (permalink / raw)
  To: tglx, johnstul, linux-kernel

Hello,

After s2ram, basically the following happens, which shouldn't happen:

[    0.880234] Clocksource tsc unstable (delta = 449782067799 ns)
[    0.881221] Time: pit clocksource has been installed.

Looking at the source, it seems that clocksource_watchdog isn't reset
after resume, while the clock source used is, and hence it thinks that
the clock is unstable.

So it appears that timekeeping_resume and/or timekeeping_suspend should
do something to prevent this from happening.

Maybe by somehow updating 'watchdog_last' after resume, but it's unclear
how that should happen, as the watchdog doesn't export any functions and
the only thing that's reachable which calls anything watchdog related is
clocksource_register().

This is a UP machine with no frequency changing CPU, so the tsc is good
to use (before someone complaints that I should use the pm timer).

An alternative would be to not select CONFIG_CLOCKSOURCE_WATCHDOG, but
it's unclear how or by what that's selected.

Greetings,

Indan



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-04-30  0:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-04-29 16:20 [2.6.21] BUG: clocksource_watchdog isn't reset after resume Indan Zupancic
2007-04-29 19:25 ` Thomas Gleixner
2007-04-29 22:54   ` Indan Zupancic
2007-04-30  0:06   ` Indan Zupancic

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®