From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Ed Sweetman <safemode@comcast.net>
Cc: Lee Revell <rlrevell@joe-job.com>,
Albert Cahalan <acahalan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: athlon 64 dual core tsc out of sync
Date: Sun, 5 Feb 2006 05:08:08 +0000 [thread overview]
Message-ID: <200602050508.08228.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43E56ACA.5050108@comcast.net>
On Sunday 05 February 2006 03:02, Ed Sweetman wrote:
[snip]
> In any case it's been generally accepted that pm timer is suggested to
> get around these errors, but i've been unable to use mine, there is no
> config option in menuconfig/gconfig etc and my .config seems to show
> that it's compiled in. Boot args like timer=pmtmr and just pmtmr and
> having nothing have resulted in the same dmesg output , with no mention
> of using the pm-timer. I know I used it in 2.6.14.3 and never had any
> sync issues, my setup and config hasn't changed since then except for
> the use of libata for pata. So how can i determine what's going on
> here? Default or not, i'd like to get the pmtmr in use if it's what
> works.
On x86 (NOT x86-64), clock=pmtmr does what you want.
--
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-05 5:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-02-05 2:24 ` Lee Revell
2006-02-05 5:06 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2006-02-04 2:10 Ed Sweetman
2006-02-04 19:03 ` Lee Revell
2006-02-04 19:52 ` Alistair John Strachan
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
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=200602050508.08228.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=acahalan@gmail.com \
--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®