From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755134AbaDPJWN (ORCPT ); Wed, 16 Apr 2014 05:22:13 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56667 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751129AbaDPJWL (ORCPT ); Wed, 16 Apr 2014 05:22:11 -0400 Date: Wed, 16 Apr 2014 11:21:46 +0200 From: Peter Zijlstra To: Richard Weinberger Cc: the arch/x86 maintainers , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Seiji Aguchi , ak@linux.intel.com, Steven Rostedt , Borislav Petkov , "linux-kernel@vger.kernel.org" Subject: Re: WARNING: CPU: 2 PID: 1857 at arch/x86/kernel/smp.c:124 Message-ID: <20140416092146.GQ11182@twins.programming.kicks-ass.net> 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 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 16, 2014 at 11:13:44AM +0200, Richard Weinberger wrote: > Hi! > > On a new 8 core server I'm facing the following issue. > After an oops a warning triggers. I think its fair to ignore everything _after_ an OOPS ;-)