Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753149AbYJ2HUY (ORCPT ); Wed, 29 Oct 2008 03:20:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752213AbYJ2HUH (ORCPT ); Wed, 29 Oct 2008 03:20:07 -0400 Received: from smtp119.sbc.mail.sp1.yahoo.com ([69.147.64.92]:23880 "HELO smtp119.sbc.mail.sp1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752020AbYJ2HUG (ORCPT ); Wed, 29 Oct 2008 03:20:06 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=3sPlSNFlouoMgJaW/qmnegpaLC2R2xQ9+2XbfrjWNGDFWmsDJvzASLzRl/ngIvhf9HrJ24QUA1PuDk/vhl9HAop14MrhC1Vsi3Puv3832va9kmyHpSunn0UT35OMRkRPQPEKD3uKx8rQrO/b7F2E9Q8Ui7gBWNtnMeys3eyov5s= ; X-YMail-OSG: c2eqQJwVM1l12xVnchP8DCqLapsIohEGfmYgk5tFfNGRoI9glQyF.nrOKKswlPUW8LCaZV_kqaw6fr0t_LA2pniux9lznsNOj0VqOquva36mTWKkSHGvxeJhtbplG_NWMieYKmQxqAyMHkxe_UnXaYR7y5prdeQU5Wx2tj0- X-Yahoo-Newman-Property: ymail-3 From: David Brownell To: Peter Zijlstra Subject: Re: [patch 2.6.28-rc2] at91_mci: workaround lockdep Date: Wed, 29 Oct 2008 00:20:03 -0700 User-Agent: KMail/1.9.10 Cc: Pierre Ossman , lkml , Ingo Molnar , Russell King , Nicolas Ferre , Andrew Victor , Thomas Gleixner References: <200810271426.27110.david-b@pacbell.net> <1225213442.15763.20.camel@lappy.programming.kicks-ass.net> <200810281022.42803.david-b@pacbell.net> In-Reply-To: <200810281022.42803.david-b@pacbell.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810290020.03953.david-b@pacbell.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 714 Lines: 21 On Tuesday 28 October 2008, David Brownell wrote: > > > > Workaround: depend on LOCKDEP=n ... Note that LOCKDEP causes the BUG() on line 1159 of drivers/mmc/host/omap.c to fire too -- exactly the same root cause: IRQ handler getting called in a goofy context, because of lockdep. That's the older OMAP1/OMAP2 driver ... the new highspeed MMC controller in OMAP3 (handling 8-bit parallel I/O etc, nyet in mainline) doesn't seem to have the same issue(s). - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/