From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Qoriq P5020 PowerPC board doesn't boot with the latest git version anymore
Date: Wed, 29 Nov 2017 11:35:49 +0100 [thread overview]
Message-ID: <0540fab0-b4c1-3328-beee-558311713c7e@xenosoft.de> (raw)
In-Reply-To: <87k1yazo21.fsf@concordia.ellerman.id.au>
Hi Michael,
Success! :-)
I disabled PREEMPT in the kernel config and I removed the spinlock patch
today. After that I compiled the RC1 again. With 'CONFIG_PREEMPT=n' and
without the spinlock patch, the RC1 boots on my Qoriq P5020 PowerPC
board without any problems.
Many thanks for your help. :-)
Cheers,
Christian
On 28 November 2017 at 11:37AM, Michael Ellerman wrote:
> Christian Zigotzky <chzigotzky@xenosoft.de> writes:
>
>> Hi All,
>>
>> I compiled the latest git kernel today. Unfortunately my Varisys Cyrus
>> Plus board still doesn't boot with the latest git kernel.
>>
>> After that I patched the kernel source code with the spinlock patch and
>> compiled the kernel again. With the spinlock patch, the latest git
>> kernel boots without any problems.
>>
>> Please find attached the spinlock patch.
> Can you remove the patch, and then build your kernel with
> CONFIG_PREEMPT=n.
>
> cheers
>
prev parent reply other threads:[~2017-11-29 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 22:27 Qoriq P5020 PowerPC board doesn't boot with the latest git version anymore Christian Zigotzky
2017-11-19 12:32 ` Christian Zigotzky
2017-11-19 16:57 ` Christian Zigotzky
2017-11-19 23:34 ` Christian Zigotzky
2017-11-22 11:28 ` Michael Ellerman
2017-11-22 12:44 ` Christian Zigotzky
2017-11-25 23:33 ` Christian Zigotzky
2017-11-28 10:37 ` Michael Ellerman
2017-11-29 10:35 ` Christian Zigotzky [this message]
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=0540fab0-b4c1-3328-beee-558311713c7e@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.