From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"npiggin@gmail.com" <npiggin@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant McEwan <grant.mcewan@alliedtelesis.co.nz>
Subject: Re: SMP lockup at boot on Freescale/NXP T2080 (powerpc 64)
Date: Thu, 8 Aug 2019 10:46:35 +0200 [thread overview]
Message-ID: <b0ad453c-3a2b-6dd5-7bfc-5e275aa7bf62@c-s.fr> (raw)
In-Reply-To: <1565141097.19352.12.camel@alliedtelesis.co.nz>
Le 07/08/2019 à 03:24, Chris Packham a écrit :
> On Wed, 2019-08-07 at 11:13 +1000, Michael Ellerman wrote:
>> Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
>>>
>>> On Tue, 2019-08-06 at 21:32 +1000, Michael Ellerman wrote:
>>> The difference between a working and non working defconfig is
>>> CONFIG_PREEMPT specifically CONFIG_PREEMPT=y makes my system hang
>>> at
>>> boot.
>>>
>>> Is that now intentionally prohibited on 64-bit powerpc?
>> It's not prohibitied, but it probably should be because no one really
>> tests it properly. I have a handful of IBM machines where I boot a
>> PREEMPT kernel but that's about it.
>>
>> The corenet configs don't have PREEMPT enabled, which suggests it was
>> never really supported on those machines.
>>
>> But maybe someone from NXP can tell me otherwise.
>>
>
> I think our workloads need CONFIG_PREEMPT=y because our systems have
> switch ASIC drivers implemented in userland and we need to be able to
> react quickly to network events in order to prevent loops. We have seen
> instances of this not happening simply because some other process is in
> the middle of a syscall.
>
> One thing I am working on here is a setup with a few vendor boards and
> some of our own kit that we can test the upstream kernels on. Hopefully
> that'd make these kinds of reports more timely rather than just
> whenever we decide to move to a new kernel version.
>
>
The defconfig also sets CONFIG_DEBUG_PREEMPT. Have you tried without
CONFIG_DEBUG_PREEMPT ?
Christophe
next prev parent reply other threads:[~2019-08-08 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 2:06 SMP lockup at boot on Freescale/NXP T2080 (powerpc 64) Chris Packham
2019-08-05 8:47 ` Chris Packham
2019-08-06 11:32 ` Michael Ellerman
2019-08-06 23:50 ` Chris Packham
2019-08-07 1:13 ` Michael Ellerman
2019-08-07 1:24 ` Chris Packham
2019-08-08 8:46 ` Christophe Leroy [this message]
2019-08-08 13:12 ` Christophe Leroy
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=b0ad453c-3a2b-6dd5-7bfc-5e275aa7bf62@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=grant.mcewan@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
/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).