Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754214AbYFDOA5 (ORCPT ); Wed, 4 Jun 2008 10:00:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758772AbYFDOAl (ORCPT ); Wed, 4 Jun 2008 10:00:41 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:57028 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757602AbYFDOAj (ORCPT ); Wed, 4 Jun 2008 10:00:39 -0400 Date: Wed, 4 Jun 2008 09:00:36 -0500 From: Dimitri Sivanich To: linux-kernel@vger.kernel.org Cc: Max Krasnyansky , Paul Jackson , Con Kolivas , "Derek L. Fults" , devik , Dinakar Guniguntala , Emmanuel Pacaud , Frederik Deweerdt , Ingo Molnar , Matthew Dobson , Nick Piggin , rostedt@goodmis.org, Oleg Nesterov , "Paul E. McKenney" , Paul Menage , Peter Zijlstra , "Randy.Dunlap" , suresh.b.siddha@intel.com, Thomas Gleixner Subject: Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses) Message-ID: <20080604140036.GC18993@sgi.com> References: <20080601213019.14ea8ef8.pj@sgi.com> <20080602164203.GA2477@sgi.com> <48443E66.6060205@qualcomm.com> <20080602214151.GA7072@sgi.com> <48446D46.2010903@qualcomm.com> <20080603144010.GA25948@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080603144010.GA25948@sgi.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2617 Lines: 48 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: > [] schedule+0x1210/0x13c0 > sp=e0000060b6dffc90 bsp=e0000060b6df11e0 > [] schedule_timeout+0x40/0x180 > sp=e0000060b6dffce0 bsp=e0000060b6df11b0 > [] wait_for_common+0x240/0x3c0 > sp=e0000060b6dffd10 bsp=e0000060b6df1180 > [] wait_for_completion+0x40/0x60 > sp=e0000060b6dffd40 bsp=e0000060b6df1160 > [] __stop_machine_run+0x120/0x160 > sp=e0000060b6dffd40 bsp=e0000060b6df1120 > [] _cpu_down+0x2a0/0x600 > sp=e0000060b6dffd80 bsp=e0000060b6df10c8 > [] cpu_down+0x60/0xa0 > sp=e0000060b6dffe20 bsp=e0000060b6df10a0 > [] store_online+0x50/0xe0 > sp=e0000060b6dffe20 bsp=e0000060b6df1070 > [] sysdev_store+0x60/0xa0 > sp=e0000060b6dffe20 bsp=e0000060b6df1038 > [] sysfs_write_file+0x250/0x300 > sp=e0000060b6dffe20 bsp=e0000060b6df0fe0 > [] vfs_write+0x1b0/0x300 > sp=e0000060b6dffe20 bsp=e0000060b6df0f90 > [] sys_write+0x70/0xe0 > sp=e0000060b6dffe20 bsp=e0000060b6df0f18 > [] ia64_ret_from_syscall+0x0/0x20 > sp=e0000060b6dffe30 bsp=e0000060b6df0f18 > [] 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/