Hi,
Done that the problem still persists
I get errors like "LRU list corrupted" or "free list corrupted".
                    Rajiv



From: [EMAIL PROTECTED] (Ajit; Kumar (IE10)) AT internet on 12/31/99
      02:37 AM CST

To:   Rajiv Gangadharan/IN/ALLTELCORP
cc:

Subject:  RE: (LI) problem with kswapd


Try keeping the size of the swap space = multiples of RAM size

Ajit
----------------------------------------------------------------------------
-------------------------
Best way to learn Linux is to put comments in the source code
___________________________________________________

> -----Original Message-----
> From:     Rajiv Gangadharan [SMTP:[EMAIL PROTECTED]]
> Sent:     Thursday, December 30, 1999 10:12 PM
> To:     [EMAIL PROTECTED]
> Subject:     [LI] problem with kswapd
>
>
>
>        Hi,
>        I run a pc with Red Hat linux 6.1. I recently upgraded my hard
>        disk from 2.1 GB to 4 GB .
>        My problem is when ever I try to compile the kernel or and such
>        activity like compiling
>        large executables the kernel panics. The kswapd daemon dies.
>        The error messages are like cannot address memory location ...
>        I have 48 MB RAM with a 64 MB swap.
>        I got a different error message each time so I could not trace
>        a particular module.
>        But all the messages invariably pointed to either the kswapd
>        daemon or dome memory
>        allocation problem.
>        Can any body suggest what might be the problem??
>                                                 Rajiv
> --------------------------------------------------------------------
> The Linux India Mailing List Archives are now available.  Please search
> the archive at http://lists.linux-india.org/ before posting your question
> to avoid repetition and save bandwidth.







 
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available.  Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.

Reply via email to