From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mac User <userm57@yahoo.com>
Cc: Rob Herring <robh+dt@kernel.org>,
fthain@telegraphics.com.au, Frank Rowand <frank.rowand@sony.com>,
Chintan Pandya <cpandya@codeaurora.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: v4.17 regression: PowerMac G3 won't boot, was Re: [PATCH v5 1/3] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()
Date: Sat, 01 Sep 2018 14:53:43 +1000 [thread overview]
Message-ID: <46510acd915b463f1944adb0a7e60c10460f9d7e.camel@kernel.crashing.org> (raw)
In-Reply-To: <d3f5a177-10ee-1696-1ddf-41b7db62de6c@yahoo.com>
On Fri, 2018-08-31 at 06:28 -0600, Mac User wrote:
> On 8/30/18 10:49 PM, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2018-08-31 at 14:35 +1000, Benjamin Herrenschmidt wrote:
> >
> > ...
> > Assuming you are using BootX (or miBoot), can you try this patch ?
>
> Yes, I'm using BootX.
>
> Thanks to Finn for applying the patch (I wouldn't have been sure
> which source tree to apply it to).
>
> Thepatched kernel (Finn's vmlinux-4.18.0-00001-gd44cf7e41c19)
> boots normally on my Beige G3 Desktop using BootX.
>
> Thanks for working on this!
Well it's still a sign of something wrong with the new code, my patch
just band-aids by creating fake phandles. I would be interesting to
figure out what causes the new code to barf.
Cheers,
Ben.
next prev parent reply other threads:[~2018-09-01 4:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1520208889-3908-1-git-send-email-frowand.list@gmail.com>
[not found] ` <1520208889-3908-2-git-send-email-frowand.list@gmail.com>
2018-08-30 0:44 ` v4.17 regression: PowerMac G3 won't boot, was Re: [PATCH v5 1/3] of: cache phandle nodes to reduce cost of of_find_node_by_phandle() Finn Thain
2018-08-30 1:05 ` Rob Herring
2018-08-31 2:39 ` Mac User
2018-08-31 4:35 ` Benjamin Herrenschmidt
2018-08-31 4:49 ` Benjamin Herrenschmidt
2018-08-31 12:28 ` Mac User
2018-08-31 23:36 ` Finn Thain
2018-09-01 4:54 ` Benjamin Herrenschmidt
2018-09-01 4:53 ` Benjamin Herrenschmidt [this message]
2018-08-31 4:49 ` Benjamin Herrenschmidt
2018-08-31 4:36 ` Frank Rowand
2018-08-31 4:58 ` Benjamin Herrenschmidt
2018-09-09 17:04 ` Benjamin Herrenschmidt
2018-09-09 23:52 ` Frank Rowand
2018-09-10 12:53 ` Rob Herring
2018-09-11 15:53 ` Frank Rowand
[not found] ` <abb0dec2-da3a-2c04-0e9f-28851b22cf75@yahoo.com>
2018-09-12 0:15 ` Finn Thain
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=46510acd915b463f1944adb0a7e60c10460f9d7e.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=cpandya@codeaurora.org \
--cc=frank.rowand@sony.com \
--cc=fthain@telegraphics.com.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=userm57@yahoo.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).