Am 05/10/2022 um 16:45 schrieb Daniel Bristot de Oliveira:
On 10/5/22 15:31, Sebastian Andrzej Siewior wrote:
On 2022-10-05 09:46:30 [+0200], Florian Paul Schmidt wrote:
5.19-rt10 has the problem
5.17.1-rt17 has the problem
5.16.2-rt19 does not have the problem
Could you check v5.17-rc1-rt1? Maybe it was introduced in v5.17 cycle.
I would possibly be willing to git bisect the issue. But I am a little
bit confused about how to go about that. What repo/tree would I
precisely bisect (I am using the the patch tarballs from
https://cdn.kernel.org/pub/linux/kernel/projects/rt/)?
if it got introduced post v5.17-rc1-rt1 then we could try to bisect it.
Otherwise we would have to trace it. Since the latency spike is huge, it
should be easy to spot.
try:
# timerlat -a 100
wait for it to stop and save the trace. Then see what the trace points out at the
end of the trace.
What package contains the timerlat command? I gathered from searching
online for timerlat that it is part of the tracing machinery but I
didn't find the executable itself..
Kind regards,
FPS
