From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: boot problems on pseries
Date: Wed, 09 Aug 2006 17:37:30 +0200 [thread overview]
Message-ID: <1155137850.17187.48.camel@localhost.localdomain> (raw)
In-Reply-To: <20060809013609.GA10876@ca-server1.us.oracle.com>
On Tue, 2006-08-08 at 18:36 -0700, Mark Fasheh wrote:
> Hello,
> So I do most of my work on some IBM JS20 powerpc blades. They
> usually run a git kernel on a stock RHEL4 distribution. The contents of
> /proc/cpuinfo is:
>
> processor : 0
> cpu : PPC970, altivec supported
> clock : 1600.000000MHz
> revision : 2.2 (pvr 0039 0202)
>
> processor : 1
> cpu : PPC970, altivec supported
> clock : 1600.000000MHz
> revision : 2.2 (pvr 0039 0202)
>
> timebase : 199837651
> platform : pSeries
> machine : CHRP IBM,8842-21X
>
>
> Recently, I discovered that newer kernels would no longer fully boot.
> There's no oops or panic message and they get through most of the kernel
> initialization before simply hanging. I spent some quality time today with
> git-bisect, and traced the badness down to this commit:
I'm just back from vacation and looking into this.
Ben.
next prev parent reply other threads:[~2006-08-09 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 1:36 boot problems on pseries Mark Fasheh
2006-08-09 11:51 ` Olaf Hering
2006-08-09 15:37 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-20 17:00 dtutty
2006-08-21 14:56 ` Olaf Hering
2006-08-22 16:50 ` dtutty
2006-08-22 22:35 ` Olaf Hering
2006-08-23 23:59 ` Linas Vepstas
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=1155137850.17187.48.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mark.fasheh@oracle.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).