From owner-freebsd-stable@FreeBSD.ORG Mon Apr 23 17:31:19 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E858F16A408 for ; Mon, 23 Apr 2007 17:31:19 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog10.obsmtp.com (s200aog10.obsmtp.com [207.126.144.124]) by mx1.freebsd.org (Postfix) with SMTP id B0F6913C489 for ; Mon, 23 Apr 2007 17:31:05 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob010.postini.com ([207.126.147.11]) with SMTP; Mon, 23 Apr 2007 17:31:04 UTC Received: from [10.0.0.89] (bill.mintel.co.uk [10.0.0.89]) by rodney.mintel.co.uk (Postfix) with ESMTP id 54B5118141B; Mon, 23 Apr 2007 18:31:04 +0100 (BST) Message-ID: <462CED97.9070707@tomjudge.com> Date: Mon, 23 Apr 2007 18:32:07 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Michael Proto References: <462CA594.5000904@tomjudge.com> <20070423155728.GC1006@xor.obsecurity.org> <462CE8FE.8060807@jellydonut.org> In-Reply-To: <462CE8FE.8060807@jellydonut.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present) 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: Mon, 23 Apr 2007 17:31:20 -0000 Michael Proto wrote: > Kris Kennaway wrote: >> On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: >>> Hi, >>> >>> Recently I have noticed that one of our Dell PE1950's has been crashing >>> a lot with the following reason "supervisor read, page not present". >>> >>> The system runs 6.2 Release under i386. >>> >>> I have attached 2 back traces, and I still have both cores if any more >>> information is required. Any light that can be shed on this problem >>> would be greatly appreciated. >>> <<>> >> You might be hitting a bug in an obscure code path because of the >> above errors. I'm CC'ing someone who might be able to help. >> >> Kris >> > > Bear in mind that a recent "urgent" firmware update was released by Dell > last week for 1950, 1955, and 2950 systems that is supposed to fix some > data-corruption issues related to dual-core processors. I don't know if > this problem is a symptom of that, but it strongly suggested to apply > the firmware update regardless. > > I have just been to dells site and there are firmware updates for almost every component in the system released about 2 weeks ago (10-11/4). I have around 17 [12]950's waiting to go into pre production testing at the moment so I think that I will spend some time upgrading the firmware on them now rather than later. Thanks for the heads up. Tom