PATCH: Assume PM Timer to be reliable on broken board/BIOS
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · Olivier Fourdan
Hi all,
Background
==========
Quoted 7 lines
I have a laptop (Compaq R3480EA, AMD 64 3400+ with NForce3) and reported multiple problems related to timer issues.
In a nutshell, sometimes, the PIT/TSC timer runs 3x too fast [1]. That causes many issues, including DMA errors, MCE, and clock running way too fast (making the laptop unusable for any software development). So far, no BIOS update was able to fix the issue for me.
Shouldn't this be looked into further rather than adding this workaround? Surely Windows is using the PIT as well, so there must be some way to get it to behave properly..
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 8 lines · Robert Hancock
Quoted 4 lines
In a nutshell, sometimes, the PIT/TSC timer runs 3x too fast [1]. That causes many issues, including DMA errors, MCE, and clock running way too fast (making the laptop unusable for any software development). So far, no BIOS update was able to fix the issue for me.
Shouldn't this be looked into further rather than adding this workaround? Surely Windows is using the PIT as well, so there must be some way to get it to behave properly..
Surely, but I've been desesperatly trying to find the cause w/out success for months.
My first idea was that the BIOS doesn't set the CPU voltage properly at boot, so I made up a patch that sets the right fid/vid before any calibration but that didn't help.
The BIOS is wrong (ie the BIOS reports a 1/3 of the actual CPU speed), memtest86+ which doesn't use any ACPI or whatever reports wrong time too, so it's definitely not a Linux bug.
My guess is that Windows reinitialize some register but it's hard to tell.
Cheers,
Olivier.
Quoted 8 lines · Robert Hancock
Quoted 4 lines
In a nutshell, sometimes, the PIT/TSC timer runs 3x too fast [1]. That causes many issues, including DMA errors, MCE, and clock running way too fast (making the laptop unusable for any software development). So far, no BIOS update was able to fix the issue for me.
Shouldn't this be looked into further rather than adding this workaround? Surely Windows is using the PIT as well, so there must be some way to get it to behave properly..
Sorry for the late follow up. Well, the timer management in Windows depends on the HAL used. By default, it's the ACPI HAL that is used in this laptop.
I did re-install Windows by forcing the "Standard PC" HAL in Windows XP installation and, without ACPI, Windows exhibits the exact same problem as Linux or any other system: The clock runs 3 times too fast in Windows too...
So my guess is that the HAL ACPI in Windows does more or less the same thing that does my patch (updated, available here:
http://www.xfce.org/~olivier/r3000), it calibrates the PIT timer based on the ACPI (PM) timer.
Cheers,
Olivier.