From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759307Ab2AFWb4 (ORCPT ); Fri, 6 Jan 2012 17:31:56 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:33115 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752947Ab2AFWby (ORCPT ); Fri, 6 Jan 2012 17:31:54 -0500 Date: Fri, 6 Jan 2012 22:31:48 +0000 From: Ben Hutchings To: Greg KH Cc: Geert Uytterhoeven , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org, Linux-Arch Message-ID: <20120106223148.GN20752@decadent.org.uk> References: <20120106201126.GA7239@kroah.com> <20120106220608.GA20623@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20120106220608.GA20623@suse.de> User-Agent: Mutt/1.5.20 (2009-06-14) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ben@decadent.org.uk Subject: Re: [GIT PATCH] driver core merge for 3.3 X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on shadbolt.decadent.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 06, 2012 at 02:06:08PM -0800, Greg KH wrote: > On Fri, Jan 06, 2012 at 10:38:41PM +0100, Geert Uytterhoeven wrote: > > On Fri, Jan 6, 2012 at 21:11, Greg KH wrote: > > > Ben Hutchings (1): > > >      topology: Provide CPU topology in sysfs in !SMP configurations > > > > FWIW, as reported before, I can confirm that 3.2.0-next-20120106 crashes > > on m68k during boot: [...] > > Disabling lock debugging due to kernel taint > > Kernel panic - not syncing: Attempted to kill init! > > > > Reverting the above commit (ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b) > > fixes it. > > > > So to preserve bisectability, you may want to drop this ommit until the > > UP-only archs have been fixed. > > Ick, sorry for missing that report, you are right. > > Ben, I thought this patch was for UP systems, how did this work on your > testing? It works just fine on UP x86. However I have been made aware that it breaks on m68k and I told you as much in <1325462025.13595.189.camel@deadeye>: > None of these architectures appears to call register_cpu(): > > c6x frv h8300 m68k microblaze openrisc score um xtensa > > and therefore they will all panic at boot following this change (commit > ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b). So either I can try to fix > them or else it must be reverted for now. Ben. > Linus, can you revert this, or I can if you want me to. > > thanks, > > greg k-h > -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus