From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tobias Ulmer <tobiasu@tmux.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: G5 Quad hangs early on 4.20.2 / 5.0-rc2+
Date: Fri, 18 Jan 2019 09:32:07 +1100 [thread overview]
Message-ID: <ae9672a789b29a546c12149650f0a7f6ab6b762d.camel@kernel.crashing.org> (raw)
In-Reply-To: <20190117094214.26t72sdqknfzxvlx@atom2.tmux.org>
On Thu, 2019-01-17 at 10:42 +0100, Tobias Ulmer wrote:
> On Wed, Jan 16, 2019 at 12:15:14PM +1100, Benjamin Herrenschmidt wrote:
> > On Tue, 2019-01-15 at 23:49 +0100, Tobias Ulmer wrote:
> > > Hi,
> > >
> > > both the latest stable 4.20.2 and 5.0 rc2+ hang early on the G5 Quad.
> > >
> > > Surely I'm not the first to run into this, but I couldn't find any
> > > discussion or bug report. Sorry if you're already aware.
> > >
> > > You can see it hang here (5.0 rc2+, 4.20.2 is nearly identical) until
> > > the watchdog triggers a reboot:
> > >
> > > https://i.imgur.com/UiCVRuG.jpg
> > >
> > > If I had to make an uneducated guess, it seems to boot into the same
> > > codepath twice (mpic was already initialized, then it starts again right
> > > after smp bringup). Maybe on a second CPU?
> > >
> > > To narrow it down a little, my last known good was 4.18.9
> >
> > I don't think it's an MPIC related problem but it does appear to hang
> > about when interrupts get turned on.
>
> When they get turned on for the second time, for some reason. You can see the
> end of the first time just on top of the screen.
No, that top of screen init is something else.
> It repeats part of the startup initialization right after it's done with
> smp bringup.
That's just the BootX console hanging over to the main console and
replaying the messages I think.
> > I have one of these critters in the office, but I'm working remotely
> > this week so I won't be able to dig into this until next week.
> >
> > It might help if you could bisect in the meantime.
>
> I'm bisecting it now, but it's slow going since I don't have much time
> to babysit the machine. The problem shows up somewhere between v4.19 and
> v4.20.
Ok, thanks.
I'll be back on monday or tuesday, let me know where you got up to then
and I'll take it from there. Also email me your .config please.
Cheers,
Ben.
> > Cheers,
> > Ben.
> >
> >
next prev parent reply other threads:[~2019-01-17 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 22:49 G5 Quad hangs early on 4.20.2 / 5.0-rc2+ Tobias Ulmer
2019-01-16 1:15 ` Benjamin Herrenschmidt
2019-01-17 9:42 ` Tobias Ulmer
2019-01-17 13:38 ` Michael Ellerman
2019-01-17 22:32 ` Benjamin Herrenschmidt [this message]
2019-01-18 0:51 ` Tobias Ulmer
2019-01-18 10:09 ` Mathieu Malaterre
2019-01-16 6:56 ` Michael Ellerman
2019-01-18 2:22 ` Paul Mackerras
2019-01-18 9:44 ` Tobias Ulmer
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=ae9672a789b29a546c12149650f0a7f6ab6b762d.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tobiasu@tmux.org \
/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).