All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
	mad skateman <madskateman@gmail.com>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
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
Date: Fri, 18 Dec 2020 23:49:25 +0100	[thread overview]
Message-ID: <ad682b81-60f6-4e13-46f4-39539de2be72@xenosoft.de> (raw)
In-Reply-To: <CAOJe8K3+j3kGHYhSfjyywXcSQFca0Y370LiAa2uVsW5znUPsAA@mail.gmail.com>

On 18 December 2020 at 10:25pm, Denis Kirjanov wrote:
 >
 >
 > On Friday, December 18, 2020, Christian Zigotzky 
<chzigotzky@xenosoft.de> 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.

Thanks,
Christian

[5] https://forum.hyperion-entertainment.com/viewtopic.php?p=52077#p52077
[6] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d0e3fc69d00d1f50d22d6b6acfc555ccda80ad1e

 >
 >
 >
 >     Thanks,
 >     Christian
 >
 >
 >     [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8a5be36b9303ae167468d4f5e1b3c090b9981396
 >     [2] http://wiki.amiga.org/index.php?title=X5000
 >     [3] 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
 >     [4] git revert 8a5be36b9303ae167468d4f5e1b3c090b9981396 -m 1
 >


  reply	other threads:[~2020-12-18 22:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 17:45 GIT kernel with the PowerPC updates 5.11-1 doesn't boot on a FSL P5040 board and in a virtual e5500 QEMU machine Christian Zigotzky
2020-12-18 21:25 ` Denis Kirjanov
2020-12-18 22:49   ` Christian Zigotzky [this message]
2020-12-19  0:38     ` Christian Zigotzky
2020-12-19  6:49     ` Christophe Leroy
2020-12-19 12:33       ` Christian Zigotzky
2020-12-22 12:15         ` Christian Zigotzky
2020-12-22 13:14         ` Michael Ellerman
2020-12-24 15:01           ` Christian Zigotzky
2021-01-27 16:07 ` FSL P5040: KVM HV doesn't work with the RC5 of kernel 5.11 Christian Zigotzky
2021-02-01  8:29   ` Christian Zigotzky
2021-02-01  8:29     ` Christian Zigotzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ad682b81-60f6-4e13-46f4-39539de2be72@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=kda@linux-powerpc.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=rtd2@xtra.co.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.