From owner-freebsd-current@freebsd.org Wed Jun 6 18:55:45 2018 Return-Path: Delivered-To: freebsd-current@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 54187FDE9D9; Wed, 6 Jun 2018 18:55:45 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB3E6820EC; Wed, 6 Jun 2018 18:55:44 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fQdat-0004aE-Ty; Wed, 06 Jun 2018 20:55:40 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "bob prohaska" Cc: freebsd-arm@freebsd.org, "FreeBSD Current" Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 References: <20180601154153.GA62632@www.zefox.net> Date: Wed, 06 Jun 2018 20:55:39 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a6d9551f4f6a9cf0aa9f9bf7e32696d9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 18:55:45 -0000 On Sat, 02 Jun 2018 13:40:27 +0200, Ronald Klop wrote: > This happened again. Now I have a crashdump. > Anyone interested? > > Some more answers below. > > > On Fri, 01 Jun 2018 17:41:54 +0200, bob prohaska > wrote: > >> On Thu, May 31, 2018 at 05:53:12PM +0200, Ronald Klop wrote: >>> I had a crash on my RPI-3B+ running freebsd 12/aarch64 from the 29 may >>> snapshot. >>> It was building world -j4 and portsnap extract. >>> >>> I will keep it in the debugger for about an hour so if I need to >>> provide >>> more information, please mail me. >>> >>> >>> db> show panic >>> panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at >>> /usr/src/sys/kern/sched_ule.c:2137 >>> >> This used to be a fairly common error on my RPI3, but I haven't seen >> it in some time. >> >> As a matter of curiosity, have you been able to run a -j4 buildworld >> to completion on your RPI3? If so, please post your setup. For several >> months now all my attempts at j4 buildworld have failed with "killed, >> out of swap" even though top seems to report minimal swap usage. It >> even happens with no -j value set at all, but usually restarting with >> -DNO_CLEAN allowed progress to pick up where it left off. How do you ever run a -j4 buildworld? My RPI3 starts building clang/llvm with sometimes 500 MB+ per process so everything starts swapping like hell and takes forever to run. Regards, Ronald. >> >> Alas, as I write this, the kernel just reported >> >> Jun 1 08:34:34 www kernel: pid 19399 (c++), uid 0, was killed: out of >> swap space >> >> top is showing >> Swap: 4096M Total, 17M Used, 4079M Free >> but since top is alive the value is stale. Nonetheless, I have seen top >> killed while still showing minimal swap usage. >> >> It seems as if the "out of swap" kills are being issued in error.. >> >> Thanks for reading, >> >> bob prohaska >> > > > I just received my RPI3 this week. It is running GENERIC with debug > options still. Building a -NODEBUG kernel from src didn't succeed yet > because of the mentioned panic. > I'm now building with -j2 to be on the safe side. > > After I have the -NODEBUG kernel it will be a bit faster and I will try > -j4 again. > > Regards, > Ronald.