Bug#498328: linux-image-2.6.26-1-amd64: nice is not "fair": mouse jumps and chars repeated in terminal
Bastian Blank wrote:
On Tue, Sep 23, 2008 at 12:24:46PM +0200, Sandro Tosi wrote:
On Tue, Sep 23, 2008 at 12:18, Havis <juraj.kvasnica@gmail.com> wrote:
Hi, I have same problems like you.
I have Debian Lenny with 2.6.26-1-686 kernel
I have been running boinc for a long time
and these issues appeard on my PC after
I started using kernels with CFS scheduler (2.6.24+)
So the problem exists with .24, .25 and .26? The Debian packages changed
the behavour of the scheduler decisions several times with the group
scheduler.
I noticed the problem first with .24+ kernels and even more when I
started to use pulseadio...
Audio was really skippy and whole system was very very unresponsive...
(but this is probably pulseaudio's bug, because it used 25-30%CPU on my
2.8GHz P4, while plaing any audio throu it.)
So I removed pulseadio, and sound is much better now (not skippy ;-))
I also enabled HyperThreading in BIOS and started searching again
where the problem could be...
The problem with repeating chars in terminal and other apps was
still occuring almost for every word I tried to write, so I removed
schedtool(Version: 1.2.10-1), as it was used to run BOINC with +19 and
SCHED_IDLEPRIO on my system and restarted BOINC (it's running with +19
Nice priority)...
I still have the problem with repeating chars in terminal or apps
but its occurance is really low...
with 2.6.26 I thought that my keyboard was broken, because when I
switched from X to terminal my arrow keys stopped working...
but later I found that it was this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497817
...so far I can't explain why the repeating char problem occurs,
sometimes it won't appear for 10 minutes and then
when I run gnome-terminal and try to run ls, I get output like this:
#lssssssssssssssssssssssssssssssssss
nevertheless it's much better now, then with pulseaduio and schedtool
...at least I can code, listen to the music and run BOINC at the same
time ;-)
Juraj
A solution for me was to turn off HyperThreading in BIOS.
If it is a real problem in the HT scheduler then we are off luck.
I think that -nice 19 processes have too high priority
and that -nice 19 behavior should be changed
so that these tasks get only _free_ (not used) CPU clocks.
No, the behaviour of niceness 19 is unchanged in years. You speak about
idle priority which also exists but is not accessible by the normal user
because of possible priority inversions.
Bastian
Reply to: