From: David Lamparter <equinox@diac24.net>
To: York Sun <york.sun@nxp.com>
Cc: Scott Wood <oss@buserror.net>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Scott Wood <swood@redhat.com>,
David Lamparter <equinox@diac24.net>
Subject: Re: [PATCH ppc-next] powerpc/fsl-booke: don't load early TLB at once
Date: Mon, 1 Oct 2018 15:51:26 +0200 [thread overview]
Message-ID: <20181001135126.GP487685@eidolon.nox.tf> (raw)
In-Reply-To: <DB7PR04MB4298007BF024E96CB6B2A02D9A120@DB7PR04MB4298.eurprd04.prod.outlook.com>
(Sorry about the delay on my end, deadlines ...)
On Fri, Sep 21, 2018 at 06:07:48PM +0000, York Sun wrote:
> On 09/21/2018 10:47 AM, Scott Wood wrote:
> > On Fri, 2018-09-21 at 17:40 +0000, York Sun wrote:
> >> On 09/20/2018 05:31 PM, Scott Wood wrote:
> >>> On Fri, 2018-09-21 at 00:48 +0200, David Lamparter wrote:
> >>>> My dusty old P4080DS just completely fails to boot (no output at all)
> >>>> without this revert. I have no clue what's going on here, I just
> >>>> bisected it down and since it looks like an optimization to me I just
> >>>> reverted it - and voilá, the P4080 boots again.
> >>>
> >>> It's not an optimization; it was required to get kdump working, at least
> >>> for certain choices of crash kernel location.
[...]
> >>> York, can you try booting the latest kernel on p4080ds?
[...]
>
> Thanks for the instruction. Linux comes up OK with corenet32_smp_defconfig.
>
> root@p4080ds:~# uname -a
> Linux p4080ds 4.19.0-rc4-00206-ga27fb6d #1 SMP Fri Sep 21 10:56:36 PDT
> 2018 ppc GNU/Linux
Well, shoot. I guess the next likely thing is that I have something
weird enabled in my .config, so I'll try booting corenet32_smp_defconfig
on my P4080DS. (I vaguely think I did that at some point but I can't
swear to it so I'll just retry.) If that doesn't boot, could either of
you provide me with your built uImage so I can exclude toolchain
stupidity?
=> I'll send another mail when I got to try corenet32_smp_defconfig.
Aaaand, during the past week I noticed this is a rev1.0 P4080 chip, which
apparently only exists on some early P4080DS boards - and Freescale even
did a replacement program to get rev2.0 boards out (I guess this one was
sitting in some broom closet.) I don't have access to erratas for this,
I only know the entire QMan/FMan stuff is royally f*cked - no idea
whether the PPC core has issues too.
FWIW, my board is running perfectly stable with that patch I posted and
I'll just carry it locally if it's an issue for this one specific board
I have here. I just don't have sufficient information to tell if that
is indeed the case.
Thanks a lot for your input and help,
-David
next prev parent reply other threads:[~2018-10-01 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 22:48 [PATCH ppc-next] powerpc/fsl-booke: don't load early TLB at once David Lamparter
2018-09-21 0:31 ` Scott Wood
2018-09-21 1:00 ` David Lamparter
2018-09-22 5:45 ` Scott Wood
2018-10-01 14:26 ` David Lamparter
2018-09-21 17:40 ` York Sun
2018-09-21 17:47 ` Scott Wood
2018-09-21 18:07 ` York Sun
2018-10-01 13:51 ` David Lamparter [this message]
2018-09-24 5:15 ` Michael Ellerman
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=20181001135126.GP487685@eidolon.nox.tf \
--to=equinox@diac24.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=swood@redhat.com \
--cc=york.sun@nxp.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).