From: Mike Mattie <codermattie@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: recomended way to check longest period that interupts are disabled ?
Date: Thu, 26 Apr 2007 02:13:50 -0700 [thread overview]
Message-ID: <20070426021350.29ddfa0a@reforged> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hello,
I am still struggling to track down problems with audio playback. I get intermittent:
Apr 26 02:01:40 reforged [13230.947879] cannot submit sync urb (err = -45)
I have tackled the scheduler issues to where I really don't think the
driver is being starved at all. I am running audacious like so:
schedtool -R -p 50 -n 1 -e audacious
At this point the strongest correlation I can get is that starting
programs seems to trigger the stutter. I have suspected IO for
some time.
My system image , / & /usr are on a libata (VIA PATA) driver.
I have disabled the write-cache , but I also have noatime set
on mount, for /usr
My big suspicion is that one of my drivers, likely IO is
disabling interrupts for too long.
I have looked but not found a tool for measuring the longest
period interrupts are disabled and pointing the finger at
the culprit, could anyone on this list recommend tools that
might help me pinpoint what is going on ?
I would also be delighted for any sort of recommended latency
testing tools.
pin-pointing this is going to be a "learning experience" but
every time I think I am about to have a bonding moment with
the kernel audio skips; I am highly motivated.
Cheers,
Mike Mattie - codermattie@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-04-26 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 9:13 Mike Mattie [this message]
2007-04-26 9:53 ` recomended way to check longest period that interupts are disabled ? Peter Zijlstra
[not found] ` <20070426040252.3f4fa8cc@reforged>
[not found] ` <1177585912.6815.6.camel@twins>
2007-04-26 12:19 ` Mike Mattie
2007-04-26 17:15 ` Thomas Gleixner
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=20070426021350.29ddfa0a@reforged \
--to=codermattie@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox