From: Lee Revell <rlrevell@joe-job.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rc5-rt3 - `IRQ 8'[798] is being piggy
Date: Fri, 21 Oct 2005 19:28:37 -0400 [thread overview]
Message-ID: <1129937318.4724.6.camel@mindpipe> (raw)
In-Reply-To: <5bdc1c8b0510211525v62212d33j84491cfc687bd200@mail.gmail.com>
On Fri, 2005-10-21 at 15:25 -0700, Mark Knecht wrote:
> >
> > No I don't think so. CONFIG_RTC_HISTOGRAM is a hack, designed to work
> > with a specific test program that runs SCHED_FIFO and poll()s on the
> > RTC. VLC apparently poll()s on the RTC but does not run SCHED_FIFO. So
> > of course there will be delays.
> Lee,
> Indeed, you are correct. Apparently under character devices I had
> turned on the RTC histogram feature. With that off I am not only
> getting the maximum latency values we expect.
>
> Now I'll have to let it run for hours/days to see if I catch any
> info on these xruns, should I get another rash of them. Yesterday they
> came only after about 14 hours of work. I had none the previous two
> days.
In general you should avoid enabling/disabling random config options
between runs. If you keep changing the .config it makes it impossible
to hunt bugs or compare one set of results to another.
The easiest way is to do:
zcat /proc/config.gz > .config
make oldconfig
Lee
next prev parent reply other threads:[~2005-10-21 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 17:03 2.6.14-rc5-rt3 - `IRQ 8'[798] is being piggy Mark Knecht
2005-10-21 17:40 ` Mark Knecht
2005-10-21 18:45 ` Lee Revell
2005-10-21 18:52 ` Mark Knecht
2005-10-21 19:44 ` Lee Revell
2005-10-21 22:25 ` Mark Knecht
2005-10-21 23:28 ` Lee Revell [this message]
2005-10-22 3:44 ` Ingo Molnar
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=1129937318.4724.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).