From: Domenico Andreoli <cavokz@gmail.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Grant Grundler <grundler@parisc-linux.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org
Subject: Re: [REGRESSION] 2.6.25 on parisc - CPU 1 is stuck
Date: Tue, 6 May 2008 18:32:06 +0200 [thread overview]
Message-ID: <20080506163206.GA2211@ska.dandreoli.com> (raw)
In-Reply-To: <20080423005438.GK19802@phobos.i.cabal.ca>
On Tue, Apr 22, 2008 at 08:54:38PM -0400, Kyle McMartin wrote:
> On Tue, Apr 22, 2008 at 06:44:40PM -0600, Grant Grundler wrote:
> >
> > *nod* I don't expect CPUs to show up in inventory if they are
> > deconfigured in BCH. Maybe J-class firmware has this wrong? *shrug*
> > Something worth checking I guess.
> >
>
> i booted the kernel from my rp3440 on my j6000. i also get this cpu1 is
> stuck message. putting a panic in the SMP C-code entrypoint is never
> hit.
>
> most oddly, putting a hpmc-causing insn sequence in the entry point
> doesn't trigger either, so the cpu isn't coming out of the rendezvous.
>
> even more oddly, the stwa insn in the bring up code looks fine.
still nothing changed with 2.6.26-rc1-00110-ga153063
cheers,
Domenico
-----[ Domenico Andreoli, aka cavok
--[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
prev parent reply other threads:[~2008-05-06 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 23:18 [REGRESSION] 2.6.25 on parisc - CPU 1 is stuck Domenico Andreoli
2008-04-21 5:00 ` Grant Grundler
2008-04-21 13:07 ` John David Anglin
2008-04-21 13:31 ` Domenico Andreoli
2008-04-23 0:54 ` Grant Grundler
2008-04-21 14:43 ` James Bottomley
2008-04-21 20:24 ` Domenico Andreoli
2008-04-23 0:44 ` Grant Grundler
2008-04-23 0:54 ` Kyle McMartin
2008-05-06 16:32 ` Domenico Andreoli [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=20080506163206.GA2211@ska.dandreoli.com \
--to=cavokz@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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