From owner-freebsd-arm@freebsd.org Sat Mar 4 16:57:42 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 1E56ECF9658 for ; Sat, 4 Mar 2017 16:57:42 +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 F2829163E for ; Sat, 4 Mar 2017 16:57:41 +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 v24GvecT009697 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 4 Mar 2017 08:57:41 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v24GveCV009696; Sat, 4 Mar 2017 08:57:40 -0800 (PST) (envelope-from fbsd) Date: Sat, 4 Mar 2017 08:57:40 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Booting an old kernel on RPI2 Message-ID: <20170304165740.GA9625@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.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2017 16:57:42 -0000 A recent world/kernel build went badly wrong, resulting in an "out of memory" report on the console and no further progress. There are two spare kernels on the system, kernel.old and kernel.spare, but even kernel.spare, which I know worked, still produces the same "out of memory" prompt on the console. The console output contains: loader> load /boot/kernel.spare/kernel /boot/kernel.spare/kernel data=0x60f7e4+0x10081c syms=[0x4+0x83aa0+0x4+0x97216] loader> boot -s Booting... followed by the line Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... WARNING: / was not properly dismounted warning: no time-of-day clock registered, system time will not be set accurately Enter full pathname of shell or RETURN for /bin/sh: Somewhat later the console emitted random: unblocking device which I didn't expect; I thought it would wait at the # prompt. In this state even the debugger escape just produces "out of memory". Am I making a syntax error in trying to boot kernel.spare in single user? Might this behavior indicate a hardware problem of some sort? Thanks for reading! bob prohaska