From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161067AbaDPNNJ (ORCPT ); Wed, 16 Apr 2014 09:13:09 -0400 Received: from mga02.intel.com ([134.134.136.20]:64859 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755622AbaDPNNH (ORCPT ); Wed, 16 Apr 2014 09:13:07 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,872,1389772800"; d="scan'208";a="494133580" Date: Wed, 16 Apr 2014 06:12:57 -0700 From: Andi Kleen To: Richard Weinberger Cc: the arch/x86 maintainers , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Seiji Aguchi , Steven Rostedt , Peter Zijlstra , Borislav Petkov , "linux-kernel@vger.kernel.org" Subject: Re: WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124 Message-ID: <20140416131257.GF32556@tassilo.jf.intel.com> References: <534E49C8.7050206@nod.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <534E49C8.7050206@nod.at> 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 > [] local_apic_timer_interrupt+0x3b/0x60 > [] smp_apic_timer_interrupt+0x45/0x60 > [] apic_timer_interrupt+0x6a/0x70 > [] ? panic+0x1a7/0x1ea > [] ? panic+0x1a3/0x1ea You're using panic_on_oops? That seems like a bug in panic. It shouldn't reenable interrupts -Andi > [] oops_end+0xd4/0xf0 > [] no_context+0x12e/0x200 > [] __bad_area_nosemaphore+0x11d/0x220 > [] bad_area+0x4e/0x60 > [] __do_page_fault+0x430/0x490 > [] ? call_console_drivers.clone.2+0xa5/0x100 > [] ? irq_work_queue+0x69/0xc0 > [] ? wake_up_klogd+0x34/0x40 > [] ? console_unlock+0x24d/0x280 > [] do_page_fault+0xc/0x10 > [] page_fault+0x22/0x30 > [] ? sysrq_handle_crash+0x16/0x20 > [] __handle_sysrq+0x129/0x190 > [] write_sysrq_trigger+0x3d/0x40 > [] proc_reg_write+0x43/0x70 > [] vfs_write+0xc4/0x1e0 > [] SyS_write+0x56/0xd0 > [] ? __audit_syscall_exit+0x216/0x2c0 > [] system_call_fastpath+0x16/0x1b