> somehow? Maybe I should try and see if the problem persists with the> ULE scheduler? No difference with ULE, with the default parameters: kern.sched.name: ulekern.sched.slice_min: 10kern.sched.slice_max: 142kern.sched.preemption: 1 mkb.