Bug 203235 - PMTimer doesn't get detected in an Asus A8V Deluxe motherboard [NEEDINFO]
Summary: PMTimer doesn't get detected in an Asus A8V Deluxe motherboard
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.4
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Brian Maly
QA Contact: Red Hat Kernel QE team
: 203236 (view as bug list)
Depends On:
Blocks: RHEL4u8_relnotes
TreeView+ depends on / blocked
Reported: 2006-08-19 17:39 UTC by Kostas Georgiou
Modified: 2009-05-18 19:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-05-18 19:27:42 UTC
Target Upstream Version:
rlerch: needinfo? (bmaly)

Attachments (Terms of Use)
lspci -v output (6.38 KB, application/octet-stream)
2006-08-23 12:34 UTC, Kostas Georgiou
no flags Details
dmesg output (21.11 KB, text/plain)
2006-10-20 10:36 UTC, Kostas Georgiou
no flags Details
test patch (599 bytes, patch)
2008-09-25 05:51 UTC, Brian Maly
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:1024 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 4.8 kernel security and bug fix update 2009-05-18 14:57:26 UTC

Description Kostas Georgiou 2006-08-19 17:39:55 UTC
The PMTimer doesn't get detected in an Asus A8V Deluxe motherboard (VIA
K8T800Pro) so the system uses TSC (even when you use
the notsc kernel option). This results in problems (#174390 for example) with
dual core cpus since TSC isn't stable there.
$ dmesg
time.c: Using 1.193182 MHz PIT timer.
time.c: Using PIT/TSC based timekeeping.

Under FC5 the PMTimer is detected fine in the same motherboard (with a single
core cpu though)
$ dmesg
ACPI: PM-Timer IO Port: 0x808
time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.

Comment 1 Jason Baron 2006-08-22 18:02:25 UTC
*** Bug 203236 has been marked as a duplicate of this bug. ***

Comment 2 Brian Maly 2006-08-22 20:33:13 UTC
What kernel version is this issue reproducable on (i.e. "uname -a")?

What chipset does this motherboard use (i.e. "lspci -v")?

Comment 3 Kostas Georgiou 2006-08-23 12:32:54 UTC
I tried kernel-smp-2.6.9-34.0.2.EL kernel-smp-2.6.9-42.EL (x86_64 of course).
The chipset is K8T800Pro, I am attaching the output of lspci -v
as well.

Comment 4 Kostas Georgiou 2006-08-23 12:34:40 UTC
Created attachment 134704 [details]
lspci -v output

Comment 5 Kostas Georgiou 2006-08-26 17:11:19 UTC
Hmm not sure why the "I am providing the requested information for this bug."
button doesn't work. Trying again. 

Comment 6 Kostas Georgiou 2006-08-26 17:21:55 UTC
It seems that the patch in bug #203374 solves the problems with using TSC so I
am dropping the severity to low since the machine is usable now.

Comment 7 Brian Maly 2006-09-12 15:30:34 UTC
Can you attach your /var/log/dmesg?

Also, do either of these boot paramaters make a difference?

"acpi_skip_timer_override" or "acpi=off"

Comment 8 Kostas Georgiou 2006-10-20 10:36:28 UTC
Created attachment 138958 [details]
dmesg output

Comment 9 Kostas Georgiou 2006-10-20 11:17:35 UTC
I'll test with acpi_skip_timer_override and acpi=off next week.

Comment 11 Kostas Georgiou 2007-03-18 18:37:29 UTC
Sorry I forgot to reply, no acpi_skip_timer_override/acpi=off doesn't seem to help.

Comment 12 Brian Maly 2007-03-21 20:28:16 UTC
can you boot with "acpi_dbg_level=1 acpi_dbg_layer=1" boot args and attach the
debugging output? Looks like x86_64 acpi parser breakage of some sort.

Comment 13 Brian Maly 2008-09-25 05:51:45 UTC
Created attachment 317655 [details]
test patch

This is a test patch that may resolve the issue. 

Is the reporter willing to test this patch, or willing to instead test a kernel?

It would be optimal to get this issue fixed in the upcoming release, however we do not have this hardware in-house and must rely on outside testing for verification.

Comment 14 Kostas Georgiou 2008-10-03 11:37:05 UTC
I can easilly test the patch or a kernel. I have one of the machines free I think so I can load rhel4 and run any tests that you need. I can also provide you root access to the machine if you prefer. Let me know if this will make it easier for you.

Recently the powernow-k8.tscsync=1 kernel option that I was using to stop tsc from drifting stopped working so I was about to have a look again at the problem.

Comment 15 Brian Maly 2008-12-15 19:44:04 UTC
Just wanted to follow up on testing results.

Can you provide more info about tscsync not working? Is this really broken? 
I am wondering if we should open a seperate bug for that.

Comment 16 Brian Maly 2008-12-22 17:54:23 UTC
Can we possibly test the proposed patch? I would like to see this make RHEL4.8 if possible.

Also, did you resolve your tscsync issue? powernow-k8 was changed to a module for  RHEL4.7 so now you have to "modprobe powernow-k8 tscsync=1" to set the tscsync option.

Comment 17 Kostas Georgiou 2008-12-23 19:30:34 UTC
With the patch I get the following:

+ACPI: PM-Timer IO Port: 0x808
-time.c: Using 1.193182 MHz PIT timer.
-time.c: Detected 2002.647 MHz processor.
+time.c: Using 3.579545 MHz PM timer.
+time.c: Detected 2002.656 MHz processor.
-time.c: Using PIT/TSC based timekeeping.
+Disabling vsyscall due to use of PM timer
+time.c: Using PM based timekeeping

So the PMTimer is now detected and used by default.

As for tscsync I can only say "D'oh!", I never noticed that it was switched to a module :(

Comment 18 Brian Maly 2008-12-23 20:05:44 UTC
Thanks for the testing assistance. Ill submit this patch for RHEL4.8.

Comment 20 RHEL Program Management 2008-12-23 20:22:32 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 22 Vivek Goyal 2009-01-09 13:54:44 UTC
Committed in 78.26.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/

Comment 27 Han Pingtian 2009-05-05 05:50:14 UTC
Due to comment#17, the bug had been fixed. And the patch,
has been included in 2.6.9-89.EL. Will change the status to VERIFIED,

Comment 29 errata-xmlrpc 2009-05-18 19:27:42 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.