From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: linux-rt-users@vger.kernel.org, Victor henri <nadaeck@hotmail.com>
Subject: Re: disk thread problem when using RT-kernel
Date: Mon, 31 Jan 2011 09:23:46 -0200 [thread overview]
Message-ID: <20110131112346.GD10900@uudg.org> (raw)
In-Reply-To: <SNT110-W222DEC20897CB3D9F79E20A8E00@phx.gbl>
On Sat, Jan 29, 2011 at 10:41:47PM +0100, Victor henri wrote:
...
| Here are some technical details:
| - I have laptop Asus Core i7 for gamers (supposed to be very fast);to
| be noted : it also happens on another Asus Core I7, but NOT on an another
| Asus Core i3; 4Go RAM;
Have you tried running hwlat_detector? You (hopefully) can find it in your
kernel sources and notes on how to use it at Documentation/hwlat_detector.txt.
In short, you could be seeing long latencies spikes created by SMIs. That kernel
module, hwlat_detector, may help you identifying them.
The hint about setting the priority of the IRQ threads is also a good one.
You should also look at the logs of the USB/firewire/whatever you are using
to commounicate with your keyboard... you may be suffering buffer underruns
due to file size or something similar to it.
Luis
--
[ Luis Claudio R. Goncalves Bass - Gospel - RT ]
[ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ]
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-31 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 21:41 disk thread problem when using RT-kernel Victor henri
2011-01-31 10:32 ` Daniel James
2011-01-31 10:37 ` Daniel James
2011-01-31 11:23 ` Luis Claudio R. Goncalves [this message]
2011-01-31 14:16 ` Victor henri
2011-01-31 15:17 ` Luis Claudio R. Goncalves
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 20:50 Victor henri
2011-02-03 21:02 ` Nathan Grennan
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=20110131112346.GD10900@uudg.org \
--to=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nadaeck@hotmail.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 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.