linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Giuliano Pochini <pochini@shiny.it>
Cc: LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: Re: CPU 1 refused to die!
Date: Tue, 23 May 2006 17:51:13 -0500	[thread overview]
Message-ID: <20060523225113.GD11414@localdomain> (raw)
In-Reply-To: <20060523235819.473e4149.pochini@shiny.it>

Giuliano Pochini wrote:
> 
> I booted with maxcpus=1, then I enabled the 2nd cpu
> with echo 1 > /sys/devices/system/cpu/cpu1/online

So onlining at runtime seems to work.  Did you verify that tasks get
run on the 2nd cpu after you online it?  Any other strange messages in
dmesg?

> I can't disable it anymore. dmesg says "CPU 1 refused to die!".

But offlining doesn't.

Can you online and offline cpus if you boot without maxcpus=1?

  reply	other threads:[~2006-05-23 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 21:58 CPU 1 refused to die! Giuliano Pochini
2006-05-23 22:51 ` Nathan Lynch [this message]
2006-05-25 12:46   ` Giuliano Pochini
2006-06-24 20:18     ` Giuliano Pochini

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=20060523225113.GD11414@localdomain \
    --to=ntl@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pochini@shiny.it \
    /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).