From owner-freebsd-hardware Wed Oct 21 01:22:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29541 for freebsd-hardware-outgoing; Wed, 21 Oct 1998 01:22:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA29523 for ; Wed, 21 Oct 1998 01:22:05 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 11703 invoked by uid 1001); 21 Oct 1998 08:20:01 +0000 (GMT) To: Tor.Egge@fast.no Cc: freebsd-current@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Problems with Digital server with P-166 and Neptune chipset In-Reply-To: Your message of "Wed, 21 Oct 1998 06:05:06 +0200" References: <199810210405.GAA07127@midten.fast.no> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 21 Oct 1998 10:20:01 +0200 Message-ID: <11701.908958001@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I now have some more info. Built a kernel with debug info, built an aout > > gdb. I have two identical machines running 3.0-RELEASE now, and both of > > them are crashing the same way (page fault in kernel mode) and in the > > same place (the zalloc inline routine in vm/vm_zone.h). ... > Looking at you dmesg output (from an earlier message), I find > > real memory = 269221888 (262912K bytes) > > instead of the expected > > real memory = 268435456 (262144K bytes) > > which indicates that the speculative memory probe stopped at 0x0100C0000, > i.e. at the end of aliased VGA memory. Yes, that was indeed the problem. Adding a suitable MAXMEM, as suggested, cured it. And I learned something about kernel debugging. Thanks a lot! Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message