Hi,
I get
Code: Select all
sudo hwlatdetect --duration=10
hwlatdetect: test duration 10 seconds
detector: tracer
parameters:
Latency threshold: 10us
Sample window: 1000000us
Sample width: 500000us
Non-sampling period: 500000us
Output File: None
Starting test
test finished
Max Latency: 22us
Samples recorded: 10
Samples exceeding threshold: 10
ts: 1559420907.061897788, inner:19, outer:22
ts: 1559420908.090908167, inner:14, outer:14
ts: 1559420909.104236691, inner:17, outer:17
ts: 1559420910.117565292, inner:15, outer:14
ts: 1559420911.130945201, inner:16, outer:17
ts: 1559420912.144232982, inner:0, outer:14
ts: 1559420913.157591537, inner:16, outer:16
ts: 1559420914.174234547, inner:14, outer:15
ts: 1559420915.184247384, inner:14, outer:14
ts: 1559420916.197586449, inner:14, outer:15
[ag@agantergos ~]$
I have gotten cyclictest to work (with smi), too:
Code: Select all
sudo cyclictest -m -Sp98 -i100 -d0 --smi
[sudo]
# /dev/cpu_dma_latency set to 0us
policy: fifo: loadavg: 1.70 1.59 1.38 2/591 7902
T: 0 ( 7897) P:98 I:100 C: 222798 Min: 1 Act: 3 Avg: 3 Max: 19 SMI: 0
T: 1 ( 7898) P:98 I:100 C: 222746 Min: 1 Act: 6 Avg: 3 Max: 19 SMI: 0
T: 2 ( 7899) P:98 I:100 C: 222677 Min: 1 Act: 3 Avg: 3 Max: 22 SMI: 0
T: 3 ( 7900) P:98 I:100 C: 222642 Min: 1 Act: 3 Avg: 3 Max: 23 SMI: 0
I had the hwlatdetect once running and got no latencies (all below threshold). All other tests were about like the one above.
It is now late in the evening here in Germany. I have not used my computer for some hours, and the battery is fully charged (and charging is over for some hours, too).
When I run my stresstest-project, I get no xruns, whereas I do get xruns with that project both when running on battery and when charging and when fully charged, but not cooled down (like: short after charging).
So I conclude:
- my system is not as reliable as yours, maybe due to the power-saving processor
- I have a thermal problem
Is there a way to track down where the latencies come from?
Thanks for your patience,
Andreas