From: Lee Revell <rlrevell@joe-job.com>
To: Michael Monnerie <michael.monnerie@it-management.at>
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: Sun, 07 May 2006 13:59:28 -0400 [thread overview]
Message-ID: <1147024769.15364.260.camel@mindpipe> (raw)
In-Reply-To: <200604251232.37939@zmi.at>
On Tue, 2006-04-25 at 12:32 +0200, Michael Monnerie wrote:
> Still, some kind of documentation in the Linux source tree would be
> nice, explaining what that message means and how to fix it.
>
It means exactly what the printk says:
"Your time source seems to be instable or
some driver is hogging interupts"
Lee
prev parent reply other threads:[~2006-05-07 17:59 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
2006-04-25 10:32 ` Michael Monnerie
2006-05-07 17:59 ` Lee Revell [this message]
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=1147024769.15364.260.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=michael.monnerie@it-management.at \
/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