From owner-freebsd-sparc64@FreeBSD.ORG Mon Nov 16 22:14:17 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07277106566B for ; Mon, 16 Nov 2009 22:14:17 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 8A2DE8FC0A for ; Mon, 16 Nov 2009 22:14:16 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id nAGMEEjb089617; Mon, 16 Nov 2009 23:14:15 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id nAGMEEEF089616; Mon, 16 Nov 2009 23:14:14 +0100 (CET) (envelope-from marius) Date: Mon, 16 Nov 2009 23:14:14 +0100 From: Marius Strobl To: KOT MATPOCKuH Message-ID: <20091116221414.GS27738@alchemy.franken.de> References: <3979a4b0909170200x754ea8c5l495e300b2a7a5113@mail.gmail.com> <20090917224556.GA41908@alchemy.franken.de> <3979a4b0909172329q3a113942xfcd71394a98fee19@mail.gmail.com> <20090918131416.GQ57060@alchemy.franken.de> <3979a4b0911120450i31831743j80fd1cfd7c6916b4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3979a4b0911120450i31831743j80fd1cfd7c6916b4@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: Is it posible to run FreeBSD/sparc64 on SunFire V215? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2009 22:14:17 -0000 On Thu, Nov 12, 2009 at 03:50:58PM +0300, KOT MATPOCKuH wrote: > Hello! > > I'm got three host panic three times with this message: > panic: pcib12: XCB error status 0x1 interrupt status 0x8 > cpuid = 0 > Uptime: 1d14h51m50s > Cannot dump. Device not defined or unavailable. > Automatic reboot in 15 seconds - press a key on the console to abort > > Is it information enough or I need to collect a crash dump from a system? > A crash dump wouldn't provide information relevant for this problem. The panic message indicates an unsolicited interrupt ACK/NACK has occured, which actually are not fatal. Please use the current patchset from: http://people.freebsd.org/~marius/fire.diff It fixes a possible cause for this problem (inappropriate interrupt group controller assignment) as well as hopefully handles such interrupts gracefully should they still occur. You'll need to either watch the dev.pcib.X.jbc_unsol_int (probably 0 and 12) SYSCTLs or boot verbosely to still get ahold of them though. Marius