From owner-freebsd-hackers@freebsd.org Sat Jan 13 02:43:50 2018 Return-Path: Delivered-To: freebsd-hackers@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 504A2E6A9D5; Sat, 13 Jan 2018 02:43:50 +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 2568E6DD1F; Sat, 13 Jan 2018 02:43:49 +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 w0D2hlL8049243 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jan 2018 18:43:48 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0D2hlMs049242; Fri, 12 Jan 2018 18:43:47 -0800 (PST) (envelope-from fbsd) Date: Fri, 12 Jan 2018 18:43:46 -0800 From: bob prohaska To: Mark Millard Cc: Freebsd-arm , FreeBSD Hackers , bob prohaska Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] Message-ID: <20180113024346.GB48702@www.zefox.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-Mailman-Approved-At: Sat, 13 Jan 2018 04:04:34 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 02:43:50 -0000 On Fri, Jan 12, 2018 at 05:53:03PM -0800, Mark Millard wrote: > > On 2018-Jan-12, at 4:54 PM, bob prohaska wrote: > > > > > The machine still answers ping. Typing escape control-b does not > > bring up a debugger, did the keysequence change? Power cycling seems > > to be the only way out. > > With or without: > > options ALT_BREAK_TO_DEBUGGER > > For with: ~^B (with being > and ^ being ) is an alternate with > this. > The line options ALT_BREAK_TO_DEBUGGER does not appear in the GENERIC kernel, but neither does the ue identifier for ethernet. I thought perhaps both were included from elsewhere. Maybe not. I'll add it. > I've see the smsc0 messages before but I'm > not up to -r327664+ yet. This has been with > a non-debug kernel running. > > I've had building large ports get into such states, > especially while at least one large link operation > was active with other fairly large processes, > as I remember. > > Note all the pfault and vmwait lines. It looks like > -r327316 and -r327468 did not happen to avoid this. > It looks like the paging/swaping has gotten stuck > in some way. How tied that might be to smsc0 > messages, I've no clue. > > You might get through by using -j3 or -j2 or -j1 which > likely would use less process space at once (worst case) > than -j4 happened to. > > Of course there are other time consequences as you > approach -j1 (or no explicit -j for the buildworld > at all). > > > I'd rather not slow things down, but slow is better than crashed.... 8-) Thanks for writing! bob prohaska