From: Marc Perkel <marc@perkel.com>
To: Scott Lampert <scott@lampert.org>
Cc: Frank van Maarseveen <frankvm@frankvm.com>, linux-kernel@vger.kernel.org
Subject: Re: Lost Ticks
Date: Tue, 20 Sep 2005 11:24:45 -0700 [thread overview]
Message-ID: <433053ED.7080209@perkel.com> (raw)
In-Reply-To: <43304F96.6000805@lampert.org>
Yeah - there's a patch for that here:
http://bugzilla.kernel.org/show_bug.cgi?id=5105
I haven't tried it yet but will later when I go to the data center. You
might want to try it and let me know if it actually fixed the problem.
diff --git a/arch/x86_64/kernel/time.c b/arch/x86_64/kernel/time.c
--- a/arch/x86_64/kernel/time.c
+++ b/arch/x86_64/kernel/time.c
@@ -959,9 +959,6 @@ static __init int unsynchronized_tsc(voi
are handled in the OEM check above. */
if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL)
return 0;
- /* All in a single socket - should be synchronized */
- if (cpus_weight(cpu_core_map[0]) == num_online_cpus())
- return 0;
#endif
/* Assume multi socket systems are not synchronized */
return num_online_cpus() > 1;
Mizery loves company. I'm glad I'm not the only one with this problem.
Scott Lampert wrote:
> I have the exact same problem on a ASUS A8N-SLI Premium board and
> Athlon64 4800+ X2 with every BIOS up to 1008-01. Running with notsc
> is the only way to get it to work.
>
> As an aside BIOS version 1008-003 is available for this board however
> this one seems to be WAY worse as the board won't even boot. It gets
> panics before the boot messages unless you boot with noapic and after
> that it gets checksum errors on the RSDP. I'm afraid to see what the
> next official BIOS version does. :/
> -Scott
>
> Frank van Maarseveen wrote:
>
>> On Sun, Sep 18, 2005 at 09:23:40PM -0700, Marc Perkel wrote:
>>
>>
>>> Got a dual core Athlon 64 X2 on an Asus board using NVidia chipset
>>> and getting lost ticks. The software clock of course is totally
>>> messed up. I've scanned google for a solution and see others
>>> complaining about bad code in the SMM BIOS. I have the latest bios
>>> and whatever they need to fix - isn't.
>>>
>>> So - what do I do to make it work?
>>>
>>
>>
>> See http://bugzilla.kernel.org/show_bug.cgi?id=5105
>>
>> On the kernel command-line:
>>
>> x86_64: try "notsc"
>> i386: try "clock=pit"
>>
>> "nosmp" works but isn't fun.
>>
>>
>>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Marc Perkel - marc@perkel.com
Spam Filter: http://www.junkemailfilter.com
My Blog: http://marc.perkel.com
next prev parent reply other threads:[~2005-09-20 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 4:23 Lost Ticks Marc Perkel
2005-09-20 7:02 ` Frank van Maarseveen
2005-09-20 18:06 ` Scott Lampert
2005-09-20 18:24 ` Marc Perkel [this message]
2005-09-20 18:39 ` Scott Lampert
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=433053ED.7080209@perkel.com \
--to=marc@perkel.com \
--cc=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@lampert.org \
/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