From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Domenico Andreoli <cavokz@gmail.com>
Cc: 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: Mon, 21 Apr 2008 09:43:38 -0500 [thread overview]
Message-ID: <1208789018.3640.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20080420231818.GA2162@ska.dandreoli.com>
On Mon, 2008-04-21 at 01:18 +0200, Domenico Andreoli wrote:
> as soon as I booted my dual PA8600 with 2.6.25 I got 1 CPU less. The
> only other kernel I successfully used on that box is Debian's 2.6.22-3.
>
> Debian never built 2.6.23 for parisc, 2.6.24 was still hanging last
> time I checked it, 2.6.25 did not even build until recent -rc. So I am
> not in the best position to bisect.
Try this one; it's a corrected version of debian 2.6.24-1 for parisc
systems:
http://www.parisc-linux.org/~jejb/parisc_debs/linux-image-2.6.24-1-parisc64-smp_2.6.24-5+b1_hppa.deb
It's known to boot correctly on B, A and rp3440 systems, but we don't
have a J system to try it out on.
> Here is the relevant dmesg.
> Releasing cpu 1 now, hpa=fffffffffffa2000
> SMP: CPU:1 is stuck.
> CPU(s): 2 x PA8600 (PCX-W+) at 552.000000 MHz
> Setting cache flush threshold to f84c0 (1 CPUs online)
Unfortunately that doesn't tell us anything other than the start IPI
failed for some reason. One thing to try with the J series is a 32 bit
kernel just in case: they're the only SMP systems that will boot 32
bits, just in case you could try a 32 bit smp kernel.
As Dave Anglin said, it could be a config problem, although when I have
CPUs deconfigured by firmware, they usually don't show up in the
inventory.
James
next prev parent reply other threads:[~2008-04-21 14:43 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 [this message]
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
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=1208789018.3640.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=cavokz@gmail.com \
--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 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.