From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 02:08:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D2D816A4CE for ; Tue, 24 Aug 2004 02:08:33 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D4C243D31 for ; Tue, 24 Aug 2004 02:08:33 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i7O28Wgv042455; Mon, 23 Aug 2004 19:08:32 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i7O28WNf042454; Mon, 23 Aug 2004 19:08:32 -0700 (PDT) (envelope-from sgk) Date: Mon, 23 Aug 2004 19:08:32 -0700 From: Steve Kargl To: Peter Wemm Message-ID: <20040824020832.GA42331@troutmask.apl.washington.edu> References: <20040823230619.GB41337@troutmask.apl.washington.edu> <200408231901.13938.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408231901.13938.peter@wemm.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: AMD64 VM panic with >8 GB memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2004 02:08:33 -0000 On Mon, Aug 23, 2004 at 07:01:13PM -0700, Peter Wemm wrote: > On Monday 23 August 2004 04:06 pm, Steve Kargl wrote: > > Some relevant info. The motherboard is a Tyan K8S Pro > > (S2882) with 12 GB of PC2700 ECC memory. If I limit > > the memory by setting 'hw.physmem="8G"' in the loader > > or in /boot/loader.conf, then the system boots fine. > > Any other setting above 8G will result in the above panic. > > > > The panic occurs too earlier to get a crash dump. > > However, I'm will to try any patch or settings. > > Hmm. I think we had an amd64 machine around somewhere at work that had > 16G of ram. I'll ask what happened to it and see if it can be > recovered to sort this out. > Thanks for looking into this. I can test any patches you devise. I also suspect that this problem is RELENG_5. -- Steve