From: Marc Perkel <marc@perkel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Lost Ticks
Date: Sun, 18 Sep 2005 21:23:40 -0700 [thread overview]
Message-ID: <432E3D4C.4070508@perkel.com> (raw)
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?
Yes - I compiled the kernel 2.6.13.1 and used a speed of 100 - the
lowest setting - and that did help some. But - the problem needs to go away.
If I compile a kermel without any of the power management at all - will
that fix the problem? I need a work around.
Thanks in advance.
--
Marc Perkel - marc@perkel.com
Spam Filter: http://www.junkemailfilter.com
My Blog: http://marc.perkel.com
next reply other threads:[~2005-09-19 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 4:23 Marc Perkel [this message]
2005-09-20 7:02 ` Lost Ticks Frank van Maarseveen
2005-09-20 18:06 ` Scott Lampert
2005-09-20 18:24 ` Marc Perkel
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=432E3D4C.4070508@perkel.com \
--to=marc@perkel.com \
--cc=linux-kernel@vger.kernel.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