From owner-freebsd-arm@freebsd.org Fri Dec 4 17:00:38 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 674F0A415BB for ; Fri, 4 Dec 2015 17:00:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (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 479081A66 for ; Fri, 4 Dec 2015 17:00:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.14.9/8.14.5) with ESMTP id tB4H0UZp089855; Fri, 4 Dec 2015 09:00:30 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.14.9/8.14.5/Submit) id tB4H0UAF089854; Fri, 4 Dec 2015 09:00:30 -0800 (PST) (envelope-from fbsd) Date: Fri, 4 Dec 2015 09:00:30 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Repeated panic: ffs_checkblk: bad block -1 on rpi2 Message-ID: <20151204170030.GD7689@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i 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 17:00:38 -0000 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