linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 12:15:14 +1100	[thread overview]
Message-ID: <8f112153558ae8ffdefba905d83329c8e896d3a9.camel@kernel.crashing.org> (raw)
In-Reply-To: <20190115224945.fvyrjjf3mjywq7u6@atom2.tmux.org>

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.

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.

Cheers,
Ben.



  reply	other threads:[~2019-01-16  1:17 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 [this message]
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
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=8f112153558ae8ffdefba905d83329c8e896d3a9.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).