Date: Thu, 26 Nov 2009 10:27:58 +0300 From: KOT MATPOCKuH <matpockuh@gmail.com> To: Marius Strobl <marius@alchemy.franken.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: Is it posible to run FreeBSD/sparc64 on SunFire V215? Message-ID: <3979a4b0911252327r679a8594id7d18224adfd1d5f@mail.gmail.com> In-Reply-To: <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> <20091116221414.GS27738@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/11/17 Marius Strobl <marius@alchemy.franken.de>: >> 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? -- MATPOCKuH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3979a4b0911252327r679a8594id7d18224adfd1d5f>