From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754741Ab1AGUX1 (ORCPT ); Fri, 7 Jan 2011 15:23:27 -0500 Received: from casper.infradead.org ([85.118.1.10]:36982 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752602Ab1AGUX0 convert rfc822-to-8bit (ORCPT ); Fri, 7 Jan 2011 15:23:26 -0500 Subject: Re: sparc boot failure due to perf init From: Peter Zijlstra To: Sam Ravnborg Cc: David Miller , lkml , sparclinux In-Reply-To: <20110107201805.GA28104@merkur.ravnborg.org> References: <20110107201805.GA28104@merkur.ravnborg.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Fri, 07 Jan 2011 21:23:52 +0100 Message-ID: <1294431832.2016.457.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2011-01-07 at 21:18 +0100, Sam Ravnborg wrote: > This was introduced by: > "perf, arch: Cleanup perf-pmu init vs lockup-detector" - 004417a6d468e24399e383645c068b498eed84ad > > I did not see any obvious fix. > (To avoid it is simple - I can disable it in my config). Or you can switch back to arch_initcall() for now, it'll cause the generic watchdog stuff not to work, but that's a lot less important. I'll have a chat with Dave on how to best sort all this.