From: Dimitri Sivanich <sivanich@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Max Krasnyansky <maxk@qualcomm.com>, Paul Jackson <pj@sgi.com>,
Con Kolivas <kernel@kolivas.org>,
"Derek L. Fults" <dfults@sgi.com>, devik <devik@cdi.cz>,
Dinakar Guniguntala <dino@in.ibm.com>,
Emmanuel Pacaud <emmanuel.pacaud@univ-poitiers.fr>,
Frederik Deweerdt <deweerdt@free.fr>, Ingo Molnar <mingo@elte.hu>,
Matthew Dobson <colpatch@us.ibm.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
rostedt@goodmis.org, Oleg Nesterov <oleg@tv-sign.ru>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Paul Menage <menage@google.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Randy.Dunlap" <rddunlap@osdl.org>,
suresh.b.siddha@intel.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses)
Date: Wed, 4 Jun 2008 09:00:36 -0500 [thread overview]
Message-ID: <20080604140036.GC18993@sgi.com> (raw)
In-Reply-To: <20080603144010.GA25948@sgi.com>
On Tue, Jun 03, 2008 at 09:40:10AM -0500, Dimitri Sivanich wrote:
> I tried the following scenario on an ia64 Altix running 2.6.26-rc4 with cpusets compiled in but cpuset fs unmounted. Do your patches already address this?
>
> $ taskset -cp 3 $$ (attach to cpu 3)
> pid 4591's current affinity list: 0-3
> pid 4591's new affinity list: 3
> $ echo 0 > /sys/devices/system/cpu/cpu2/online (down cpu 2)
> (above command hangs)
>
> Backtrace of pid 4591 (bash)
>
> Call Trace:
> [<a00000010078e990>] schedule+0x1210/0x13c0
> sp=e0000060b6dffc90 bsp=e0000060b6df11e0
> [<a00000010078ef60>] schedule_timeout+0x40/0x180
> sp=e0000060b6dffce0 bsp=e0000060b6df11b0
> [<a00000010078d3e0>] wait_for_common+0x240/0x3c0
> sp=e0000060b6dffd10 bsp=e0000060b6df1180
> [<a00000010078d760>] wait_for_completion+0x40/0x60
> sp=e0000060b6dffd40 bsp=e0000060b6df1160
> [<a000000100114ee0>] __stop_machine_run+0x120/0x160
> sp=e0000060b6dffd40 bsp=e0000060b6df1120
> [<a000000100765ae0>] _cpu_down+0x2a0/0x600
> sp=e0000060b6dffd80 bsp=e0000060b6df10c8
> [<a000000100765ea0>] cpu_down+0x60/0xa0
> sp=e0000060b6dffe20 bsp=e0000060b6df10a0
> [<a000000100768090>] store_online+0x50/0xe0
> sp=e0000060b6dffe20 bsp=e0000060b6df1070
> [<a0000001004f8800>] sysdev_store+0x60/0xa0
> sp=e0000060b6dffe20 bsp=e0000060b6df1038
> [<a00000010022e370>] sysfs_write_file+0x250/0x300
> sp=e0000060b6dffe20 bsp=e0000060b6df0fe0
> [<a00000010018a750>] vfs_write+0x1b0/0x300
> sp=e0000060b6dffe20 bsp=e0000060b6df0f90
> [<a00000010018b350>] sys_write+0x70/0xe0
> sp=e0000060b6dffe20 bsp=e0000060b6df0f18
> [<a00000010000af80>] ia64_ret_from_syscall+0x0/0x20
> sp=e0000060b6dffe30 bsp=e0000060b6df0f18
> [<a000000000010720>] ia64_ivt+0xffffffff00010720/0x400
> sp=e0000060b6e00000 bsp=e0000060b6df0f18
The following workaround alleviates the symptom and hopefully is a hint as to the solution:
echo -1 > /proc/sys/kernel/sched_rt_runtime_us
next prev parent reply other threads:[~2008-06-04 14:00 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 2:30 Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses) Paul Jackson
2008-06-02 16:42 ` Dimitri Sivanich
2008-06-02 18:39 ` Max Krasnyansky
2008-06-02 21:41 ` Dimitri Sivanich
2008-06-02 21:59 ` Max Krasnyansky
2008-06-03 14:40 ` Dimitri Sivanich
2008-06-03 17:57 ` Max Krasnyanskiy
2008-06-04 14:00 ` Dimitri Sivanich [this message]
2008-06-04 18:07 ` Stop machine threads are getting preemted by the rt period enforcement Max Krasnyansky
2008-06-04 18:18 ` Peter Zijlstra
2008-06-04 18:24 ` Max Krasnyansky
2008-06-04 18:55 ` Peter Zijlstra
2008-06-04 20:14 ` Max Krasnyansky
2008-06-02 22:35 ` Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses) Ingo Oeser
2008-06-02 22:45 ` Peter Zijlstra
2008-06-02 23:04 ` Max Krasnyansky
2008-06-02 23:55 ` Ingo Oeser
2008-06-03 3:32 ` Max Krasnyansky
2008-06-03 23:47 ` Max Krasnyanskiy
2008-06-04 0:41 ` Paul Jackson
2008-06-04 4:32 ` Max Krasnyansky
2008-06-04 4:47 ` Paul Jackson
2008-06-04 12:18 ` Andi Kleen
2008-06-04 17:41 ` Paul Jackson
2008-06-04 18:29 ` Max Krasnyansky
2008-06-04 18:56 ` Peter Zijlstra
2008-06-04 19:34 ` Max Krasnyansky
2008-06-04 18:58 ` Paul Jackson
2008-06-04 19:31 ` Max Krasnyansky
2008-06-04 19:37 ` Paul Jackson
2008-06-04 19:45 ` Max Krasnyansky
2008-06-04 20:05 ` Andi Kleen
2008-06-04 20:23 ` Paul Jackson
2008-06-04 20:03 ` Andi Kleen
2008-06-04 20:16 ` Paul Jackson
2008-06-04 20:33 ` Andi Kleen
2008-06-04 20:38 ` Paul Jackson
2008-06-04 21:16 ` Max Krasnyansky
2008-06-04 21:17 ` Paul Jackson
2008-06-04 21:20 ` Max Krasnyansky
2008-06-04 21:26 ` Paul Jackson
2008-06-04 1:18 ` Nick Piggin
2008-06-04 3:00 ` Max Krasnyansky
2008-06-04 16:18 ` Ingo Oeser
2008-06-04 17:47 ` Max Krasnyansky
2008-06-03 6:03 ` Nick Piggin
2008-06-04 9:58 ` Mark Hounschell
2008-06-04 17:26 ` Paul Jackson
2008-06-04 21:00 ` Mark Hounschell
2008-06-04 21:03 ` Paul Jackson
2008-06-04 19:26 ` Max Krasnyansky
2008-06-04 20:25 ` Peter Zijlstra
2008-06-04 21:44 ` Michael Trimarchi
2008-06-04 21:52 ` Peter Zijlstra
2008-06-05 11:16 ` Michael Trimarchi
2008-06-05 12:07 ` Peter Zijlstra
2008-06-05 14:57 ` Michael Trimarchi
2009-05-08 2:48 ` GeunSik Lim
2008-06-05 11:44 ` Mark Hounschell
2008-06-06 22:28 ` Max Krasnyanskiy
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=20080604140036.GC18993@sgi.com \
--to=sivanich@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=colpatch@us.ibm.com \
--cc=devik@cdi.cz \
--cc=deweerdt@free.fr \
--cc=dfults@sgi.com \
--cc=dino@in.ibm.com \
--cc=emmanuel.pacaud@univ-poitiers.fr \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=oleg@tv-sign.ru \
--cc=paulmck@us.ibm.com \
--cc=pj@sgi.com \
--cc=rddunlap@osdl.org \
--cc=rostedt@goodmis.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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.