From owner-freebsd-stable@FreeBSD.ORG Thu Nov 24 23:16:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF38C16A80C for ; Thu, 24 Nov 2005 23:16:02 +0000 (GMT) (envelope-from dan@syz.com) Received: from mail.clearwave.ca (h139-142-194-114.gtcust.grouptelecom.net [139.142.194.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA0545C21 for ; Thu, 24 Nov 2005 21:49:20 +0000 (GMT) (envelope-from dan@syz.com) Received: from localhost (localhost.clearwave.ca [127.0.0.1]) by mail.clearwave.ca (Postfix) with ESMTP id 0783A1037A68 for ; Thu, 24 Nov 2005 14:49:07 -0700 (MST) Received: from mail.clearwave.ca ([127.0.0.1]) by localhost (mail.clearwave.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74244-01 for ; Thu, 24 Nov 2005 14:48:58 -0700 (MST) Received: from [192.168.2.108] (h139-142-196-33.gtcust.grouptelecom.net [139.142.196.33]) by mail.clearwave.ca (Postfix) with ESMTP id 74FF41037A48 for ; Thu, 24 Nov 2005 14:48:58 -0700 (MST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <24EC8636-1C7E-418A-BD16-41F5AF57C988@syz.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Dan Charrois Date: Thu, 24 Nov 2005 14:49:10 -0700 X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at clearwave.ca Subject: Re: FreeBSD unstable on Dell 1750 using SMP? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 23:16:03 -0000 I just thought of one other bit of info that may be relevant to the auto-rebooting problem I've experienced with our PowerEdge 2850. Since the problem may be related to memory allocation, I thought I should mention that we have more memory in that machine that is typical for some users. We have 5 Gigs installed. From "top": Mem: 175M Active, 4121M Inact, 244M Wired, 244M Cache, 214M Buf, 23M Free Swap: 10G Total, 12K Used, 10G Free If this turns out to be an AMD64 vs. 386 issue and we were to revert to the 386 branch, would we still be able to access this memory, or would the 386 be limited to 4Gb (or maybe 2Gb) due to 32 bit addressing? We don't need anywhere near this much memory for user space programs, but the kernel does make good use of it to cache commonly accessed regions of the file system in memory. Dan -- Syzygy Research & Technology Box 83, Legal, AB T0G 1L0 Canada Phone: 780-961-2213