From owner-freebsd-hardware@FreeBSD.ORG Fri Jun 25 13:29:41 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 E0F23106564A for ; Fri, 25 Jun 2010 13:29:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B5D228FC15 for ; Fri, 25 Jun 2010 13:29:41 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 70E5D46B4C; Fri, 25 Jun 2010 09:29:41 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7DA118A04E; Fri, 25 Jun 2010 09:29:40 -0400 (EDT) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Fri, 25 Jun 2010 08:42:22 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C2499B5.3030404@wp.pl> In-Reply-To: <4C2499B5.3030404@wp.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006250842.22551.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 25 Jun 2010 09:29:40 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Ireneusz Pluta 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 13:29:42 -0000 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 > Jun 22 15:09:21 emu kernel: > Jun 22 15:09:21 emu kernel: I > Jun 22 15:09:21 emu kernel: > Jun 22 15:09:21 emu kernel: < > Jun 22 15:09:21 emu kernel: <<2>22< >00<, > Jun 22 15:09:21 emu kernel: > Jun 22 15:09:21 emu kernel: <>2>EI2S2A 0 > Jun 22 15:09:21 emu kernel: 0> > Jun 22 15:09:21 emu kernel: ,< SE2AI>S>A 0E 3IS0IA, S A0E > Jun 22 15:09:21 emu kernel: I > Jun 22 15:09:21 emu kernel: > Jun 22 15:09:21 emu kernel: > Jun 22 15:09:21 emu kernel: <<2>2S>A 300 > Jun 22 15:09:21 emu kernel: , > Jun 22 15:09:21 emu kernel: EISA 0 > Jun 22 15:09:24 emu kernel: NMI ISA N3M0I, IESNISAAM 0I > Jun 22 15:09:24 emu kernel: 3N > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: < > Jun 22 15:09:24 emu kernel: <22<>0,EN I2IMI>SASA NM0> 2INI > Jun 22 15:09:24 emu kernel: >MS I > Jun 22 15:09:24 emu kernel: MMAE A II2S 0I, AI IE0SIS > Jun 22 15:09:24 emu kernel: SS > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: < > Jun 22 15:09:24 emu kernel: 2<<> Jun 22 15:09:24 emu kernel: 2 > Jun 22 15:09:24 emu kernel: ><>>A2 A200 , 22E>,0I ,SE EIASI SAA 00A2 > Jun 22 15:09:24 emu kernel: 0 > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: > Jun 22 15:09:24 emu kernel: <<22>>,0 > Jun 22 15:09:24 emu kernel: E > Jun 22 15:09:24 emu kernel: ISA 0 You are getting NMI's. Have you tried checking the system's event log (if it has one) for messages about hardware errors? -- John Baldwin