From: Chris Snook <csnook@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: Lossy interrupts on x86_64
Date: Thu, 13 Sep 2007 09:40:44 -0400 [thread overview]
Message-ID: <46E93DDC.7090207@redhat.com> (raw)
In-Reply-To: <200709120833.15980.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> I just narrowed down a weird problem where I was losing more than 50% of
> my vblank interrupts to what seems to be the hires timers patch. Stock
> 2.6.23-rc5 works fine, but the latest (171) kernel from rawhide drops
> most of my interrupts unless I also have another interrupt source
> running (e.g. if I hold down a key or move the mouse I get the expected
> number of vblank interrupts, otherwise I get between 3 and 30 instead
> of the expected 60 per second).
>
> Any ideas? It seems like it might be bad APIC programming, but I
> haven't gone through those mods to look for suspects...
What happens if you boot with 'noapic' or 'pci=nomsi'? Please post dmesg as
well so we can see how the kernel is initializing the relevant hardware.
-- Chris
next prev parent reply other threads:[~2007-09-13 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 15:33 Lossy interrupts on x86_64 Jesse Barnes
2007-09-12 16:01 ` Randy Dunlap
2007-09-12 16:29 ` Jesse Barnes
2007-09-12 17:06 ` Thomas Gleixner
2007-09-17 19:13 ` Jesse Barnes
2007-09-17 19:18 ` Thomas Gleixner
2007-09-17 19:40 ` Jesse Barnes
2007-09-20 19:22 ` Jesse Barnes
2007-09-20 19:50 ` Thomas Gleixner
2007-09-21 0:40 ` Jesse Barnes
2007-09-14 17:35 ` Chuck Ebbert
2007-09-13 13:40 ` Chris Snook [this message]
2007-09-17 19:24 ` Jesse Barnes
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=46E93DDC.7090207@redhat.com \
--to=csnook@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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