From owner-freebsd-hackers Tue Jun 6 04:31:45 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA15980 for hackers-outgoing; Tue, 6 Jun 1995 04:31:45 -0700 Received: from orion.stars.sed.monmouth.army.mil ([158.9.11.65]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA15974 ; Tue, 6 Jun 1995 04:31:41 -0700 Message-Id: <199506061131.EAA15974@freefall.cdrom.com> Received: by orion.stars.sed.monmouth.army.mil (1.37.109.16/16.2) id AA015058102; Tue, 6 Jun 1995 07:28:22 -0400 From: william pechter ILEX Subject: Re: 2.0.5-A: Very disheartening? To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Tue, 6 Jun 1995 07:28:22 -0400 (EDT) Cc: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) In-Reply-To: <28172.802415540@freefall.cdrom.com> from "Jordan K. Hubbard" at Jun 5, 95 10:12:20 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 823 Sender: hackers-owner@freebsd.org Precedence: bulk > > > Once 2.0.5-Alpha is installed and running on a non-compressed kernel, I can > > put the cache back in (or enable it) and everything still works, even with > > memory amounts that would panic or hang with the cache present. On the Micronics Gemini Baby AT 486 motherboard the kernel reboots automatically just as it prints the string that shows its entry point. This problem seems to have been there since the 2.0-Release. If it boots from the install floppy it's ok. It doesn't even get to kernel configuration with the -c option. Bill ----------------------------------------------------------------------------- Bill Pechter |Systems Administrator | N2RDI Ilex Systems |170 Patterson Ave | Shrewsbury, New Jersey 07702 908-532-2369 |pechter@sesd.ilex.com | pechter@stars.sed.monmouth.army.mil