From owner-freebsd-arm@freebsd.org Mon May 29 16:58:59 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 AE294D7B51A for ; Mon, 29 May 2017 16:58:59 +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 6557E8225F for ; Mon, 29 May 2017 16:58:59 +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 v4TGwxvj054857 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 May 2017 09:58:59 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v4TGwweH054856; Mon, 29 May 2017 09:58:58 -0700 (PDT) (envelope-from fbsd) Date: Mon, 29 May 2017 09:58:58 -0700 From: bob prohaska To: Warner Losh Cc: "freebsd-arm@freebsd.org" Subject: Re: 12.0-CURRENT #54 r318674 can't enter single user mode Message-ID: <20170529165858.GA54632@www.zefox.net> References: <20170529020808.GA52443@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Mon, 29 May 2017 16:58:59 -0000 On Mon, May 29, 2017 at 12:06:44AM -0600, Warner Losh wrote: > Signal 12 -- SIGSYS > > You're likely being bitten by not having enough compat in your kernel, > either new binaries on an old kernel, or old binaries on a new one. This > sort of thing should ever happen, but the ino64 merge had so many moving > parts it broke a lot of things. > Ok, at least it's not entirely self-inflicted...8-) Two questions: First, is the snapshot dated May 26th, 2017 recent enough to step around the problem? Second, is there some sort of formatting utility that can be used to rewrite the microSD card? At present the card seems unrecognizable when plugged into a Pi2 running 11-stable and a Pi3 running Raspbian. The adapter is an ATIVA PS2008 which worked fine in the past. No device file is created, so it's not even possible to blindly dd a new image. Thank you! bob prohaska > Warner > > On Sun, May 28, 2017 at 8:08 PM, bob prohaska wrote: > > > While building world and kernel on RPI2 12.0-CURRENT #54 r318674 reported > > "one error" and gradually became completely unresponsive. After > > power-cycling > > things looked normal until > > > > WARNING: / was not properly dismounted > > warning: no time-of-day clock registered, system time will not be set > > accurately > > random: unblocking device. > > arc4random: no preloaded entropy cache > > arc4random: no preloaded entropy cache > > arc4random: no preloaded entropy cache > > pid 27 (sh), uid 0: exited on signal 12 > > May 28 14:29:07 init: /bin/sh on /etc/rc terminated abnormally, going to > > single user mode > > Enter full pathname of shell or RETURN for /bin/sh: > > pid 28 (sh), uid 0: exited on signal 12 > > May 28 14:29:10 init: single user shell terminated, restarting > > Enter full pathname of shell or RETURN for /bin/sh: > > > > I've tried the escape, tilda, control-b sequence, it's echoed but > > the debugger does not take over the console. > > > > The machine had been running stably under fairly high load for > > several days compiling www/epiphany. During the world > > build epiphany was run and it started segfaulting after > > a couple of minutes. Shortly after that the world build stopped. > > I was unable to see the error message, unfortunately. > > > > Thanks for reading, and any thoughts. > > > > bob prohaska > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >