On 2019-10-28 11:22:58 [-0700], Davidlohr Bueso wrote: > Hi, Hi, > I've been running into rcu self-stalls as soon as I start running > the pi_stress program on a v5.2.21-rt13 kernel - I've seen it on > older rt 5.2 versions as well so it's not specific to 954ad80c23e > (futex: Make the futex_hash_bucket spinlock_t again and bring back > its old state), for example. > > No other workload is running on the machine. The workload does not > crash, but incurs in very long response times. > > I'm attaching two different splats I'm seeing for the futex wait > and wake paths. Does this ring any bells? On 8-CPU system here I have: |Starting PI Stress Test |Number of thread groups: 7 |Duration of test run: infinite |Number of inversions per group: unlimited | Admin thread SCHED_FIFO priority 4 |7 groups of 3 threads will be created | High thread SCHED_FIFO priority 3 | Med thread SCHED_FIFO priority 2 | Low thread SCHED_FIFO priority 1 |Current Inversions: 199678139 without any RCU-stalls. The system is slow but then the test kind of asked for it… I see *only* the workqueue stalls which is hardly any news since the system is busy on almost every CPU with RT tasks and the workqueue is not of RT prio so, yes. That means you might not have RCU-boost enabled. CPU0 goes sometimes idle and hardly has any RT-task. CPU1-7 almost never see idle and are busy scheduling/running RT-tasks. > Thanks, > Davidlohr Sebastian
