From: Lee Trager <Lee@PicturesInMotion.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-smp@vger.kernel.org
Subject: Re: Time Fast on SMP
Date: Fri, 06 Jan 2006 00:20:32 -0500 [thread overview]
Message-ID: <43BDFE20.4070700@PicturesInMotion.net> (raw)
In-Reply-To: <20060104224356.350f6d09.rdunlap@xenotime.net>
I tired the patch with and with out disable_timer_pin_1 as boot options
and I still get a fast clock :\
Randy.Dunlap wrote:
>On Thu, 05 Jan 2006 01:33:02 -0500 Lee Trager wrote:
>
>
>
>>I recently upgraded from an AMD 3500+ to an AMD X2 4400(dual core thus
>>SMP). After a couple of hours of use I noticed that the system clock was
>>going fast, I did some googling and found some boot options to add to my
>>kernel in order to make it go away(currently notsc no_timer_check=0).
>>While both of those help it seems that my system time does get faster
>>and faster when I do CPU intensive stuff such as compiling and gaming.
>>This problem appears on both 2.6.14 and 2.6.15. Ive looked all over for
>>patches and other fixes but ive found nothing that will fix this, Im not
>>sure if this is a kernel bug or not so I posted here to see if anyone
>>could help me before I report it. Could someone please help me?
>>
>>
>
>I don't know if it is relevant for your system, but this was
>just discussed on lkml today. There is a patch that may or
>may not help you:
> http://lkml.org/lkml/2005/11/24/188
>
>and another kernel boot option:
> disable_timer_pin_1
>that someone suggested could help.
>
>---
>~Randy
>-
>To unsubscribe from this list: send the line "unsubscribe linux-smp" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
prev parent reply other threads:[~2006-01-06 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 6:33 Time Fast on SMP Lee Trager
2006-01-05 6:43 ` Randy.Dunlap
2006-01-06 5:20 ` Lee Trager [this message]
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=43BDFE20.4070700@PicturesInMotion.net \
--to=lee@picturesinmotion.net \
--cc=linux-smp@vger.kernel.org \
--cc=rdunlap@xenotime.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.