linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Darren Stevens <darren@stevens-zone.net>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Christoph Hellwig <hch@lst.de>, "R.T.Dickinson" <rtd2@xtra.co.nz>
Subject: Re: Boot issue with the latest Git kernel
Date: Thu, 4 Jun 2020 17:46:45 +0200	[thread overview]
Message-ID: <E5F27F7E-A3C0-4ED5-97C7-B9F2FBA118D2@xenosoft.de> (raw)
In-Reply-To: <f7f1b233-6101-2316-7996-4654586b7d24@csgroup.eu>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hello Christophe,

I tested it on my Nemo board with a P.A. Semi PA6T CPU [1], on my Cyrus+ board with a FSL P5040 CPU [2] and in a virtual e5500 QEMU machine. You can find the kernel configs in the following package.

Link: http://www.xenosoft.de/linux-image-5.8-alpha1-X1000_X5000.tar.gz

Cheers,
Christian

[1] https://en.m.wikipedia.org/wiki/AmigaOne_X1000
[2] https://www.amigaos.net/hardware/133/amigaone-x5000


> On 4. Jun 2020, at 16:29, Christophe Leroy <christophe.leroy@csgroup.eu> wrote:
> 
> 
> 
>> Le 04/06/2020 à 16:26, Christophe Leroy a écrit :
>> Hi,
>>> Le 04/06/2020 à 16:16, Christian Zigotzky a écrit :
>>> Hi All,
>>> 
>>> I tested the latest Git kernel today. [1]. Unfortunately it doesn't boot on my PowerPC machines.
>>> 
>>> Could you please test the latest Git kernel with your PowerPC machine?
>>> 
>>> BTW, it doesn't boot in a virtual QEMU PowerPC machine either.
>>> 
>> Which machine/platform ? Which defconfig are you using ?
> 
> 
> And are you able to perform a 'git bisect' to identify the guilty commit ?
> 
> Thanks
> Christophe

[-- Attachment #2: Type: text/html, Size: 2635 bytes --]

  reply	other threads:[~2020-06-04 21:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:16 Boot issue with the latest Git kernel Christian Zigotzky
2020-06-04 14:26 ` Christophe Leroy
2020-06-04 14:29   ` Christophe Leroy
2020-06-04 15:46     ` Christian Zigotzky [this message]
2020-06-04 15:53     ` Christian Zigotzky
2020-06-04 17:15       ` Christophe Leroy
2020-06-05 16:23         ` Christian Zigotzky
2020-06-07 13:27           ` Christian Zigotzky
2020-06-07 14:07           ` Aneesh Kumar K.V
2020-06-09 22:18             ` PowerPC KVM-PR issue Christian Zigotzky
2020-06-10  9:06               ` Christian Zigotzky
2020-06-10 11:23                 ` Christian Zigotzky
2020-06-11 14:47                   ` Christian Zigotzky
2020-06-12 13:01                     ` Christian Zigotzky
2020-06-14  8:50                       ` Nicholas Piggin
2020-06-14 12:53                       ` Nicholas Piggin
2020-06-14 14:52                         ` Christian Zigotzky
2020-06-14 23:39                           ` Christian Zigotzky
2020-06-15  7:34                             ` Christian Zigotzky
2020-06-25  9:38                             ` 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=E5F27F7E-A3C0-4ED5-97C7-B9F2FBA118D2@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=darren@stevens-zone.net \
    --cc=hch@lst.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).