O18.1int problems

O18.1int problems

[Joonas Koivunen]

Hi,

after reading some mails and discussion about Con Kolivas' patches I decided 
to give a try. Got latest (-test4) vanilla and applied patch-test4-O18.1int. 
Desktop (kde pre 3.2) runs smoother than with vanilla 2.6.0-test3.

But when I tried to recompile my kde sources (first updating from cvs) 
starting with rebuilding makefile templates (make -f Makefile.cvs) (some 
autoconf/automake stuff, don't really know :) it froze. In Konsole window I 
tried ctrl-c, ctrl-d, no effect. A brief ps aux | grep make shows that make 
is in D state and so is it's find task. This D state didn't clear in 24 
houres and I seem to be unable of reproducing it under vanilla 2.6.0-test4. 
Killing of those processes didn't work (though I'm not sure if it should kill 
those instantly).

Is this problem with my configuration or some sneaky bug? System had been up 
some time (24-48 houres) so I'll try reproducing it later also.

-rzei

Re: O18.1int problems

[Con Kolivas]

On Mon, 1 Sep 2003 07:12, Joonas Koivunen wrote:
> Hi,
>
> after reading some mails and discussion about Con Kolivas' patches I
> decided to give a try. Got latest (-test4) vanilla and applied
> patch-test4-O18.1int. Desktop (kde pre 3.2) runs smoother than with vanilla
> 2.6.0-test3.

Great thanks for feedback.

> But when I tried to recompile my kde sources (first updating from cvs)
> starting with rebuilding makefile templates (make -f Makefile.cvs) (some
> autoconf/automake stuff, don't really know :) it froze. In Konsole window I
> tried ctrl-c, ctrl-d, no effect. A brief ps aux | grep make shows that make
> is in D state and so is it's find task. This D state didn't clear in 24
> houres and I seem to be unable of reproducing it under vanilla 2.6.0-test4.
> Killing of those processes didn't work (though I'm not sure if it should
> kill those instantly).
>
> Is this problem with my configuration or some sneaky bug? System had been
> up some time (24-48 houres) so I'll try reproducing it later also.

Please look further into it for something else sneaky. There is nothing in the 
O1int patch logic that says put this state into D forever.

Cheers,
Con