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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C73AFC43381 for ; Mon, 25 Mar 2019 06:53:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 67B5A2075D for ; Mon, 25 Mar 2019 06:53:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=c-s.fr header.i=@c-s.fr header.b="SsJewLc+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729765AbfCYGxF (ORCPT ); Mon, 25 Mar 2019 02:53:05 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:10076 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729683AbfCYGxE (ORCPT ); Mon, 25 Mar 2019 02:53:04 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 44SQ223mkBz9v0Rt; Mon, 25 Mar 2019 07:52:58 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=SsJewLc+; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id XTaxsEE-PT-g; Mon, 25 Mar 2019 07:52:58 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 44SQ222g8Lz9v0Rr; Mon, 25 Mar 2019 07:52:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1553496778; bh=U6aYjqz/73cS/hlJOauTV57AvkWh/SqU5alecyRDuTU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=SsJewLc+FZm7Q871t4+5dm/+daz9m+iiWFbUiElaihL/jA2TH88ouLr6mBUO7wXng 5EXTCgTShpATeIlnGS3nzciPjJeAiHdsTvfZgf6/jqilt57BZMcw01IsPgxij1tw6u 7oS1s7emtb+FaTuO3fWgXmvB3zzY2tOnTuzKIcXU= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id C6FE28B7BC; Mon, 25 Mar 2019 07:53:02 +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 qtcAkNnR5onj; Mon, 25 Mar 2019 07:53:02 +0100 (CET) Received: from PO15451 (po15451.idsi0.si.c-s.fr [172.25.231.2]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 84FD88B74F; Mon, 25 Mar 2019 07:53:02 +0100 (CET) Subject: Re: Regression in 5.1.0-rc2: PowerBook G4 Aluminum fails to boot - bisected to commit 0df977eafc792 To: Larry Finger , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , ppc-dev Cc: LKML References: From: Christophe Leroy Message-ID: Date: Mon, 25 Mar 2019 07:53:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 25/03/2019 à 01:49, Larry Finger a écrit : > A build of kernel 5.1.0-rc2 resulted in a failure to boot on my > PowerBook G4 Aluminum. The bootstrap loads the initial kernel and issues > the appropriate start, but the machine hangs at that point. Can you please be more explicit ? What do you mean by "issues the appropriate start" ? What is "that point" ? Any messages on the console ? Thanks Christophe > > The problem does not depend on the choice of PPC32 processor type. This > machine has a 7447A according to /proc/cpuinfo. > > The problem was bisected to the following: > > commit 0df977eafc792a5365a7f81d8d5920132e03afad > Author: Christophe Leroy > Date:   Thu Feb 21 10:37:54 2019 +0000 > >     powerpc/6xx: Don't use SPRN_SPRG2 for storing stack pointer while > in RTAS > >     When calling RTAS, the stack pointer is stored in SPRN_SPRG2 >     in order to be able to restore it in case of machine check in RTAS. > >     As machine check is not a perfomance critical path, this patch >     frees SPRN_SPRG2 by using a field in thread struct instead. > >     Signed-off-by: Christophe Leroy >     Signed-off-by: Michael Ellerman > > I reverted this patch and found that the system began execution, and > then failed, likely due to the reassignment of SPRN_SPRG2. > > I had found this problem with 5.1.0-rc1, but -rc2 was out by the time I > finished the bisection. Unfortunately, none of the changes in -rc2 fixed > the problem. > > Attached is the .config that I used. > > Thanks, > > Larry