On 2018-08-31 18:30:19 [-0500], Julia Cartwright wrote: > On Fri, Aug 31, 2018 at 06:31:52PM +0200, Sebastian Andrzej Siewior wrote: > > On 2018-08-31 01:18:20 [-0700], Ramesh Thomas wrote: > [..] > > > 2. Timer is armed even though only a single high priority task is running. > > > > something must have armed that timer. The clock_nanosleep() API won't > > use those new threads but for instance timer_create() / timer_settime() > > will. > > Did we actually ever solve the "ktimersoftd uselessly woken on every > tick" problem? I think so, yes. According to the report the problem does not happen the first invocation. However the "ktimersoftd uselessly woken on every tick" problem occurred "always". > Julia Sebastian
