From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9545EC433EF for ; Tue, 9 Nov 2021 16:13:51 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1275D60FD8 for ; Tue, 9 Nov 2021 16:13:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 1275D60FD8 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=csgroup.eu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4HpY252KYrz3cCQ for ; Wed, 10 Nov 2021 03:13:49 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=csgroup.eu (client-ip=93.17.235.10; helo=pegase2.c-s.fr; envelope-from=christophe.leroy@csgroup.eu; receiver=) Received: from pegase2.c-s.fr (pegase2.c-s.fr [93.17.235.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4HpY1c54hnz2yK3 for ; Wed, 10 Nov 2021 03:13:22 +1100 (AEDT) Received: from localhost (mailhub3.si.c-s.fr [172.26.127.67]) by localhost (Postfix) with ESMTP id 4HpY1V1gm2z9sSJ; Tue, 9 Nov 2021 17:13:18 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from pegase2.c-s.fr ([172.26.127.65]) by localhost (pegase2.c-s.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rY5l2W1lpe1v; Tue, 9 Nov 2021 17:13:18 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase2.c-s.fr (Postfix) with ESMTP id 4HpY1V0vl4z9sSG; Tue, 9 Nov 2021 17:13:18 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 0A9418B77A; Tue, 9 Nov 2021 17:13:18 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id G4AVCO6bIdsl; Tue, 9 Nov 2021 17:13:17 +0100 (CET) Received: from [192.168.233.192] (unknown [192.168.233.192]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 827828B767; Tue, 9 Nov 2021 17:13:17 +0100 (CET) Message-ID: Date: Tue, 9 Nov 2021 17:13:19 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: [FSL P50x0] Cyrus+ board doesn't boot with the PowerPC updates 5.16-1 Content-Language: fr-FR To: Christian Zigotzky References: <3eedbe78-1fbd-4763-a7f3-ac5665e76a4a@xenosoft.de> <15731ad7-83ff-c7ef-e4a1-8b11814572c2@xenosoft.de> <17e37b22-5839-0e3a-0dbf-9c676adb0dec@xenosoft.de> From: Christophe Leroy In-Reply-To: <17e37b22-5839-0e3a-0dbf-9c676adb0dec@xenosoft.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Darren Stevens , "R.T.Dickinson" , mad skateman , Matthew Leaman , linuxppc-dev , Christian Zigotzky Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Le 08/11/2021 à 15:48, Christian Zigotzky a écrit : > Hi Christophe, > > The Cyrus+ board with FSL P50x0 SoC [1] doesn't boot with the PowerPC > updates 5.16-1 [2]. > > I was able to revert the new PowerPC updates 5.16-1 [2]. After a new > compiling, the kernel boots without any problems on the Cyrus+ board. > > I bisected today [3]. 52bda69ae8b5102fe08c9db10f4a1514478e07d3 > (powerpc/fsl_booke: Tell map_mem_in_cams() if init is done) [4] is the > first bad commit. Yes, the bad commit is obviously ... bad. That commit should have just added an additional argument set to 'true' while not changing anything else. Apparently it went wrong in mm/nohash/tlb.c I will send a fixup early next week as I'm AFK at the moment. Christophe