From owner-freebsd-hardware@FreeBSD.ORG Fri Jun 25 15:52:19 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 A8C0B106564A for ; Fri, 25 Jun 2010 15:52:19 +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 33C678FC19 for ; Fri, 25 Jun 2010 15:52:18 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 23989 invoked from network); 25 Jun 2010 17:52:17 +0200 Received: from abbp41.neoplus.adsl.tpnet.pl (HELO [127.0.0.1]) (ipluta@[83.6.205.41]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 25 Jun 2010 17:52:17 +0200 Message-ID: <4C24D0AF.5000307@wp.pl> Date: Fri, 25 Jun 2010 17:52:15 +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> <201006250842.22551.jhb@freebsd.org> In-Reply-To: <201006250842.22551.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 [QSPE] 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: Fri, 25 Jun 2010 15:52:19 -0000 John Baldwin pisze: > On Friday 25 June 2010 7:57:41 am Ireneusz Pluta wrote: > >> Hello, >> >> I already posted this to freebsd-questions, with no response, so far. >> As this is rather a problem closer to hardware issues, so maybe here I >> have a better luck. Hope nobody blames me for crossposting. >> >> Jun 22 15:09:21 emu kernel: N NISAM NIM I II3SS0A,A N NE3MIMS0II3, >> N 0I ,ENSIMA NSI IEAMASI MI A IS3S A00 0, >> Jun 22 15:09:21 emu kernel: I >> Jun 22 15:09:21 emu kernel: A33 >> >> > You are getting NMI's. Have you tried checking the system's event log (if it > has one) for messages about hardware errors? > > Thank you, John, for paying attention. The mb is intel S5520HC so it has event log. From your article http://www.bsdcan.org/2008/schedule/attachments/45_article.pdf I found that I yet needed impitool, so I installed it. `impitool sel elist` shows quite a lot of messages already stored like these: e05 | 06/24/2010 | 18:08:24 | Critical Interrupt PCIe Fat Sensor | e06 | 06/24/2010 | 18:09:28 | Critical Interrupt PCIe Fat Sensor | e07 | 06/25/2010 | 16:12:56 | Critical Interrupt PCIe Fat Sensor | e08 | 06/25/2010 | 17:34:16 | Critical Interrupt PCIe Fat Sensor | e09 | 06/25/2010 | 17:34:55 | Critical Interrupt PCIe Fat Sensor | They seem to appear exactly at the moments of system lockups - the last two were appended after I made another try. Intel document related to the motherboard http://download.intel.com/support/motherboards/server/sb/e68105004_msu_s5520hc_s5500hcv_july_09.pdf says something about these messages, but in the context completely unrelated to my case. Any thoughts?