Re: Help:General protection fault in Linux?????? (It's the swap!)

["Jose M. Sanchez" <opjose ex-pressnet com>]

-----Original Message-----
From: Alexander Woodby <awoodby tir com>
To: Jose M. Sanchez <opjose ex-pressnet com>
Cc: redhat-install-list redhat com <redhat-install-list redhat com>;
redhat-list redhat com <redhat-list redhat com>
Date: Thursday, October 29, 1998 12:06 PM
Subject: Re: Help:General protection fault in Linux??????


>Well, the computer doesn't even come up any more, just halts on the POST
>with
>CMOS checksum error - Defaults loaded
>

This is more than likely caused by the original problem. Apps were probably
erringly writing to wrong memory regions finally erasing the CMOS...

>look below, something wierd here?
>I CAN make it come up with F1, the results of Free show
>


Set the CMOS data before anything else, or else the bios will report the
wrong info to Linux...

>Mem: 64108 62824 1284 18924 45460 6136
>-/+ buffers/cache:11228 52880
>Swap: 130748 0 130748

Ok so you have 64Megs of physical RAM linux knows about and 128Megs of swap
space....
>
>I have 1 128meg sdram in this computer (but don't have the
>append="mem=128M" in lilo.conf, am adding that now...)
>

I have had problems with Linux, on systems using a single SDRAM strip when
the OS was unaware of the full ram amount... the 128m line might be enough
to cure the problem.... eh, no, I just saw the message below...

---

>fstab has...
>/dev/sda1 / ext2 defaults 1 1
>/dev/sda2 /var ext2 defaults 1 2
>/dev/sda3 /web ext2 defaults 1 2
>/dev/sda4 swap swap defaults 0 0
>/dev/fd0 /mnt/floppy ext2 noauto 0 0
>/dev/cdrom /mnt/cdrom iso9660 noauto,ro 0 0
>none /proc proc defaults 0 0
>
>
>and fdisk shows...
>
>/dev/sda1 * 1 1 64 514048+ 83 Linux native
>/dev/sda2 65 65 128 514080 83 Linux native
>/dev/sda3 129 129 500 2988090 83 Linux native
>/dev/sda4 501 501 554 433755 82 Linux swap
>
>It doesn't look to me that swap is on?  What did I miss?  Shouldn't I
>have 433755 megs of swap space, not 130?
>


You mean 4xx megs, but you are right, the 130 is incorrect, the swap file
size is misreported. Bring the unit up in single user mode and run fdisk
again... something is definitely wrong with the swap file...

-JMS