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=-12.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 69C9FC433DB for ; Tue, 22 Dec 2020 12:19:28 +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 7F42620449 for ; Tue, 22 Dec 2020 12:19:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7F42620449 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xenosoft.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4D0b4C5JttzDqDq for ; Tue, 22 Dec 2020 23:19:23 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.helo=mo4-p01-ob.smtp.rzone.de (client-ip=81.169.146.166; helo=mo4-p01-ob.smtp.rzone.de; envelope-from=chzigotzky@xenosoft.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=xenosoft.de Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=xenosoft.de header.i=@xenosoft.de header.a=rsa-sha256 header.s=strato-dkim-0002 header.b=UBmNigje; dkim-atps=neutral Received: from mo4-p01-ob.smtp.rzone.de (mo4-p01-ob.smtp.rzone.de [81.169.146.166]) (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 4D0b0d0x0JzDqDD for ; Tue, 22 Dec 2020 23:16:11 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1608639364; s=strato-dkim-0002; d=xenosoft.de; h=In-Reply-To:Date:Message-ID:References:Cc:To:From:Subject:From: Subject:Sender; bh=kiNm4DXGXLmdmYW3w3gKomiOkcikhrWnMZqNuMN+4no=; b=UBmNigjeEZxgrD5ioXM65ByCcJxJ65eQ8rwqDycFLVI5AO0mc2TsguQPveOV0YNBQD cQJczUKKNrRKvR93Yakv/nZHqw37Zcz1Lx+7bAKo+JHRRqLK2yfa1ZtMS2nXU9eWroa1 uYSxdGwdXvINBHnK+vbNQ0TQgWTikj5GAas/5Pw7EkLmaC1Lc6uUDtLKzQpgwl/Jf3mk 8UUMUKDL25AhQybG4gSqbtXJiZmmtr7QdXH20urtdF+N73Ui82bQgUFaDhoChMHrygIW 90lyF+LDeYwltHXH3D51LEM85Z8HFbZ660bjJzvJnclaiQwIBrRFs2lYjvxO2l24GRIK PCuw== X-RZG-AUTH: ":L2QefEenb+UdBJSdRCXu93KJ1bmSGnhMdmOod1DhGM4l4Hio94KKxRySfLxnHfJ+Dkjp5DdBJSrwuuqxvPgGLCCSDVtFoWTYRiXBE8s7vg==" X-RZG-CLASS-ID: mo00 Received: from Christians-iMac.fritz.box by smtp.strato.de (RZmta 47.10.2 AUTH) with ESMTPSA id D06d08wBMCFu2TR (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 22 Dec 2020 13:15:56 +0100 (CET) Subject: Re: GIT kernel with the PowerPC updates 5.11-1 doesn't boot on a FSL P5040 board and in a virtual e5500 QEMU machine From: Christian Zigotzky To: Christophe Leroy , Denis Kirjanov References: <7543ec1a-005d-f868-5607-448baaccb88a@csgroup.eu> <8d25f58b-a7bf-4413-b8cc-ed3bd0107263@xenosoft.de> Message-ID: Date: Tue, 22 Dec 2020 13:15:55 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <8d25f58b-a7bf-4413-b8cc-ed3bd0107263@xenosoft.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: de-DE 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 , linuxppc-dev , "R.T.Dickinson" , mad skateman Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Hello, I compiled the latest Git kernel today and unfortunately the boot issue still exists. I was able to reduce the patch for reverting the changes. In this way we know the problematic code now. vdso-v2.patch: diff -rupN a/arch/powerpc/kernel/vdso32/vgettimeofday.c b/arch/powerpc/kernel/vdso32/vgettimeofday.c --- a/arch/powerpc/kernel/vdso32/vgettimeofday.c    2020-12-19 00:01:16.829846652 +0100 +++ b/arch/powerpc/kernel/vdso32/vgettimeofday.c    2020-12-19 00:00:37.817369691 +0100 @@ -10,12 +10,6 @@ int __c_kernel_clock_gettime(clockid_t c      return __cvdso_clock_gettime32_data(vd, clock, ts);  } -int __c_kernel_clock_gettime64(clockid_t clock, struct __kernel_timespec *ts, -                   const struct vdso_data *vd) -{ -    return __cvdso_clock_gettime_data(vd, clock, ts); -} -  int __c_kernel_gettimeofday(struct __kernel_old_timeval *tv, struct timezone *tz,                  const struct vdso_data *vd)  { ---- With this patch, the uImage boots without any problems on my FSL P5040 board and in a virtual e5500 QEMU machine. Please check the problematic code. Thanks, Christian On 19 December 2020 at 01:33pm, Christian Zigotzky wrote: > On 19 December 2020 at 07:49am, Christophe Leroy wrote: >> >> >> Le 18/12/2020 à 23:49, Christian Zigotzky a écrit : >>> On 18 December 2020 at 10:25pm, Denis Kirjanov wrote: >>>  > >>>  > >>>  > On Friday, December 18, 2020, Christian Zigotzky >>> wrote: >>>  > >>>  >     Hello, >>>  > >>>  >     I compiled the latest Git kernel with the new PowerPC updates >>> 5.11-1 [1] today. Unfortunately this kernel doesn't boot on my FSL >>> P5040 board [2] and in a virtual e5500 QEMU machine [3]. >>>  > >>>  >     I was able to revert the new PowerPC updates 5.11-1 [4] and >>> after a new compiling, the kernel boots without any problems on my >>> FSL P5040 board. >>>  > >>>  >     Please check the new PowerPC updates 5.11-1. >>>  > >>>  > >>>  > Can you bisect the bad commit? >>>  > >>> Hello Denis, >>> >>> I have bisected [5] and d0e3fc69d00d1f50d22d6b6acfc555ccda80ad1e >>> (powerpc/vdso: Provide __kernel_clock_gettime64() on vdso32) [6] is >>> the first bad commit. >>> >>> I was able to revert this bad commit and after a new compiling, the >>> kernel boots without any problems. >> >> That's puzzling. >> >> Can you describe the symptoms exactly ? What do you mean by "the >> kernel doesn't boot" ? Where and how does it stops booting ? > It stops during the disk initialisation. >> >> This commit only adds a new VDSO call, for getting y2038 compliant >> time. At the time I implemented it there was no libc using it yet. Is >> your libc using it ? > I tested it with ubuntu MATE 16.04.7 LTS (32-bit userland + 64-bit > kernel) and with Debian Sid (MintPPC and Fienix 32-bit userland + > 64-bit kernel) on my FSL P5040 board and in a virtual e5500 QEMU > machine. How can I figure out if the libc use it? >> >> Where can I find all the elements you are using to boot with QEMU ? >> Especially the file MintPPC32-X5000.img > Download: http://www.xenosoft.de/MintPPC32-X5000.tar.gz (md5sum: > b31c1c1ca1fcf5d4cdf110c4bce11654) The password for both 'root' and > 'mintppc' is 'mintppc'. > > QEMU command with KVM on my P5040 board: qemu-system-ppc64 -M ppce500 > -cpu e5500 -enable-kvm -m 1024 -kernel uImage -drive > format=raw,file=MintPPC32-X5000.img,index=0,if=virtio -netdev > user,id=mynet0 -device e1000,netdev=mynet0 -append "rw root=/dev/vda" > -device virtio-vga -device virtio-mouse-pci -device > virtio-keyboard-pci -device pci-ohci,id=newusb -device > usb-audio,bus=newusb.0 -smp 4 > > QEMU command without KVM on macOS Intel: qemu-system-ppc64 -M ppce500 > -cpu e5500 -m 1024 -kernel uImage -drive > format=raw,file=MintPPC32-X5000.img,index=0,if=virtio -netdev > user,id=mynet0 -device virtio-net-pci,netdev=mynet0 -append "rw > root=/dev/vda" -device virtio-vga -usb -device usb-ehci,id=ehci > -device usb-tablet -device virtio-keyboard-pci -smp 4 -vnc :1 >> >> Can you also share you kernel config > See attachment. >> >> Thanks >> Christophe > Thanks > Christian >