From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Daniel Paquet <daniel.paquet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Again the rtc: lost some interrupts at 1024Hz
Date: Fri, 17 Aug 2007 15:30:33 +0300 [thread overview]
Message-ID: <46C594E9.4090908@qumranet.com> (raw)
In-Reply-To: <9a1a10a40708150655n1a76962k6494be724b12017b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Daniel Paquet wrote:
> Well im still playing with this darn error, and in fact I am even
> starting to think that this is my cause of kicker crash. Im getting my
> logs filled with
> rtc: lost some interrupts at 1024Hz when I sed the max freq to 1024 as
> per request of kvm when I start it.
>
> Im running debian Lenny and a vanilla kernel 2.6.23-rc3 with no patch.
>
> I may miss some information since im not a dev, so let me know if you
> need more information, or maybe if I should RTFM ;) but I alread did
> alot of search on google for this, and it has not been very
> successfull...
>
I think there's some RTC emulation feature you need... try setting
CONFIG_HPET_EMULATE_RTC=y. But I'm not 100% sure.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-17 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 13:55 Again the rtc: lost some interrupts at 1024Hz Daniel Paquet
[not found] ` <9a1a10a40708150655n1a76962k6494be724b12017b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-17 12:30 ` Avi Kivity [this message]
[not found] ` <46C594E9.4090908-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-17 12:31 ` Daniel Paquet
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=46C594E9.4090908@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=daniel.paquet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.