Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757169AbdLPWd3 (ORCPT ); Sat, 16 Dec 2017 17:33:29 -0500 Received: from mail-vk0-f44.google.com ([209.85.213.44]:35551 "EHLO mail-vk0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756888AbdLPWd2 (ORCPT ); Sat, 16 Dec 2017 17:33:28 -0500 X-Google-Smtp-Source: ACJfBot2331ZrbRzcG1rqp5SS6lW+7+ftDHOBISAadqZA85kG9pjA+iRQP+xXq+4iG4gPT2oEWrgvxf0MhWDP/wCHXY= MIME-Version: 1.0 In-Reply-To: References: From: Balbir Singh Date: Sun, 17 Dec 2017 09:33:27 +1100 Message-ID: Subject: Re: powerpc64 kernel panic if you disable CONFIG_PPC_TRANSACTIONAL_MEM? To: Rob Landley Cc: Kernel Mailing List , "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 630 Lines: 15 On Sun, Dec 17, 2017 at 8:34 AM, Rob Landley wrote: > I just added a ppc64 target to https://github.com/landley/mkroot which > means I built 4.14 with the attached miniconfig and ran it with the > attached qemu command line, and it works fine as is but if you remove > the transactional mem line from the config the kernel panics instead > of launching a shell prompt: > > init[1]: unhandled signal 4 at 0000000010001a04 nip 0000000010001a04 > lr 000000001002ebe8 code 1 > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 > what does the instruction at 10001a04 look like? Balbir Singh.