From owner-freebsd-sparc64@FreeBSD.ORG Sun Nov 29 21:50:52 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 C5860106568F for ; Sun, 29 Nov 2009 21:50:52 +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 532988FC15 for ; Sun, 29 Nov 2009 21:50:51 +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 nATLooHl041345; Sun, 29 Nov 2009 22:50:50 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id nATLooDD041344; Sun, 29 Nov 2009 22:50:50 +0100 (CET) (envelope-from marius) Date: Sun, 29 Nov 2009 22:50:50 +0100 From: Marius Strobl To: KOT MATPOCKuH Message-ID: <20091129215050.GV6562@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> <20091116221414.GS27738@alchemy.franken.de> <3979a4b0911252327r679a8594id7d18224adfd1d5f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3979a4b0911252327r679a8594id7d18224adfd1d5f@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: Sun, 29 Nov 2009 21:50:52 -0000 On Thu, Nov 26, 2009 at 10:27:58AM +0300, KOT MATPOCKuH wrote: > 2009/11/17 Marius Strobl : > > >> 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 > > > 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. > After 8 days of uptime: > 10:22AM up 8 days, 16:42, 11 users, load averages: 0.01, 0.00, 0.00 > I have: > # sysctl -a | grep jbc_unsol_int > dev.pcib.0.jbc_unsol_int: 0 > dev.pcib.12.jbc_unsol_int: 0 > > Is it indicates that the problem is solved? Well, I don't know how frequently you've hit this problem before (was it always in the 1-2 days range?) but an uptime of 8 days without seeing an unsolicited interrupt ACK/NACK indeed suggest that the bug fixed was the culprit in this case. I haven't seen this issue myself as I had fixed the bug here before upgrading my v215 to SMP. FYI, pending some final tests I think that the code for supporting PCIe-based sun4u machines is now ready for hitting HEAD (but given that it touches several pieces, commit it while take a bit). Marius