Thomas Gleixner wrote:
quoted text > On Mon, 1 Sep 2008, Larry Finger wrote:
>> The timed sleep is as accurate as I can measure.
>>
>> I put in some test prints. The value of pm2 is zero when the else branch of
>> the "if (hpet)" is entered; however, pm1 is 15768471. When we reach the
>> do_div(tsc2, tsc1) statement, tsc2 is zero, which I think means that the two
>> calls to tsc_read_refs() are returning the same junk value.
>
> Ok, so the pmtimer is probably detected later as unusable and disabled.
> Please check your logs for:
> "PM-Timer had inconsistent results:"
Booting 2.6.26, the dmesg output has a line that says:
PM-Timer running at invalid rate: 200% of normal - aborting.
Amazing that it should be exactly 200%. Why is the CPU running at half
speed when the PM-Timer rate is measured?
Larry
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: Regression in 2.6.27 caused by commit bfc0f59 , Larry Finger , (Mon Sep 1, 1:23 pm)