From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 30 10:09:23 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35899106566C for ; Wed, 30 Jun 2010 10:09:23 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id B24548FC1A for ; Wed, 30 Jun 2010 10:09:22 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 26657 invoked from network); 30 Jun 2010 12:09:19 +0200 Received: from 121-20-N1.aster.pl (HELO [127.0.0.1]) (ipluta@[94.75.121.20]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 30 Jun 2010 12:09:19 +0200 Message-ID: <4C2B17CE.5060209@wp.pl> Date: Wed, 30 Jun 2010 12:09:18 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Antony Mawer References: <4C2499B5.3030404@wp.pl> <201006281326.08896.jhb@freebsd.org> <4C28E287.5010103@wp.pl> <201006281409.23546.jhb@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [UROk] Cc: freebsd-hardware@freebsd.org Subject: Re: System hangs during heavy sequential write to mfi device X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 10:09:23 -0000 Antony Mawer pisze: > On Tue, Jun 29, 2010 at 4:09 AM, John Baldwin wrote: > >> On Monday 28 June 2010 1:57:27 pm Ireneusz Pluta wrote: >> >>> John Baldwin pisze: >>> >>>> On Monday 28 June 2010 12:00:06 pm Ireneusz Pluta wrote: >>>> >>>> >>>>> John Baldwin pisze: >>>>> >>>>> >>>>>> On Friday 25 June 2010 4:59:57 pm Ireneusz Pluta wrote: >>>>>> >>>>>> >>>>>> >>>>>>> John Baldwin pisze: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hmmm. You might have a hardware issue. OTOH, you can try seeing if >>>>>>>> >> you >> >>>> have >>>> >>>> >>>>>>>> a BIOS option to disable PCIE error logging. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> is it one of them?: >>>>>>> >>>>>>> Assert NMI on SERR >>>>>>> Assert NMI on PERR >>>>>>> >>>>>>> (pdf page 109 of: -> >>>>>>> >>>>>>> >>>>>>> >> http://download.intel.com/support/motherboards/server/s5520hc/sb/e39529013_s5520hc_s5500hcv_s5520hct_tps_r1_9.pdf) >> >>>>>>> >>>>>> Well, that will turn off the NMIs. Not sure if it will affect the event >>>>>> logging, but it is worth a shot. >>>>>> >>>>>> >>>>>> >>>>> Per BIOS setup documentation: >>>>> >>>>> On SERR, generate an NMI and log an error. >>>>> Note: [Enabled] must be selected for the Assert NMI >>>>> on PERR setup option to be visible. >>>>> >>>>> and: >>>>> >>>>> On PERR, generate an NMI and log an error. >>>>> Note: This option is only active if the Assert NMI on >>>>> SERR option is [Enabled] selected. >>>>> >>>>> However, disabling them did not change anything. >>>>> >>>>> >>>> Is it still logging errors and sending NMIs with them disabled? >>>> >>>> >>> with the options I mentioned disabled. They do not have to be the only >>> sources of NMIs, do they? >>> >> Well, they should be the sources of the log messages you found in your system >> event log. There is a good chance that you have some broken hardware >> somewhere, I'm not sure how easy it is for you to debug that via swapping out >> components, but the RAID controller is the first thing I would try. >> > > You might want to try a BIOS update to see if it resolves these > problems ... I seem to remember some mention of these sorts of errors > in the change log of one of the recent Intel server board BIOSes. > Yeah, I tried, and the problem dissappeared. I really could do that initially but none of the entries found in the BIOS changelog from Intel seemed to address my particular issue.