From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 21:13:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A796D0C for ; Mon, 23 Jun 2014 21:13:34 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65C462510 for ; Mon, 23 Jun 2014 21:13:34 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 505BEB91F; Mon, 23 Jun 2014 17:13:33 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org, lausts@acm.org Subject: Re: Intermittant Kernel Panic FreeBSD 10 STABLE Date: Mon, 23 Jun 2014 16:20:46 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <53A05461.22133.7CA31A@lausts.acm.org> In-Reply-To: <53A05461.22133.7CA31A@lausts.acm.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201406231620.46779.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 23 Jun 2014 17:13:33 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 21:13:34 -0000 On Tuesday, June 17, 2014 10:44:49 am Thomas Laus wrote: > I have a new Giabyte J1900N-D3V motherboard that intermittantly panics when > starting up or rebooting. It shows the same issue on FreeBSD 10 Release and > FreeBSD Stable snapshot r265408. I loaded and ran with a FreeBSD Current > r265628 snapshot for a few days without any issues. I also loaded and ran > Win7 for 2 weeks on this system without any problems. This PC does have > a solid state disk, which may affect my boot time. > > Most of the time the automatic reboot after the panic proceeds normally and > once the system is up, everything appears to work normally. I have been > able to make and build world as well as rebuild all of my ports without > any problem. So does HEAD never panic but 10 often panics? The odd thing here is that this should be a static table generated by the BIOS that should have the same contents every boot. The panic is claiming that one of the fields in the table is set to an invalid value. If it happened on every boot it could be a software bug (or a BIOS bug we need to workaround). If it only happens on certain boots it feels more like a memory error. :-/ -- John Baldwin