From owner-freebsd-questions Thu Nov 20 16:00:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22041 for questions-outgoing; Thu, 20 Nov 1997 16:00:27 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from ultra.ultra.net.au (chaos@ultra.ultra.net.au [203.20.237.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22025 for ; Thu, 20 Nov 1997 16:00:21 -0800 (PST) (envelope-from chaos@ultra.net.au) Received: from localhost (chaos@localhost) by ultra.ultra.net.au (8.8.8/8.8.8) with SMTP id KAA06437; Fri, 21 Nov 1997 10:00:20 +1000 (EST) Date: Fri, 21 Nov 1997 10:00:19 +1000 (EST) From: Simon Coggins To: John Kelly cc: questions@freebsd.org Subject: Re: 2.2.5 Boot Floppy and Kernel Panic In-Reply-To: <3475ced7.3953995@smtp-gw01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, John Kelly wrote: > On Fri, 21 Nov 1997 07:37:42 +1000 (EST), Simon Coggins > wrote: > > >RAM: 64 Meg of ram in 4x16 EDO > > > >What gets me is the 2.2.2 boot disk still works fine.. Just not 2.2.5 :/ > > > >>> fatal trap 9 general protection fault while in kernel > > 64 meg of RAM? > > Sounds like the problem I reported a while back in 2.2.5 -- the one > where it used to be (in 2.2.2) 48 meg of RAM showing the problem. > > Try removing a SIMM to leave 48 meg and then boot the old 2.2.2 > floppy. If it fails at 48 meg with the "double fault" panic, then you > have the old slippery 48 meg bug. > > Then you can load 2.2.5 -- it will boot with 48 meg. I'll try this.. But first thing i did was remove 2 simms and droped it to 32 meg of ram.. 2.2.5 still paniced.. *stumped* Regards Simon