From: Hugh Dickins <hughd@google.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: powerpc/pci sysdata batch hangs G5 boot
Date: Sat, 19 Mar 2011 20:41:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1103192023140.1592@sister.anvils> (raw)
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
Currently, ppc32 uses sysdata for the pci_controller pointer, and
ppc64 uses it to hold the device_node pointer. This patch moves the
of_node pointer into (struct pci_bus*)->dev.of_node and
(struct pci_dev*)->dev.of_node so that sysdata can be converted to always
use the pci_controller pointer instead. It also fixes up the
allocating of pci devices so that the of_node pointer gets assigned
consistently and increments the ref count.
The last message I see on screen when booting is
mpic: ISU size: 124, shift: 7, mask: 7f
Usually that would be followed by
mpic: Initializing for 124 sources
but with your commit it just hangs; revert that commit,
from mmotm or from Linus's current git, and all is fine.
Config available privately on request. Noticing that patch is a
PPC OF PCI thing, and that I have CONFIG_PPC_OF_PLATFORM_PCI off,
I did try switching that on, but it made no difference.
Thanks,
Hugh
next reply other threads:[~2011-03-20 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 3:41 Hugh Dickins [this message]
2011-03-20 6:25 ` powerpc/pci sysdata batch hangs G5 boot Grant Likely
2011-03-20 9:10 ` Benjamin Herrenschmidt
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=alpine.LSU.2.00.1103192023140.1592@sister.anvils \
--to=hughd@google.com \
--cc=grant.likely@secretlab.ca \
--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