From owner-freebsd-stable@FreeBSD.ORG Tue Oct 19 03:11:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E86DA106564A for ; Tue, 19 Oct 2010 03:11:52 +0000 (UTC) (envelope-from wilkinsa@dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.freebsd.org (Postfix) with ESMTP id 735698FC08 for ; Tue, 19 Oct 2010 03:11:52 +0000 (UTC) Received: from ednmsw520.dsto.defence.gov.au (ednmsw520.dsto.defence.gov.au [131.185.68.60]) by digger1.defence.gov.au (DSTO/DSTO) with ESMTP id o9J3568H009173 for ; Tue, 19 Oct 2010 12:35:07 +0930 (CST) Received: from ednex510.dsto.defence.gov.au (ednex510.dsto.defence.gov.au) by ednmsw520.dsto.defence.gov.au (Clearswift SMTPRS 5.4.0) with ESMTP id for ; Tue, 19 Oct 2010 13:41:49 +1030 Received: from stlex511.dsto.defence.gov.au ([203.6.60.49]) by ednex510.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 Oct 2010 13:41:48 +1030 Received: from stlux550.dsto.defence.gov.au ([203.6.60.61]) by stlex511.dsto.defence.gov.au with Microsoft SMTPSVC(6.0.3790.4675); Tue, 19 Oct 2010 11:11:44 +0800 Received: from stlux550.dsto.defence.gov.au (localhost [127.0.0.1]) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3) with ESMTP id o9J3Bifn068995 for ; Tue, 19 Oct 2010 11:11:44 +0800 (WST) (envelope-from wilkinsa@stlux550.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by stlux550.dsto.defence.gov.au (8.14.3/8.14.3/Submit) id o9J3BinT068994 for freebsd-stable@freebsd.org; Tue, 19 Oct 2010 11:11:44 +0800 (WST) (envelope-from wilkinsa) Date: Tue, 19 Oct 2010 11:11:44 +0800 From: "Wilkinson, Alex" To: freebsd-stable@freebsd.org Message-ID: <20101019031144.GA68635@stlux503.dsto.defence.gov.au> Mail-Followup-To: freebsd-stable@freebsd.org References: <1287158693.5225.7.camel@home-yahoo> <20101015162714.GA12400@icarus.home.lan> <4CB881AF.1080708@acm.poly.edu> <1287160697.5225.14.camel@home-yahoo> <1287258720.2522.26.camel@home-yahoo> <20101016201603.GA9807@icarus.home.lan> <1287266288.2522.27.camel@home-yahoo> <1287353406.2431.3.camel@home-yahoo> <20101018113334.GA33226@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20101018113334.GA33226@icarus.home.lan> Organisation: Defence Science Technology Organisation X-Message-Flag: "Please Restore Line Breaks If Necessary" User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 19 Oct 2010 03:11:45.0031 (UTC) FILETIME=[5C2BA970:01CB6F3B] X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17712.004 X-TM-AS-Result: No--2.363000-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No Content-Transfer-Encoding: 7bit Subject: Re: kpanic on install >32GB of RAM [SEC=UNCLASSIFIED] 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: Tue, 19 Oct 2010 03:11:53 -0000 0n Mon, Oct 18, 2010 at 04:33:34AM -0700, Jeremy Chadwick wrote: >On Sun, Oct 17, 2010 at 03:10:06PM -0700, Sean Bruno wrote: >> >> > We've successfully installed RHEL 5u4 on it, I'll fire that up and post >> > the boot output shortly. >> > >> > Sean >> >> >> Perhaps this is something as simple as a hardware failure? HP DL980 >> looks sick, but I'm not sure. Here's the hardware logs, from the iLO on >> the box as screen scraping on the console is pointless as it's garbled >> too badly. >> >> Bad CPU, Bad Ram or other? >> >> http://people.freebsd.org/~sbruno/dl980_Machcheck_exceptions.png > >Hard to say -- the MCE will need to be decoded. I'm working on a >program which can do this, though I know John Baldwin already has one >which should work. Will it work something like http://freshmeat.net/projects/mcelog/ ? -Alex IMPORTANT: This email remains the property of the Department of Defence and is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have received this email in error, you are requested to contact the sender and delete the email.