* Mark Knecht <[email protected]> wrote:
> What I'm seeing is that when using basic menus, or when watching
> videos I get no xruns. However, if I'm in the preview menu I get an
> xrun every few minutes. [...]
this could be some sort of hardware latency, as Lee suspects. Videocards
are known to be pretty agressively holding the system bus, for the last
few percentiles of Quake performance ... Also, mainboard chipsets are
sometimes not that good at enforcing fairness between DMA agents -
possibly starving the CPU itself for lengthly amounts of time. We have
seen such incidents before, and latency tracing ought to be able to show
this with reasonable certainty. If it's some sort of generic hardware
latency then you ought to see weird traces when enabling WAKEUP_TIMING
and LATENCY_TRACING in the .config. No need for any other debug options
or Jack level hackery at this point - just enable these and do a:
echo 0 > /proc/sys/kernel/preempt_max_latency
and try to trigger as large latencies as possible via MythTV. (you wont
necessarily see a large latency reported by the kernel when you see an
xrun. We can trace xruns too, but that needs Jackd changes and is more
effort to set up.)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]