From owner-freebsd-questions@FreeBSD.ORG Fri Jan 12 03:01:06 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2226616A407 for ; Fri, 12 Jan 2007 03:01:06 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id B70C413C457 for ; Fri, 12 Jan 2007 03:01:05 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-174-60.hsd1.pa.comcast.net [71.60.174.60]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Thu, 11 Jan 2007 22:01:04 -0500 id 0005648D.45A6F9F0.0000548C Date: Thu, 11 Jan 2007 22:00:48 -0500 From: Bill Moran To: Josh Paetzel Message-Id: <20070111220048.a26c6bc5.wmoran@collaborativefusion.com> In-Reply-To: <200701111909.52695.josh@tcbug.org> References: <45A596FC.8040907@chapman.edu> <200701111909.52695.josh@tcbug.org> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed version 2.2.10 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, Jay Chandler Subject: Re: Dell PE 1950 - Only seeing 3.2 gigs of ram X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 03:01:06 -0000 Josh Paetzel wrote: > > On Wednesday 10 January 2007 19:46, Jay Chandler wrote: > > > On a related note for this hardware platform, has anyone gotten > > past the "randomly decides not to reboot when told to" issue? > > Requires a hard shutdown by hand, as the console becomes completely > > non-responsive. > > I've heard of this problem, some people have it all the time and > others don't have it at all on the PE 1950. I suspect it has > something to do with the way Dell will occassionally change hardware > mid-run and not tell anyone. :) It's a bizarre timing problem involving the shutdown of drivers. We were trying to track it down, but any time we changed anything in the code, the problem disappeared (i.e. just adding a printf()). Our conclusion was that it was an extremely sensitive timing issue.