From owner-freebsd-arm@freebsd.org Sun Jun 3 06:30:53 2018 Return-Path: Delivered-To: freebsd-arm@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 BDC2DEFD228 for ; Sun, 3 Jun 2018 06:30:53 +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 5D23372994 for ; Sun, 3 Jun 2018 06:30:53 +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 1fPMXS-0005vk-6G; Sun, 03 Jun 2018 08:30:50 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Warner Losh" , "Konstantin Belousov" Cc: freebsd-arm@freebsd.org 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> <20180602091606.63a1ab37.freebsd.ed.lists@sumeritec.com> <20180602150549.GA68197@www.zefox.net> <20180602193255.GA68908@www.zefox.net> <20180602210450.GK3789@kib.kiev.ua> Date: Sun, 03 Jun 2018 08:30:51 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20180602210450.GK3789@kib.kiev.ua> 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: 4b95630a2805109a2fafe329e7ec4fd6 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 06:30:53 -0000 On Sat, 02 Jun 2018 23:04:50 +0200, Konstantin Belousov wrote: > On Sat, Jun 02, 2018 at 02:39:00PM -0600, Warner Losh wrote: >> On Sat, Jun 2, 2018, 1:32 PM bob prohaska wrote: >> >> > On Sat, Jun 02, 2018 at 09:14:18AM -0600, Warner Losh wrote: >> > > >> > > Do you have r334508? It fixes the OOM falsely triggering. >> > > >> > At the moment sources are at 334456, world and kernel are at >> > 334276. >> > >> > Might it be feasible to stop the present buildworld, update >> > sources and then try to build a new kernel before building >> > world? >> > >> >> That's recent enough that you should be fine. There might be an lld vs >> binutils ld issue. There was on i386 recently, but I think it was i386 >> specific. It's a good risk. > > This happens on arm64 ? In fact, try this. > I did not even compiled the change. > > diff --git a/sys/arm64/arm64/swtch.S b/sys/arm64/arm64/swtch.S > index c9843303b1d..4c2c3aca583 100644 > --- a/sys/arm64/arm64/swtch.S > +++ b/sys/arm64/arm64/swtch.S > @@ -165,10 +165,9 @@ ENTRY(cpu_switch) > mov x0, x19 > /* > - * Release the old thread. This doesn't need to be a store-release > - * as the above dsb instruction will provide release semantics. > + * Release the old thread. > */ > - str x2, [x0, #TD_LOCK] > + stlr x2, [x0, #TD_LOCK] > #if defined(SCHED_ULE) && defined(SMP) > /* Spin if TD_LOCK points to a blocked_lock */ > ldr x2, =_C_LABEL(blocked_lock) Thanks, I will try. Is this patch for the TDQ_LOCKPTR assert in the subject? Or for the OOM message which hijacked this thread a little bit? As a data point: my RPI3 paniced again on the TDQ_LOCKPTR this night. Regards, Ronald.