linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org, Hugh Dickins <hughd@google.com>
Subject: Re: powerpc/pci sysdata batch hangs G5 boot
Date: Sun, 20 Mar 2011 20:10:10 +1100	[thread overview]
Message-ID: <1300612210.2402.1.camel@pasglop> (raw)
In-Reply-To: <AANLkTikMbMqSRpt9gCrHgzpJuRCGL7rfLAs6erJL0Qjc@mail.gmail.com>

On Sun, 2011-03-20 at 00:25 -0600, Grant Likely wrote:
> On Sat, Mar 19, 2011 at 9:41 PM, Hugh Dickins <hughd@google.com> wrote:
> > Hi Grant,
> >
> > I've been unable to boot mmotm on the G5 for a few weeks; and now that
> > the problem has reached Linus, I've bisected and it converges on your:
> >
> > commit b5d937de0367d26f65b9af1aef5f2c34c1939be0
> >    powerpc/pci: Make both ppc32 and ppc64 use sysdata for pci_controller
> 
> Hi Hugh,
> 
> Thanks for the testing.  I don't have access to a G5 unfortunately.
> Are you able to capture the good/bad console output and send it to me?
>  A digital photo would be fine if you can't grab the raw text.  Add
> #define DEBUG to the top of arch/powerpc/kernel/pci-common.c above the
> #includes too if you don't mind.
> 
> I'm investigating on my end.  I suspect that I've messed up retrieval
> of the hose pointer.

Hrm, you merged that already ? I would have liked to have a chance to at
least test and review properly...

Oh well, I have G5's here, I'll see if I can find what's wrong tomorrow.

Cheers,
Ben.

      reply	other threads:[~2011-03-20  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20  3:41 powerpc/pci sysdata batch hangs G5 boot Hugh Dickins
2011-03-20  6:25 ` Grant Likely
2011-03-20  9:10   ` Benjamin Herrenschmidt [this message]

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=1300612210.2402.1.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hughd@google.com \
    --cc=linuxppc-dev@lists.ozlabs.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).