From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Srivatsa S. Bhat" Subject: Re: WARNING: at arch/x86/kernel/smp.c:119 native_smp_send_reschedule+0x25/0x43() Date: Fri, 10 Feb 2012 15:36:45 +0530 Message-ID: <4F34EC35.7010109@linux.vnet.ibm.com> References: <1328751082.5611.6.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Josh Boyer , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Avi Kivity , kvm , linux-kernel , x86 , Suresh B Siddha , Peter Zijlstra , Sergey Senozhatsky To: Sasha Levin Return-path: Received: from e28smtp06.in.ibm.com ([122.248.162.6]:58260 "EHLO e28smtp06.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759076Ab2BJKG6 (ORCPT ); Fri, 10 Feb 2012 05:06:58 -0500 Received: from /spool/local by e28smtp06.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 10 Feb 2012 15:36:54 +0530 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Adding Suresh and Peter to Cc. On 02/10/2012 01:16 AM, Sasha Levin wrote: > On Wed, Feb 8, 2012 at 7:59 PM, Josh Boyer wrote: >> On Wed, Feb 8, 2012 at 8:31 PM, Sasha Levin wrote: >>> Hi all, >>> >>> I got the following warning when shutting down a KVM guest with a whole bunch of cores (254 in this case). >>> >>> It's actually pretty easy to reproduce it, it happens every once in 2-3 shutdowns. >>> >>> [ 32.448626] ------------[ cut here ]------------ >>> [ 32.449160] WARNING: at arch/x86/kernel/smp.c:119 native_smp_send_reschedule+0x25/0x43() >>> [ 32.449621] Pid: 1, comm: init_stage2 Not tainted 3.2.0+ #14 >>> [ 32.449621] Call Trace: >>> [ 32.449621] [] ? native_smp_send_reschedule+0x25/0x43 >>> [ 32.449621] [] warn_slowpath_common+0x7b/0x93 >>> [ 32.449621] [] ? tick_nohz_handler+0xc9/0xc9 >>> [ 32.449621] [] warn_slowpath_null+0x15/0x18 >>> [ 32.449621] [] native_smp_send_reschedule+0x25/0x43 >>> [ 32.449621] [] smp_send_reschedule+0xa/0xc >>> [ 32.449621] [] scheduler_tick+0x21a/0x242 >>> [ 32.449621] [] update_process_times+0x62/0x73 >>> [ 32.449621] [] tick_sched_timer+0x6a/0x8a >>> [ 32.449621] [] __run_hrtimer.clone.26+0x55/0xcb >>> [ 32.449621] [] hrtimer_interrupt+0xcb/0x19b >>> [ 32.449621] [] smp_apic_timer_interrupt+0x72/0x85 >>> [ 32.449621] [] apic_timer_interrupt+0x6e/0x80 >>> [ 32.449621] [] ? _raw_spin_unlock_irqrestore+0x3a/0x3e >>> [ 32.449621] [] ? arch_local_irq_restore+0x6/0xd >>> [ 32.449621] [] default_send_IPI_mask_allbutself_phys+0x78/0x88 >>> [ 32.449621] [] ? __migrate_task+0xf1/0xf1 >>> [ 32.449621] [] physflat_send_IPI_allbutself+0x12/0x14 >>> [ 32.449621] [] native_stop_other_cpus+0x4d/0xa8 >>> [ 32.449621] [] native_machine_shutdown+0x56/0x6d >>> [ 32.449621] [] kvm_shutdown+0x1a/0x1c >>> [ 32.449621] [] machine_shutdown+0xa/0xc >>> [ 32.449621] [] native_machine_restart+0x20/0x32 >>> [ 32.449621] [] machine_restart+0xa/0xc >>> [ 32.449621] [] kernel_restart+0x49/0x4d >>> [ 32.449621] [] sys_reboot+0x14b/0x18a >>> [ 32.449621] [] ? remove_wait_queue+0x4c/0x51 >>> [ 32.449621] [] ? do_wait+0x1a4/0x1e7 >>> [ 32.449621] [] ? sys_wait4+0xa8/0xbc >>> [ 32.449621] [] ? clear_tsk_thread_flag+0xf/0xf >>> [ 32.449621] [] ? async_page_fault+0x25/0x30 >>> [ 32.449621] [] system_call_fastpath+0x16/0x1b >>> [ 32.449621] ---[ end trace d0f03651493fd3d6 ]-- >> >> You don't really point out exactly which kernel this is, but we saw this in >> 3.3 git and it was fixed by commit 71325960d16cd68ea0e22a8da15b2495b0f363f7. >> Or at least something very like it was. > > The kernel there was vanilla 3.2 (as stated in the warning header). > > I've tried it again with linux-next from today which includes the > commit you mentioned, and still get the same error.