On Mon, 2003-06-02 at 03:36, Ingo Molnar wrote:
> On Sat, 31 May 2003, Andrew Morton wrote:
> > > [...] Upon looking a little further it
> > > seemed that the kernel was dynamically boosting the priority of the
> > > process much higher than it probably should be, in the end, not leaving
> > > enough CPU for playing the sounds without skipping.
> > Yes, it seems that too many real-world applications are accidentally
> > triggering this problem.
> no, the problem is exactly the opposite. Here's the key observation:
> > the problem seemed to be caused by the fact that the pluginserver (wine)
> > was using 100% of the CPU. I simply reniced this process to -10 and
> > everything started working fine.
> the kernel has detected this process to be a CPU-hog - and indeed the
> traces and the above description all say that it really is a CPU hog.
> by renicing it to -10 it gets super-attention from the scheduler, so it
> can be a CPU hog _and_ create sound.
Sorry, this is my fault, I'm actually renicing the process to '10' not
'-10' that's a typo. I tested this again this morning to make sure.
I'm renicing this as a regular user, I don't think that a regular user
is allowed to renice to a negative value.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:16 EST