From: Tim Hockin <thockin@hockin.org>
To: Andi Kleen <ak@suse.de>
Cc: Erick Turnquist <jhujhiti@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Lost Ticks on x86_64
Date: Sun, 7 Aug 2005 10:48:11 -0700 [thread overview]
Message-ID: <20050807174811.GA31006@hockin.org> (raw)
In-Reply-To: <p73mznuc732.fsf@bragg.suse.de>
On Sun, Aug 07, 2005 at 01:36:01PM +0200, Andi Kleen wrote:
> Erick Turnquist <jhujhiti@gmail.com> writes:
>
> > Hi, I'm running an Athlon64 X2 4400+ (a dual core model) with an
> > nVidia GeForce 6800 Ultra on a Gigabyte GA-K8NXP-SLI motherboard and
> > getting nasty messages like these in my dmesg:
> >
> > warning: many lost ticks.
> > Your time source seems to be instable or some driver is hogging interupts
> > rip default_idle+0x20/0x30
>
> It's most likely bad SMM code in the BIOS that blocks the CPU too long
> and is triggered in idle. You can verify that by using idle=poll
> (not recommended for production, just for testing) and see if it goes away.
>
> No way to fix this, but you can work around it with very new kernels
> by compiling with a lower HZ than 1000.
Some BIOSes do not lock SMM, and you *could* turn it off at the chipset
level.
next prev parent reply other threads:[~2005-08-07 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5348b8ba050806204453392f7f@mail.gmail.com.suse.lists.linux.kernel>
2005-08-07 11:36 ` Lost Ticks on x86_64 Andi Kleen
2005-08-07 17:07 ` Erick Turnquist
2005-08-07 17:48 ` Tim Hockin [this message]
2005-08-07 18:46 ` Erick Turnquist
2005-08-07 20:14 ` Tim Hockin
2005-08-08 12:01 ` Andi Kleen
2005-08-08 16:47 ` Tim Hockin
2005-08-08 16:51 ` Andi Kleen
2005-08-08 18:09 ` Lee Revell
2005-08-07 18:51 ` Lee Revell
2005-08-07 20:04 ` Zwane Mwaikambo
2005-08-07 21:24 ` Tim Hockin
2005-08-07 14:29 Parag Warudkar
2005-08-07 16:19 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-08-07 3:44 Erick Turnquist
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=20050807174811.GA31006@hockin.org \
--to=thockin@hockin.org \
--cc=ak@suse.de \
--cc=jhujhiti@gmail.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 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.