Date: Mon, 16 Nov 2009 23:14:14 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: KOT MATPOCKuH <matpockuh@gmail.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: Is it posible to run FreeBSD/sparc64 on SunFire V215? Message-ID: <20091116221414.GS27738@alchemy.franken.de> In-Reply-To: <3979a4b0911120450i31831743j80fd1cfd7c6916b4@mail.gmail.com> References: <3979a4b0909170200x754ea8c5l495e300b2a7a5113@mail.gmail.com> <20090917224556.GA41908@alchemy.franken.de> <3979a4b0909172329q3a113942xfcd71394a98fee19@mail.gmail.com> <20090918131416.GQ57060@alchemy.franken.de> <3979a4b0911120450i31831743j80fd1cfd7c6916b4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091116221414.GS27738>