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=-1.0 required=3.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 4C7B2C072B5 for ; Fri, 24 May 2019 07:12:19 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (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 C43BC21841 for ; Fri, 24 May 2019 07:12:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C43BC21841 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=bugzilla.kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 459Hcb487MzDqdp for ; Fri, 24 May 2019 17:12:15 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=bugzilla.kernel.org (client-ip=198.145.29.98; helo=mail.wl.linuxfoundation.org; envelope-from=bugzilla-daemon@bugzilla.kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=bugzilla.kernel.org Received: from mail.wl.linuxfoundation.org (mail.wl.linuxfoundation.org [198.145.29.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 459Hb30tDpzDqcT for ; Fri, 24 May 2019 17:10:54 +1000 (AEST) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 6AA352880D for ; Fri, 24 May 2019 07:10:51 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 5E3182882E; Fri, 24 May 2019 07:10:51 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linuxppc-dev@lists.ozlabs.org Subject: [Bug 203699] New: Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=0x01501000 Date: Fri, 24 May 2019 07:10:50 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: AssignedTo platform_ppc-32@kernel-bugs.osdl.org X-Bugzilla-Product: Platform Specific/Hardware X-Bugzilla-Component: PPC-32 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: blocking X-Bugzilla-Who: mathieu.malaterre@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: platform_ppc-32@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version cf_kernel_version rep_platform op_sys cf_tree bug_status bug_severity priority component assigned_to reporter cf_regression Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Virus-Scanned: ClamAV using ClamSMTP 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: , Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" https://bugzilla.kernel.org/show_bug.cgi?id=3D203699 Bug ID: 203699 Summary: Kernel 5.2-rc1 fails to boot on a Mac Mini G4: dt_headr_start=3D0x01501000 Product: Platform Specific/Hardware Version: 2.5 Kernel Version: Kernel 5.2 Hardware: PPC-32 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: PPC-32 Assignee: platform_ppc-32@kernel-bugs.osdl.org Reporter: mathieu.malaterre@gmail.com Regression: No From: Christophe Leroy <> I found the issue. In order to be able to support KASAN, the setup of=20 segments have moved earlier in the boot. Your problem is a side effect=20 of this change. Function setup_disp_bat() is supposed to setup BAT3 for btext data. But setup_disp_bat() rely on someone setting in disp_BAT the values to=20 be loaded into BATs. This is done by btext_prepare_BAT() which is called=20 by bootx_init(). The problem is that bootx_init() is never called, so setup_disp_bat()=20 does nothing and the access to btext data is possible because the=20 bootloader has set an entry for it in the hash table. But by setting up the segment earlier, we break the bootloader hash=20 table, which shouldn't be an issue if the BATs had been set properly as=20 expected. The problematic commit is 215b823707ce ("powerpc/32s: set up an early=20 static hash table for KASAN)" Here is a dirty fix that works for me when CONFIG_KASAN is NOT set. Of course, the real fix has to be to setup the BATs properly, but I=20 won't have time to look at that before June. Maybe you can ? --=20 You are receiving this mail because: You are watching the assignee of the bug.=