From: Michael Monnerie <michael.monnerie@it-management.at>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
linux-kernel@vger.kernel.org
Subject: Re: rtc: lost some interrupts at 256Hz
Date: Fri, 21 Apr 2006 10:52:58 +0200 [thread overview]
Message-ID: <200604211052.59498@zmi.at> (raw)
In-Reply-To: <1145571721.5412.47.camel@mindpipe>
[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]
On Freitag, 21. April 2006 00:22 Lee Revell wrote:
> I asked about the app because I was wondering whether he had a server
> or a desktop.
It's all servers. The Hz rate can change over time:
Mar 3 02:04:41 baum kernel: rtc: lost some interrupts at 256Hz.
Mar 3 02:04:53 baum kernel: rtc: lost some interrupts at 256Hz.
Mar 3 02:04:55 baum kernel: rtc: lost some interrupts at 256Hz.
Mar 3 02:38:19 baum kernel: rtc: lost some interrupts at 256Hz.
Mar 3 02:42:22 baum kernel: rtc: lost some interrupts at 256Hz.
Mar 16 15:53:50 baum kernel: rtc: lost some interrupts at 2048Hz.
Mar 16 15:54:01 baum kernel: rtc: lost some interrupts at 2048Hz.
Mar 16 16:29:33 baum kernel: rtc: lost some interrupts at 2048Hz.
Mar 29 23:01:36 baum kernel: warning: many lost ticks.
Interesting may be the fact that VMware runs on at least some hosts. I
didn't check if all servers have it, but I found a good article on
vmware support:
http://www.vmware.com/support/kb/enduser/std_adp.php?p_sid=tthOqz5i&p_lva=&p_faqid=1420&p_created=1093994398&p_sp=cF9zcmNoPTEmcF9ncmlkc29ydD0mcF9yb3dfY250PTE3JnBfc2VhcmNoX3RleHQ9bG9zdCBzb21lIGludGVycnJ1cHRzJnBfc2VhcmNoX3R5cGU9NyZwX3Byb2RfbHZsMT1_YW55fiZwX3Byb2RfbHZsMj1_YW55fiZwX3NvcnRfYnk9ZGZsdCZwX3BhZ2U9MQ**&p_li=
So as a summary:
- Lee Revell said changing preemption model from server to voluntary or
preemption could help
- increasing HZ on the vm-host, decreasing in the vm-clients should
help, according to VMware support
It would be good if this information is spread on the support lists, I
saw that question a lot. Also, a short text under Documentation in the
kernel source could be nice, explaining why this happens and what to do
then.
I will try the suggestion from the vmware support link I posted above,
and will report back.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660/4156531 .network.your.ideas.
// PGP Key: "lynx -source http://zmi.at/zmi3.asc | gpg --import"
// Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE
// Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-21 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 20:37 rtc: lost some interrupts at 256Hz Michael Monnerie
2006-04-20 20:57 ` linux-os (Dick Johnson)
2006-04-20 21:03 ` Lee Revell
2006-04-20 22:18 ` Florian Schmidt
2006-04-20 22:18 ` Jan Engelhardt
2006-04-20 22:22 ` Lee Revell
2006-04-21 8:52 ` Michael Monnerie [this message]
2006-04-25 10:32 ` Michael Monnerie
2006-05-07 17:59 ` Lee Revell
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=200604211052.59498@zmi.at \
--to=michael.monnerie@it-management.at \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=rlrevell@joe-job.com \
/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