From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ed Sweetman <safemode@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: athlon 64 dual core tsc out of sync
Date: Sat, 4 Feb 2006 19:52:40 +0000 [thread overview]
Message-ID: <200602041952.40945.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1139079812.2791.45.camel@mindpipe>
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.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-02-04 19:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 2:10 Ed Sweetman
2006-02-04 19:03 ` Lee Revell
2006-02-04 19:52 ` Alistair John Strachan [this message]
2006-02-04 21:55 ` Ed Sweetman
2006-02-04 19:16 ` Lee Revell
2006-02-05 16:32 ` Andi Kleen
2006-02-06 1:12 ` Ed Sweetman
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=200602041952.40945.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=safemode@comcast.net \
/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
all inboxes | Powered by JetHome®