linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Rutger Nijlunsing <rutger@nospam.com>
Subject: Re: [PATCH] Re: 2.6.22-git hangs during boot on PowerBook G3 in 0.0 seconds
Date: Tue, 24 Jul 2007 18:59:46 -0500	[thread overview]
Message-ID: <20070724185946.722f34b5.kim.phillips@freescale.com> (raw)
In-Reply-To: <1185234923.5439.158.camel@localhost.localdomain>

On Tue, 24 Jul 2007 09:55:23 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:

> 
> > > After hours of fun git bisecting, finally found the commit to revert
> > > to make my PowerBook G3 Lombard boot again. This does not result in
> > > the complains the reverted commit was revering to.
> > 
> > ..but it does on my MPC8360.
> 
> In which circumstances are you trying to translate an address with no
> size cell ?

for the enumerated PHYs. As the original commit comment states, I was
getting these messages:

prom_parse: Bad cell count for /qe@e0100000/mdio@2120/ethernet-phy@00
prom_parse: Bad cell count for /qe@e0100000/mdio@2120/ethernet-phy@01

> I also wonder why it hangs on the powerbook... Rutger, I would expect to
> see that complaint warning with the reverted patch, what does it say ?
> 
> My Wallstreet (also based on Grackle) doesn't have the problem. Also can
> you send me a tarball of /proc/device-tree ?

I don't have any of those machines, but it seems that older kernels
running on the Lombard emitted:

device-tree: Duplicate name in /cpus/PowerPC,750@0, renamed to "l2-cache#1"

messages*.  Experimenting with adding two chosen nodes (due to a prior
thread on this list**) results in a hung kernel on the 8360 also, so
perhaps they're related (and the kernel's tolerance to duplicate
entries has changed, which explains where I had seen the chosen node
being renamed).

but yeah, size-cells should be allowed to be 0 (even address-cells) and
it may be the case that the Lombard needs some fixup code.

Kim

* http://lists.infradead.org/pipermail/linux-pcmcia/2007-April/004503.html
** http://ozlabs.org/pipermail/linuxppc-dev/2007-July/039758.html

  reply	other threads:[~2007-07-25  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 19:21 2.6.22-git hangs during boot on PowerBook G3 in 0.0 seconds Rutger Nijlunsing
2007-07-21 21:28 ` [PATCH] " Rutger Nijlunsing
2007-07-23 22:27   ` Kim Phillips
2007-07-23 23:55     ` Benjamin Herrenschmidt
2007-07-24 23:59       ` Kim Phillips [this message]
2007-07-25  2:07         ` Benjamin Herrenschmidt
2007-07-26  3:31         ` Paul Mackerras
2007-07-26  3:42         ` Paul Mackerras
2007-07-26 21:29           ` Kim Phillips
2007-07-26 21:53             ` Benjamin Herrenschmidt
2007-07-27 22:11             ` [PATCH] Re: 2.6.22-git hangs during PCMCIA " Rutger Nijlunsing
2007-07-27 22:26               ` Benjamin Herrenschmidt
2007-07-27 23:29                 ` Kim Phillips

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=20070724185946.722f34b5.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rutger@nospam.com \
    /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).