From: Cliff Wickman <cpw@sgi.com>
To: dmitry.adamushko@gmail.com, avi@qumranet.com, mingo@elte.hu,
heiko.carstens@de.ibm.com, a.p.zijlstra@chello.nl,
vatsa@linux.vnet.ibm.com
Cc: Avi Kivity <avi@qumranet.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
PeterZijlst@sgi.com
Subject: [BUG] hotplug cpus on ia64
Date: Wed, 21 May 2008 09:48:40 -0500 [thread overview]
Message-ID: <20080521144840.GA32628@sgi.com> (raw)
In-Reply-To: <b647ffbd0805140113i4296076cna3f371c86c479653@mail.gmail.com>
Gentlemen,
I built an ia64 kernel from Andrew's tree (2.6.26-rc2-mm1)
and get a very predictable hotplug cpu problem.
billberry1:/tmp/cpw # ./dis
disabled cpu 17
enabled cpu 17
billberry1:/tmp/cpw # ./dis
disabled cpu 17
enabled cpu 17
billberry1:/tmp/cpw # ./dis
The script that disables the cpu always hangs (unkillable)
on the 3rd attempt.
I haven't spent any debugging time on it yet.
Just wondering if you've seen it? It doesn't seem to happen x86_64.
-Cliff Wickman
cpw@sgi.com
next prev parent reply other threads:[~2008-05-21 14:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 14:33 [BUG] cpu hotplug vs scheduler Avi Kivity
2008-05-13 15:33 ` Avi Kivity
2008-05-13 19:00 ` Heiko Carstens
2008-05-14 8:13 ` Dmitry Adamushko
2008-05-14 12:30 ` Avi Kivity
2008-05-14 13:05 ` Dmitry Adamushko
2008-05-15 10:19 ` Avi Kivity
2008-05-21 12:31 ` Heiko Carstens
2008-05-21 12:42 ` Avi Kivity
2008-05-21 12:55 ` Heiko Carstens
2008-05-21 13:03 ` Avi Kivity
2008-05-21 14:48 ` Cliff Wickman [this message]
[not found] <E1K1l2y-0007bu-44@eag09.americas.sgi.com>
[not found] ` <1212154614.12349.244.camel@twins>
2008-06-03 22:17 ` [BUG] hotplug cpus on ia64 Cliff Wickman
2008-06-04 13:50 ` Dimitri Sivanich
2008-06-05 12:49 ` Peter Zijlstra
2008-06-05 13:51 ` Dimitri Sivanich
2008-06-05 14:18 ` Peter Zijlstra
2008-06-10 10:19 ` Ingo Molnar
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=20080521144840.GA32628@sgi.com \
--to=cpw@sgi.com \
--cc=PeterZijlst@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@qumranet.com \
--cc=dmitry.adamushko@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
/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