All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	Domenico Andreoli <cavokz@gmail.com>
Cc: Dave Land <xmechanic@landcomp.net>
Subject: Re: HP J5600/J6750 64bit SMP CPU#1 stuck problems [was: Does there exists any 32bit-only PARISC SMP machines?]
Date: Mon, 21 Oct 2013 22:39:12 +0200	[thread overview]
Message-ID: <526590F0.8040504@gmx.de> (raw)
In-Reply-To: <BLU0-SMTP632514F697DEA3A182EE9897010@phx.gbl>

On 10/21/2013 10:37 PM, John David Anglin wrote:
> It also likely will boot 32-bit SMP kernel with both CPUs with more than 3 GB memory.  This provides 3.63 GB
> of usable memory.

Sure, it will.
But the idea is to be able to drop the 32bit SMP kernels for Debian...
And those machines are currently the only reason why we can't drop 32bit SMP. 

Helge

> On 10/21/2013 4:07 PM, Helge Deller wrote:
>> Domenico,
>>
>> On 09/04/2013 04:28 PM, Domenico Andreoli wrote:
>>>>>> J5600 is SMP capable in both 32bit and 64bit mode.
>>>>>> mine doesn't boot 64bit SMP since 2.6.22. I've never been able to trace
>>>>>> it down but can confirm it happens also on more recent kernels.
>>>> I confirm that smp parisc64 v3.11 doesn't bring up both the cpus on my
>>>> system but at least it boots one, something that didn't happen in some
>>>> darker moments since 2.6.22.
>>>>
>>>> similar "SMP: CPU:1 is stuck." happens also with debian v3.10-parisc64-smp kernel.
>>> BTW, this is the most detailed investigation I'm aware of:
>>> https://lkml.org/lkml/2008/4/20/251
>> Dave Anglin had the idea that the 64bit SMP CPU#1 stuck problems might be
>> related to PDC- or I/O-space conflicts with physical memory.
>> On Dave Land's machine (J6750) we could verify that off-list.
>>
>> I assume you have more than 3GB (4GB) RAM in your machine?
>> If yes, then if you phyiscally remove some memory so that you leave a max.
>> of 3GB in, the 64bit SMP kernel will most likely boot up all CPUs.
>>
>> You wrote:
>>> mine doesn't boot 64bit SMP since 2.6.22.
>> Are you *really* sure that it booted 64bit SMP with kernel 2.6.22 ?
>> Or did you maybe upgraded memory after that date?
>> If it sucessfully booted, then we maybe have only some kind of regression.
>>
>> Helge


  reply	other threads:[~2013-10-21 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 18:51 Does there exists any 32bit-only PARISC SMP machines? Helge Deller
2013-08-30  2:42 ` James Bottomley
2013-09-03 15:56   ` Domenico Andreoli
2013-09-04  8:13     ` Aw: " Helge Deller
2013-09-04 14:07       ` Domenico Andreoli
2013-09-04 14:28         ` Domenico Andreoli
2013-09-04 15:41           ` John David Anglin
2013-09-05 16:24             ` John David Anglin
2013-10-21 20:07           ` HP J5600/J6750 64bit SMP CPU#1 stuck problems [was: Does there exists any 32bit-only PARISC SMP machines?] Helge Deller
2013-10-21 20:37             ` John David Anglin
2013-10-21 20:39               ` Helge Deller [this message]
2013-10-26 22:06                 ` Helge Deller
2013-10-29 13:31                   ` Domenico Andreoli
2013-09-04  8:44 ` Does there exists any 32bit-only PARISC SMP machines? Thomas Bogendoerfer

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=526590F0.8040504@gmx.de \
    --to=deller@gmx.de \
    --cc=cavokz@gmail.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-parisc@vger.kernel.org \
    --cc=xmechanic@landcomp.net \
    /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.