Re: highmem=system killer, 2.2.17=performance killer ?

[Klaus Meyer <k.meyer@m3its.de>]

Hi all,

thank you very much for your convenience and effort.
I've now located the real reason for all my problems.

It was just a bad memory modul. Believe me, i'd tested them before
carefully.
But i had to learn that even ECC-modules installed in brand motherboards
dont tell you that they are not working correctly.

After trying all new kernel versions and patches i was really
desperated.
All the discussions in the LKLM concerning the new vm +swap
frustated me since i was really thinking that the stable kernel tree is
not really stable.
I'm a user of linux since 0.99pl2 so this would have been a new
experience to me.

All in all i'm still wondering that the system was working anyway.
So finding the real error was just inspiration and luck.

Thanx for all hints

	Klaus

Stephan von Krawczynski wrote:
> 
> On Tue, 15 Jan 2002 17:42:36 +0100
> Klaus Meyer <k.meyer@m3its.de> wrote:
> 
> > As I just took a look on the output of cat /proc/meminfo i got the idea
> > that i'll increase the pysical swap space. (136M before that means >
> > highmem).
> > astonishing (using Suse kernel 2.4.16): after an increase to 2GB swap
> > and
> > using 1,5GB of mem the system runs quit a longer time with a good
> > performance,
> > but starting the copy process leads also to a slow down of the machine.
> > Finally i could see that kupdated is suffering.
> 
> I was already tempted to suggest you turn off swap completely, as 136 MB in a 2
> GB box are somehow useless anyways. I know, I have the same setup (256MB swap).
> As this could work without boot, willing to give it a try? Anyway I would very
> much suggest to use -pre3.
> 
> Regards,
> Stephan