From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 28 17:57:30 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 C1EFC106566B for ; Mon, 28 Jun 2010 17:57:30 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx3.wp.pl (mx3.wp.pl [212.77.101.7]) by mx1.freebsd.org (Postfix) with ESMTP id 4D0D98FC1A for ; Mon, 28 Jun 2010 17:57:29 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 20170 invoked from network); 28 Jun 2010 19:57:28 +0200 Received: from aayh18.neoplus.adsl.tpnet.pl (HELO [127.0.0.1]) (ipluta@[83.6.119.18]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 28 Jun 2010 19:57:28 +0200 Message-ID: <4C28E287.5010103@wp.pl> Date: Mon, 28 Jun 2010 19:57:27 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: John Baldwin References: <4C2499B5.3030404@wp.pl> <201006280937.56174.jhb@freebsd.org> <4C28C706.80309@wp.pl> <201006281326.08896.jhb@freebsd.org> In-Reply-To: <201006281326.08896.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [kfPk] 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: Mon, 28 Jun 2010 17:57:30 -0000 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?