From owner-freebsd-arm@freebsd.org Fri Nov 17 02:00:13 2017 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 C31A9DF06E9 for ; Fri, 17 Nov 2017 02:00:13 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A4765748FD for ; Fri, 17 Nov 2017 02:00:13 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id vAH20Jf5041706 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Nov 2017 18:00:20 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id vAH20JE5041705; Thu, 16 Nov 2017 18:00:19 -0800 (PST) (envelope-from fbsd) Date: Thu, 16 Nov 2017 18:00:19 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: panic: dead bo 0xc47cf854 on rpi2 Message-ID: <20171117020019.GA41643@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 02:00:13 -0000 While running make clean in /usr/ports an rpi2 running FreeBSD www.zefox.com 12.0-CURRENT FreeBSD 12.0-CURRENT #8 r325884: Thu Nov 16 01:28:57 PST 2017 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/RPI2 arm reported panic: dead bo 0xc47cf854 Console, backtrace and logfile are at http://www.zefox.net/~fbsd/rpi2/crashes/crash_11_16_17/ I've never before seen a panic during make clean, in ports or src, so it was a considerable surprise. One other oddity was that an ssh session running a top window started to exit and close the ssh session without errors repeatedly after the make clean started, so it's unlikely the top window shown has much to do with what was running at the time of the panic. Thanks for reading, and any suggestions. bob prohaska