Re: 2.6.14-rt22 (acpi_pm vs tsc vs BIOS)

[Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>]

On Fri, 2005-12-09 at 15:48 -0800, Fernando Lopez-Lezcano wrote:
> Hi all, I'm running 2.6.14-rt22 and just noticed something strange. I
> have not installed it in all machines yet, but in some of them (same
> hardware as others that seems to work fine) the TSC was selected as the
> main clock for the kernel. Remember this is one of the Athlon X2
> machines in which the TCS's drift...
> 
> dmesg shows this:
>   PM-Timer running at invalid rate: 2172% of normal - aborting.
> 
> and after that the tsc is selected as the timing source.
>   Time: tsc clocksource has been installed.
> 
> The strange thing is that this is the same hardware as on other
> machines. 

Aha! Yes but no. The BIOS makes a difference. The first BIOS that has
support for the X2 processors on this particular motherboard works fine
with regards to the acpi_pm clock source, subsequent ones make linux say
things like:
  PM-Timer running at invalid rate: 2159% of normal - aborting.
and then tsc is selected as the clock source...

> I have to install this kernel on more machines, will report
> then...
> 
> This is what's available after the boot:
> # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> jiffies tsc pit
> 
> So I selected by hand:
> # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> pit
> 
> On the machine that's not selecting tsc the options are:
> # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> acpi_pm jiffies tsc pi
> (and acpi_pm is selected, of course).
> 
> I think TSC's should never be selected on this hardware and it is known
> not to work. 

-- Fernando


-
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/