re: elevator=as, or actually gpm doesn't get time from scheduler???

From: Antti Lankila
Date: Mon Apr 19 2004 - 08:14:29 EST

In response to Nick Piggin's:

> The only other problems I can think of that you might be
> having are chipset problems, or CPU scheduler problems.
> Which reminds me, do you have your X server at nice 0?

X has been reniced to zero. But hey! I was doing "cat /dev/psaux" when mouse
stopped moving in X, and I _did_ see data coming from /dev/psaux! So this is
a major update to my understanding of the problem.

But make no mistake, I have been doing this cat /dev/psaux test earlier and
at that time I did _not_ see chars coming out of psaux when the mouse
stopped. That is why I thought I had established that the problem is in the
kernel. I must retest this on the other machines involved when I get to
their consoles next week. I can not explain why this time psaux appears to
work regardless of the userland mouse stall, so for now I must assume some
other factor confused the cat /dev/psaux test at that time.

My X reads gpmdata, so perhaps that's the problem? I now undercut gpm in
order to examine the situation, and my system behaves _perfectly_ as far as
I can see. The mouse issues are all gone. (gpm is still running in the
background, X just reads psaux directly. As I have understood, this is
possible in 2.6 while in 2.4 it caused a problem for multiple readers.)

I progress from now by removing gpm on all my systems. There's still the
issue what gpm (or maybe kernel's scheduler) is doing wrong, I suppose.
Nevertheless, gpm is virtually useless for me and has so far caused far more
grief than its utility has ever been worth.

I'm sorry for having wasted your time with this.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at