linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Tobias Ulmer <tobiasu@tmux.org>, linuxppc-dev@ozlabs.org
Subject: Re: G5 Quad hangs early on 4.20.2 / 5.0-rc2+
Date: Wed, 16 Jan 2019 17:56:39 +1100	[thread overview]
Message-ID: <87r2ddxf88.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190115224945.fvyrjjf3mjywq7u6@atom2.tmux.org>

Tobias Ulmer <tobiasu@tmux.org> writes:
> 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.

Actually you're probably the first to hit it :)

I have a quad but it never gets to openfirmware and I haven't had time
to look into why.

My iMac G5 and dual G5 are booting OK though.

> 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?

Can you compare to a working boot log, does that give us any clues?

Can you post your full .config for the non-working case.

cheers

  parent reply	other threads:[~2019-01-16  7:00 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
2019-01-18  0:51       ` Tobias Ulmer
2019-01-18 10:09         ` Mathieu Malaterre
2019-01-16  6:56 ` Michael Ellerman [this message]
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=87r2ddxf88.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --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).