From owner-freebsd-hardware Sun Oct 15 12:27:27 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA06166 for hardware-outgoing; Sun, 15 Oct 1995 12:27:27 -0700 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA06161 for ; Sun, 15 Oct 1995 12:27:22 -0700 Received: by Sysiphos id AA27823 (5.67b/IDA-1.5 for hardware@freebsd.org); Sun, 15 Oct 1995 20:23:45 +0100 Message-Id: <199510151923.AA27823@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 15 Oct 1995 20:23:44 +0100 In-Reply-To: Pete Kruckenberg "Memory upgrade problems w/ 2.0.5R" (Oct 14, 12:39) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Pete Kruckenberg Subject: Re: Memory upgrade problems w/ 2.0.5R Cc: hardware@freebsd.org, hackers@freefall.freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Oct 14, 12:39, Pete Kruckenberg wrote: } Subject: Memory upgrade problems w/ 2.0.5R } Last night, I attempted to upgrade my FreeBSD 2.0.5R news/Web server from } 64 to 96MB. It ended in slight disaster. I wanted to find out if I missed } something critical, or if one or both of my SIMMs might have been bad. } } Here's what I did: } } modified my conf file with 'options MEMMAX="98304"', then rebuilt the } kernel } when building the kernel, I use optimizations (gcc 2.6.3): } -O2 -m486 -fomit-frame-pointer -pipe Hmm, is "-fomit-frame-pointer" legal when compiling the kernel ??? Maybe something depends on the stack always being in "standard" format ? -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html