From owner-freebsd-arm@freebsd.org Mon Jun 11 00:24:16 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 926A010012FF for ; Mon, 11 Jun 2018 00:24:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 0DCD480DF7 for ; Mon, 11 Jun 2018 00:24:15 +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 w5B0OMbY011771 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Jun 2018 17:24:23 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5B0OMcX011770; Sun, 10 Jun 2018 17:24:22 -0700 (PDT) (envelope-from fbsd) Date: Sun, 10 Jun 2018 17:24:22 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: RPI3, panic on warm boot at r334894 Message-ID: <20180611002421.GA11616@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 00:24:16 -0000 For the first time in months my Pi3 got through a -j4 buildworld/installworld cycle. Make clean was run in /usr/src, but no other cleaning was done and the -DNO_CLEAN option was used in buildworld/buildkernel. However, on reboot using shutdown -r now it panic'd, with (in part) (da0:umass-sim0:0:0:0): Error 5, Retries exhausted g_vfs_done():da0a[READ(offset=163840, length=32768)]error = 5 panic: mount: lost mount cpuid = 3 time = 1528671592 KDB: stack backtrace: [console output is at http://www.zefox.net/~fbsd/rpi3/crashes/20180610/] On a whim, I power-cycled the machine, and it came back up just fine. Sources were updated to 334935 and a new build/install cycle is running, again using -DNO_CLEAN to speed things along, without any cleaning. This is the second occurrence in the last couple of days. Last time the system was rebooted (warm) to the old kernel, this time a complete power cycle cleared the error. Might the -DNO_CLEAN be the culprit? I expected it would cause compile time problems, if any. Thanks for reading, and any guidance. bob prohaska