From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754686Ab1ALK6a (ORCPT ); Wed, 12 Jan 2011 05:58:30 -0500 Received: from www.tglx.de ([62.245.132.106]:57253 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753157Ab1ALK61 (ORCPT ); Wed, 12 Jan 2011 05:58:27 -0500 Date: Wed, 12 Jan 2011 11:57:50 +0100 (CET) From: Thomas Gleixner To: =?ISO-8859-15?Q?Uwe_Kleine-K=F6nig?= cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de, Nick Piggin , Soren Sandmann , Steven Rostedt , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Arjan van de Ven , Frederic Weisbecker , Arnaldo Carvalho de Melo Subject: Re: BUG: spinlock recursion (sys_chdir, user_path_at, do_path_lookup ...) In-Reply-To: <20110112075229.GZ24920@pengutronix.de> Message-ID: References: <20110111110539.GP24920@pengutronix.de> <20110112075229.GZ24920@pengutronix.de> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463795968-1577090938-1294829872=:12146" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463795968-1577090938-1294829872=:12146 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Wed, 12 Jan 2011, Uwe Kleine-König wrote: > > [ 75.280000] r5:be961ee4 r4:00063015 > > > > I started to bisect, but already the first test case showed a different > > error (my getty dying every few seconds). > I bisected this one now, the first bad commit is > > 9c0729d (x86: Eliminate bp argument from the stack tracing routines) > > . It made a x86 specific change to include/linux/stacktrace.h. As I said on IRC already, that's complete nonsense. The commit changes a function prototype which is only relevant for x86. So how should that affect ARM ? > According to tglx the lockup above "is related to nicks scalability > stuff". I havn't researched yet the offending commit. Is that > necessary? Only if you are interested that the problem gets fixed. Thanks, tglx ---1463795968-1577090938-1294829872=:12146--