Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Kaz Kylheku <kaz@zeugmasystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 64-bit 2.6.17.7 SMP hangs in __cpu_up().
Date: Fri, 8 Sep 2006 12:59:53 +0200	[thread overview]
Message-ID: <20060908105953.GA1555@linux-mips.org> (raw)
In-Reply-To: <66910A579C9312469A7DF9ADB54A8B7D390152@exchange.ZeugmaSystems.local>

On Thu, Sep 07, 2006 at 04:25:51PM -0700, Kaz Kylheku wrote:

> Anyone seen anything like this?
> 
> Execution does not get past the loop:
> 
>   while (!cpu_isset(cpu, cpu_callin_map))
>     udelay(100);
> 
> The other CPU is not coming up.
> 
> 32 bit SMP works fine.

Interesting because the 64-bit kernel is considered bettere tested on
Sibyte chips than 32-bit these days.

Not a problem I was aware of.

  Ralf

      parent reply	other threads:[~2006-09-08 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 23:25 64-bit 2.6.17.7 SMP hangs in __cpu_up() Kaz Kylheku
2006-09-07 23:25 ` Kaz Kylheku
2006-09-08 10:59 ` Ralf Baechle [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=20060908105953.GA1555@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kaz@zeugmasystems.com \
    --cc=linux-mips@linux-mips.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