From owner-freebsd-arm@freebsd.org Fri Dec 4 18:07:41 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52DFFA417EC for ; Fri, 4 Dec 2015 18:07:41 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 34DEC1C17 for ; Fri, 4 Dec 2015 18:07:40 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Fri, 4 Dec 2015 18:08:11 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tB4I7bK8022043; Fri, 4 Dec 2015 11:07:37 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1449252457.6214.37.camel@freebsd.org> Subject: Re: Repeated panic: ffs_checkblk: bad block -1 on rpi2 From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Fri, 04 Dec 2015 11:07:37 -0700 In-Reply-To: <20151204170030.GD7689@www.zefox.net> References: <20151204170030.GD7689@www.zefox.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2015 18:07:41 -0000 On Fri, 2015-12-04 at 09:00 -0800, bob prohaska wrote: > Hi all, > > The last few attempts to build world have failed with > panic: ffs_checkblk: bad block -1 > The latest incident was at r291652. > > So far, it's been possible to restart the machine and > complete the build/install cycle, typically in single > user mode as a precaution. Once complete the reboot has > been uneventful. > > The same failure has been seen on both disk and flash > backed machines. Later instances have been on the disk- > backed machine, simply because it is the only one with > serial console. > > The latest event is documented to the best of my ability at > www.zefox.net/~fbsd/rpi2/crashes/build_12_4_15 > > Is there any chance this might be a hardware issue? For the > moment I tend to think not, but am far from certain. > > Thanks for reading and any guidance, > > bob prohaska > I see from your console log that you're on r291652. I think the problem you're having was introduced at r291460 and fixed in r291671 and/or r291743. So just updating the kernel source may fix it. The problem may prevent you from building a newer kernel, you might have to crossbuild it, or grab a kernel out of a snapshot archive from a couple weeks ago. -- Ian