The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Wichert Akkerman <wichert@wiggy.net>
To: linux-kernel@vger.kernel.org
Cc: p_gortmaker@yahoo.com, pavel@suse.cz
Subject: rtc misses interrupts after resume
Date: Tue, 15 Mar 2005 23:00:31 +0100	[thread overview]
Message-ID: <20050315220031.GD29715@wiggy.net> (raw)

I recently upgraded my laptop to 2.6.11.3 and removed the notsc boot
option I added a fairly long time ago to see if things worked properly
without it now. It seems to work, except that after a resume I get
an awful lot of these messages:

Mar 15 09:53:04 typhoon kernel: rtc: lost some interrupts at 1024Hz.
Mar 15 09:53:06 typhoon last message repeated 103 times

and indeed looking at /proc/interrupts interrupt 8 is not getting hit.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

             reply	other threads:[~2005-03-15 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 22:00 Wichert Akkerman [this message]
2005-03-15 22:07 ` rtc misses interrupts after resume Pavel Machek

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=20050315220031.GD29715@wiggy.net \
    --to=wichert@wiggy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p_gortmaker@yahoo.com \
    --cc=pavel@suse.cz \
    /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