From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:38796 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750783AbbJaWXs (ORCPT ); Sat, 31 Oct 2015 18:23:48 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5108220326 for ; Sat, 31 Oct 2015 18:23:47 -0400 (EDT) Date: Sat, 31 Oct 2015 15:23:45 -0700 From: Greg KH To: Marc Haber Cc: stable@vger.kernel.org Subject: Re: PC Engines APU panics on boot since 4.2.4 Message-ID: <20151031222345.GA29528@kroah.com> References: <20151031211551.GH4392@torres.zugschlus.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151031211551.GH4392@torres.zugschlus.de> Sender: stable-owner@vger.kernel.org List-ID: On Sat, Oct 31, 2015 at 10:15:51PM +0100, Marc Haber wrote: > Hi, > > 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? thanks, greg k-h