From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752081Ab2IEM5I (ORCPT ); Wed, 5 Sep 2012 08:57:08 -0400 Received: from mga11.intel.com ([192.55.52.93]:21635 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751323Ab2IEM5G (ORCPT ); Wed, 5 Sep 2012 08:57:06 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.80,374,1344236400"; d="scan'208";a="218349269" Date: Wed, 5 Sep 2012 20:57:00 +0800 From: Fengguang Wu To: Peter Zijlstra Cc: Michael Wang , LKML , x86@kernel.org, Suresh Siddha , Venkatesh Pallipadi Subject: Re: WARNING: cpu_is_offline() at native_smp_send_reschedule() Message-ID: <20120905125700.GA5833@localhost> References: <20120905011152.GA19853@localhost> <5046D69F.9000705@linux.vnet.ibm.com> <1346842480.2461.11.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1346842480.2461.11.camel@laptop> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 05, 2012 at 12:54:40PM +0200, Peter Zijlstra wrote: > On Wed, 2012-09-05 at 12:35 +0800, Michael Wang wrote: > > > [ 10.968565] reboot: machine restart > > > [ 10.983510] ------------[ cut here ]------------ > > > [ 10.984218] WARNING: at /c/kernel-tests/src/stable/arch/x86/kernel/smp.c:123 native_smp_send_reschedule+0x46/0x50() > > > [ 10.985880] Pid: 88, comm: kpktgend_0 Not tainted 3.6.0-rc3-00005-gb374aa1 #10 > > > [ 10.987185] Call Trace: > > > [ 10.987506] [<7902f42a>] warn_slowpath_common+0x5a/0x80 > > > [ 10.987506] [<7901ee16>] ? native_smp_send_reschedule+0x46/0x50 > > > [ 10.987506] [<7901ee16>] ? native_smp_send_reschedule+0x46/0x50 > > > [ 10.987506] [<7902f4fd>] warn_slowpath_null+0x1d/0x20 > > > [ 10.987506] [<7901ee16>] native_smp_send_reschedule+0x46/0x50 > > > > So this cpu try to fire a nohz balance kick ipi to an offline cpu? > > > > May be we are choosing a wrong cpu to kick but that's not the point, > > what I can't understand is why this cpu could do this kick. > > > > We have nohz_kick_needed() to check whether current cpu should do kick , > > and the first condition we need to match is that current cpu should be > > idle, but the trace show current pid is 88 not 0. > > > > We should add Peter to cc list, may be he will be interested on what > > happened. > > > > [ 10.987506] [<7905fdad>] trigger_load_balance+0x1bd/0x250 > > > [ 10.987506] [<79056d14>] scheduler_tick+0xd4/0x100 > > > [ 10.987506] [<7903bde5>] update_process_times+0x55/0x70 > > Hmm, added both venki and suresh as they touched it last ;-) > > I suppose you're running a hotplug loop along with your workload? I would definitely like to add some hotplug tests! However for this trace, it's simply booting into an ubuntu-core initrd and run the "reboot" command in some late init.d script. It seems that the bug was introduced somewhere in v3.3..v3.4. I'm now running 100 kvms to speedup the bisect progress :) Thanks, Fengguang