From owner-freebsd-questions Thu Mar 18 2:19:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hal6000.thp.Uni-Duisburg.DE (hal6000.uni-duisburg.de [134.91.140.2]) by hub.freebsd.org (Postfix) with ESMTP id 4C2A3153A5; Thu, 18 Mar 1999 02:19:37 -0800 (PST) (envelope-from ralf@thp.Uni-Duisburg.DE) Received: from localhost (ralf@localhost) by hal6000.thp.Uni-Duisburg.DE (8.9.0/8.9.0) with ESMTP id LAA151246; Thu, 18 Mar 1999 11:15:46 +0100 Date: Thu, 18 Mar 1999 11:15:46 +0100 (MEZ) From: Ralf Meyer To: flygt@sr.se, patseal@hyperhost.net, grog@lemis.com, nadas@raleigh.ibm.com, alexandr@mail.eecis.udel.edu, sos@freebsd.dk Cc: freebsd-questions@FreeBSD.org, freebsd-mobile@FreeBSD.org Subject: Re: System freezes on reboot (solved) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again, the problem is solved. Many thanks to all people who answered to my posting. Following Steve's suggestions I noticed carefully the amount of memory tested by the BIOS. In my case this is 130496 kB which is smaller than the physical memory size by the same amount Steve reports (576 kB). After putting MAXMEM=130496 into the kernel configuration file the problem did not show up again (Jerry's solution of subtracting 1 MB should therefore also work as well as my solution of leaving out 32 MB). I think that such a difference between the physical size of memory and the really available size is not uncommon. I would think that this is caused by the fact that some parts of the address space are mapped to ROM and devices thereby hiding some parts of the RAM. What is really wrong is that (without a MAXMEM statement) the size of the usable RAM is not correctly determined by FreeBSD. Since this obviously works on other machines (also hiding a part of the RAM) I would think of a BIOS flaw. Regards Ralf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message