From owner-freebsd-arm@freebsd.org Fri Apr 29 18:52:10 2016 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 453C1B211FD for ; Fri, 29 Apr 2016 18:52:10 +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 0EC5318B9 for ; Fri, 29 Apr 2016 18:52:09 +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 u3TIqAYe072641 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Apr 2016 18:52:11 GMT (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id u3TIq9S7072640; Fri, 29 Apr 2016 11:52:09 -0700 (PDT) (envelope-from fbsd) Date: Fri, 29 Apr 2016 11:52:09 -0700 From: bob prohaska To: Svatopluk Kraus Cc: "freebsd-arm@freebsd.org" Subject: Re: Another reboot hang Message-ID: <20160429185209.GQ71221@www.zefox.net> References: <20160426183030.GN71221@www.zefox.net> <20160426204016.GO71221@www.zefox.net> <20160426214309.GP71221@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.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 18:52:10 -0000 On Wed, Apr 27, 2016 at 05:15:49PM +0200, Svatopluk Kraus wrote: > > Those were general hints how to deal with such situation. In your > case, it looks more like an infinite waiting for something on another > thread not in your backtrace. So the all procs and locks dumps would > be unavoidable. And probably a backtrace of all threads too. > > So far the reboot hang hasn't repeated in half a dozen or so attempts..... not sure if that's good or bad. In the meantime the system ran stress2 (old version) for 12 hours 49 minutes, the previous record was around ten hours. Interestingly, the crash did _not_ report "translation fault (L2)", but rather "panic: pmap_growkernel: no memory to grow kernel". That's different, at least. Thanks for reading, bob prohaska