From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:59025 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752106AbbKASeU (ORCPT ); Sun, 1 Nov 2015 13:34:20 -0500 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 08CB9203F1 for ; Sun, 1 Nov 2015 13:34:20 -0500 (EST) Date: Sun, 1 Nov 2015 10:34:18 -0800 From: Greg KH To: Marc Haber , Thomas Gleixner , Mika Westerberg , Jiang Liu , jarkko.nikula@linux.intel.com Cc: stable@vger.kernel.org Subject: Re: PC Engines APU panics on boot since 4.2.4 Message-ID: <20151101183418.GA15500@kroah.com> References: <20151031211551.GH4392@torres.zugschlus.de> <20151031222345.GA29528@kroah.com> <20151101182628.GL4392@torres.zugschlus.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151101182628.GL4392@torres.zugschlus.de> Sender: stable-owner@vger.kernel.org List-ID: On Sun, Nov 01, 2015 at 07:26:28PM +0100, Marc Haber wrote: > Hi, > > On Sat, Oct 31, 2015 at 03:23:45PM -0700, Greg KH wrote: > > On Sat, Oct 31, 2015 at 10:15:51PM +0100, Marc Haber wrote: > > > I run a PC Engines APU in my basement for local infrastructure with > > > KVM. Kernels 4.2.4 and 4.2.5 panic on bootup pretty fast after the > > > usual "x86: Booted up 1 node, 2 CPUs", "smpboot: Total of 2 processors > > > activated (3999.89 BogoMIPS)" message. The message I would expect > > > instead of the kernel panic would be "devtmpfs: initialized", as one > > > can see on a successful 4.2.3 boot with identical kernel configuration. > > > > If you use 'git bisect' between 4.2.3 and 4.2.5, can you find the > > problem commit for us to help track this down? > > The winner is ... > [21f751a634f3b5eaf916f940e47f327fbc6e9727] x86/ioapic: Force affinity setting in setup_ioapic_dest() > > After rolling this back in 4.2.5, the APU now runs fine. Ok, this matches up with commit 21f751a634f3b5eaf916f940e47f327fbc6e9727 in Linus's tree. Thomas and Mika, any thoughts about this? Marc, do you have this same problem with Linus's tree at the moment as well? thanks, greg k-h