From: Andi Kleen <ak@suse.de>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: Andi Kleen <ak@suse.de>, Erick Turnquist <jhujhiti@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Lost Ticks on x86_64
Date: Sun, 7 Aug 2005 18:19:02 +0200 [thread overview]
Message-ID: <20050807161902.GX8266@wotan.suse.de> (raw)
In-Reply-To: <080720051429.26355.42F61ABC0005F4BA000066F3220699849900009A9B9CD3040A029D0A05@comcast.net>
On Sun, Aug 07, 2005 at 02:29:16PM +0000, Parag Warudkar wrote:
> > No way to fix this, but you can work around it with very new kernels
> > by compiling with a lower HZ than 1000.
>
> John Stultz's timeofday patches seem to fix this lost ticks issue. You might want to try them.
>
> (I too, routinely get "lost ticks - rip is at acpi_processor_idle" messages which vanished during the period when I was trying John's patches.)
They will just hide the problem in this case.
-Andi
next prev parent reply other threads:[~2005-08-07 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 14:29 Lost Ticks on x86_64 Parag Warudkar
2005-08-07 16:19 ` Andi Kleen [this message]
[not found] <5348b8ba050806204453392f7f@mail.gmail.com.suse.lists.linux.kernel>
2005-08-07 11:36 ` Andi Kleen
2005-08-07 17:07 ` Erick Turnquist
2005-08-07 17:48 ` Tim Hockin
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
-- 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=20050807161902.GX8266@wotan.suse.de \
--to=ak@suse.de \
--cc=jhujhiti@gmail.com \
--cc=kernel-stuff@comcast.net \
--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