honx

No, sorry, because the project went a different way. Well not yet, actually, it may be that this gets implemented at a later time. If we do create something I'll...

I cleaned up my debug logging a bit. Here is a gist: https://gist.github.com/honx/525e27b360576f3c5fa11ca26bffa918

I found a possible one-line fix and created the above PR. This fixes my problem and should also leave the behaviour of global and org scope runners unchanged. However, to...

I did some more testing and repo runners still don't behave correctly. I'll do more debugging and report back. The fix i put in the PR does not seem sufficient.

I closed the PR since i cannot say that the fix is actually correct. I debugged a bit more but I need further information before i can continue. I am...

Seems like the DB entries were wrong and "ownerID = 0 and repoID = " is the correct format for repo scope runners. Since i currently cannot reproduce the behaviour...

> cat /sys/kernel/debug/dmaengine/summary I'm a colleague of @kraln On the non-working 6.6.51+rpt-rpi-2712 we get: dma0 (1000010000.dma): number of channels: 5 dma1 (1000010600.dma): number of channels: 5 dma1chan0 | 107d004000.spi:tx dma1chan1...

quick update: yes, the above dmaengine/summary output is the correct way around. however, it seems our issue was only triggered by disabling DMA but looking at the traces, it seems...

> quick update: yes, the above dmaengine/summary output is the correct way around. > > however, it seems our issue was only triggered by disabling DMA but looking at the...