Re: [regression] __tick_program_event of hpet is stuck

[Thomas Gleixner <tglx@linutronix.de>]

On Tue, 9 Sep 2008, Frans Pop wrote:
> On Tuesday 09 September 2008, Thomas Gleixner wrote:
> > > CE: __tick_program_event of hpet is stuck 1468f1b3c9 1468f1c751
> > > CE: increasing min_delta_ns 5000 to 10000 nsec
> > > [...]
> > > CE: __tick_program_event of hpet is stuck 33576032f74 33576035684
> > > CE: increasing min_delta_ns 10000 to 20000 nsec
> > > [...]
> > > CE: __tick_program_event of hpet is stuck 63242b30d28 63242b35b48
> > > CE: increasing min_delta_ns 20000 to 40000 nsec
> >
> > what's the highest value which you have seen ?
> 
> These are the highest I've seen, but that's possibly because I haven't 
> left the system running for longer. There's just under an hour between 
> the messages (kern.log has 00:59:17, 01:56:38, 02:51:23 for the three 
> increases listed above) with the first fairly shortly after boot.
> 
> I've just awakened the laptop from suspend and will let it sit for the 
> rest of the day. If I get any higher values I'll let you know.

It's nothing to worry about. I out the WARN_ON() there to get some
information about the validation of min_delta_ns and to see in which
range this happens.

I'm going to remove the WARN_ON() and just keep the information that
we need to increase the min_delta_ns value for safe operation.

Thanks,

	tglx