From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7385917E0 for ; Mon, 5 Dec 2022 08:48:26 +0000 (UTC) Received: (Authenticated sender: philippe.gerum@sourcetrek.com) by mail.gandi.net (Postfix) with ESMTPSA id 32EBF1BF217; Mon, 5 Dec 2022 08:48:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xenomai.org; s=gm1; t=1670230099; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KJ2yo8UcZpArZ/bkvD/FpXKPOT3JVkJdgFsPIvOLDlI=; b=WKiYdB8d8IduGLSgMGO6yInhr0o6Ok7ySiiuZbpNZD+1CcYkVg/T1i3AAQABMNGZ3rOMid qS1Cx0cU6exFjCNe9PDhBi58Zm46pIiCAZAtA2k5Q8Nikvg+XRtC2/DGNFPWv6Z222bvg7 obYH1lQCp42UwqAUJH5EQrSvsO/QuTm6kgKpOaqZ+GBo5ztx5CHpBy6BCueHuu5EKALyeb LSz+j4LgkGDlleAl435FnaCyzUXaBIzaKJXDv7rUvh4PRt9XMJbngzpSTf9IPeo6IRY45g QQbvACGyJ68Ql0+vogZZXnBjJFKG9shf86/XT4ulhSIfK38Sh5zkB34PgLQNhg== References: <877czothz0.fsf@xenomai.org> <87h6yj6mvg.fsf@xenomai.org> <0082bff2d91b0125ac60050159d3003e64b45bffa35e0c4f0ed9799e38b97b8c@mu> <87h6ygwi2l.fsf@xenomai.org> <875yevw5ln.fsf@xenomai.org> <871qpiw3zd.fsf@xenomai.org> <87wn797rj3.fsf@xenomai.org> <87cz917m8z.fsf@xenomai.org> <87v8mshg4n.fsf@xenomai.org> <87r0xgh4n2.fsf@xenomai.org> <87mt83zano.fsf@xenomai.org> <87iliryrgg.fsf@xenomai.org> User-agent: mu4e 1.6.6; emacs 28.1 From: Philippe Gerum To: Russell Johnson Cc: Bryan Butler , "xenomai@lists.linux.dev" , Shawn McManus Subject: Re: [External] - Re: EVL Memory Date: Mon, 05 Dec 2022 09:45:24 +0100 In-reply-to: Message-ID: <87a642z166.fsf@xenomai.org> Precedence: bulk X-Mailing-List: xenomai@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Russell Johnson writes: > [[S/MIME Signed Part:Undecided]] > Just ran the latest kernel from the next branch with the lockdep turned back > on and ftrace off for now. Good news is that I no longer see a boosting > issue. Thanks again for the work to track that down. All that is left at the > moment is one lockdep kernel splat which may not be important, but I > attached anyway. > I'll have a look at this one too, this is depending on CONFIG_DEBUG_LOCKDEP. I have not been able to reproduce it yet. ftrace should be back to normal as well, I fixed the recently broken tracepoint causing crashes. -- Philippe.