2009-01-08, 04:23
I would point out, again, that I am NOT seeing this issue so before you decide it's the scheduler you might want to take into account that I am running the SAME scheduler without this issue. If this were the kernel wouldn't I be seeing this too?