All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: Roland Dreier <roland@topspin.com>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	ppc64 dev list <linuxppc64-dev@ozlabs.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc5-git8 regression on PPC64
Date: Sat, 04 Jun 2005 08:56:23 +1000	[thread overview]
Message-ID: <1117839384.31082.186.camel@gaston> (raw)
In-Reply-To: <20050603182725.GB11355@otto>

On Fri, 2005-06-03 at 13:27 -0500, Nathan Lynch wrote:
> Roland Dreier wrote:
> > I'm seeing something possibly related as well -- with an up-to-date
> > git tree (HEAD == d8d088d25822b0199fdfb392085e1cf8a5914a97), I get a
> > hang early in the boot on an OpenPower 710 (2 x POWER5).
> 
> Backing this one out fixes it here on a Power5 570.
> 
> http://marc.theaimsgroup.com/?l=bk-commits-head&m=111772917211270&q=raw
> 
> Ben, any ideas?

Weird, works fine on our POWER5 here. What is the output ? Especially,
what if you enable DEBUG_PROM in there ?

Ben.



      parent reply	other threads:[~2005-06-03 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-03 14:52 2.6.12-rc5-git8 regression on PPC64 Martin J. Bligh
2005-06-03 17:42 ` Roland Dreier
2005-06-03 18:27   ` Nathan Lynch
2005-06-03 19:07     ` Roland Dreier
2005-06-03 19:25       ` [PATCH] prom_find_machine_type typo breaks pSeries lpar boot Nathan Lynch
2005-06-03 22:58         ` Benjamin Herrenschmidt
2007-11-14 12:27           ` B. N. Poornima
2007-11-14 19:37             ` Nathan Lynch
2007-11-16 10:10               ` B. N. Poornima
2007-11-14 22:13             ` Benjamin Herrenschmidt
2005-06-03 22:56     ` 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=1117839384.31082.186.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=mbligh@mbligh.org \
    --cc=ntl@pobox.com \
    --cc=roland@topspin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.