From: Ed Sweetman <safemode@comcast.net>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: Re: athlon 64 dual core tsc out of sync
Date: Sat, 04 Feb 2006 16:55:51 -0500 [thread overview]
Message-ID: <43E522E7.9010800@comcast.net> (raw)
In-Reply-To: <200602041952.40945.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
>On Saturday 04 February 2006 19:03, Lee Revell wrote:
>
>
>>On Fri, 2006-02-03 at 21:10 -0500, Ed Sweetman wrote:
>>
>>
>>>I know this has been gone over before, and I am aware of the possible
>>>fix being the use of the pmtmr.
>>>
>>>My question is, if there is support builtin to the kernel for more than
>>>one timer, and we know that no timer but the pmtimer is reliable on a
>>>dual core system, why doesn't the startup of the kernel choose the
>>>pmtimer based on if it detects the system is a dual core proc with smp
>>>enabled? And if the pmtimer doesn't fix this sync issue, is there a
>>>fix out there? Currently with 2.6.16-rc1-mm5 the non-customized boot
>>>args to the kernel results in these messages.
>>>
>>>
>>Excellent question. What's the status of this bug? It's a showstopper
>>for a ton of people on the JACK list...
>>
>>
>
>As Andi has recounted many times already, pmtmr is now the default on x86-64
>if it's built in. I'm sure you can confirm this from the sources.
>
>[alistair] 19:52 [~] uname -a
>Linux damocles 2.6.15.1 #5 SMP PREEMPT Wed Feb 1 09:43:23 GMT 2006 x86_64
>x86_64 x86_64 GNU/Linux
>
>[alistair] 19:52 [~] dmesg | egrep -e time.c.*PM
>time.c: Using 3.579545 MHz PM timer.
>time.c: Using PM based timekeeping.
>
>
>
this is the relevent (as far as i know) section of my .config i'm using now.
CONFIG_HPET_TIMER=y
CONFIG_X86_PM_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
CONFIG_RTC=y
# CONFIG_HPET is not set
Now, there is no option in menuconfig for choosing pm timer, so i take
it that the config option here compiles it in. Note, ACPI is also
compiled in, without any apm code so acpi is enabled, as is apic.
This is my dmesg output.
Feb 3 16:22:49 psuedomode kernel: ACPI: PM-Timer IO Port: 0x4008
Feb 3 16:22:49 psuedomode kernel: time.c: Using 1.193182 MHz PIT timer.
Feb 3 16:22:49 psuedomode kernel: time.c: Using PIT/TSC based timekeeping.
So what happened to the pm timer. I used to use the pm timer when i was
using older kernels, 2.6.14.3'ish.
next prev parent reply other threads:[~2006-02-04 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 2:10 athlon 64 dual core tsc out of sync Ed Sweetman
2006-02-04 19:03 ` Lee Revell
2006-02-04 19:52 ` Alistair John Strachan
2006-02-04 21:55 ` Ed Sweetman [this message]
2006-02-04 19:16 ` Lee Revell
2006-02-05 16:32 ` Andi Kleen
2006-02-06 1:12 ` Ed Sweetman
-- strict thread matches above, loose matches on Subject: below --
2006-02-04 20:24 Albert Cahalan
2006-02-05 1:00 ` Lee Revell
2006-02-05 1:45 ` Albert Cahalan
2006-02-05 2:08 ` Lee Revell
2006-02-05 3:02 ` Ed Sweetman
2006-02-05 5:08 ` Alistair John Strachan
2006-02-05 2:24 ` Lee Revell
2006-02-05 5:06 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E522E7.9010800@comcast.net \
--to=safemode@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=s0348365@sms.ed.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox