Re: TSC marked unstable on suspend and resume

[David Fries]

On Fri, May 08, 2009 at 11:53:12PM +0200, Ondrej Zary wrote:
> On Thursday 30 April 2009 05:37:33 john stultz wrote:
> > On Wed, 2009-04-29 at 18:25 -0500, David Fries wrote:
> > > On Wed, Apr 29, 2009 at 09:45:40AM -0700, john stultz wrote:
> > > > On Fri, Feb 20, 2009 at 7:39 PM, David Fries <david@xxxxxxxxx> wrote:
> > > > > I'm getting TSC marked as unsable on hibernate to disk with
> > > > > 2.6.29-rc3. ?The last kernel I ran 2.6.24.4 ran 300+ days without a
> > > > > problem and does not loose TSC on hibernate.
> > > > >
> > > > > I'm hibernating with `echo disk > /sys/power/state`.
> > > > > These look like the relavant messages,
> > > > >
> > > > > CPU 0 irqstacks, hard=c0379000 soft=c0378000
> > > > > PID hash table entries: 1024 (order: 10, 4096 bytes)
> > > > > Fast TSC calibration using PIT
> > > > > Detected 300.705 MHz processor.
> > > > > Calibrating delay loop (skipped), value calculated using timer
> > > > > frequency.. 601.41 BogoMIPS (lpj=300705) hibernate to disk,
> > > > > Restarting tasks ... done.
> > > > > Clocksource tsc unstable (delta = 499883531 ns)
> > > > >
> > > > > model name      : AMD-K6(tm) 3D processor
> > > > > Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
> > > >
> > > > Hmm. Seems like the clocksource watchdog is having some problem
> > > > handling state around hibernate.
> >
> > Yea. This seems to be the case here. There's watchdog code and variables
> > to handle resume properly, but there isn't a corresponding suspend hook,
> > so the resume path doesn't actually change anything.
> >
> > Here's a patch you can try, I only had time to compile test it today, so
> > its untested. Hopefully I didn't miss anything obvious.
> 
> I have the same problem and the patch does not solve it for me too.

What CPU and motherboard chipset?

> I noticed that after resume, ping is unable to measue short time correctly:
> 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.000 ms
> 
> "echo tsc >/sys/devices/system/clocksource/clocksource0/current_clocksource" 
> fixes the problem until next hibernation:
> 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.223 ms

I didn't know about that, thanks for posting the tip.

-- 
David Fries <david@xxxxxxxxx>
http://fries.net/~david/ (PGP encryption key available)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/