From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by ozlabs.org (Postfix) with ESMTP id 32B86DE247 for ; Tue, 20 May 2008 05:59:25 +1000 (EST) Received: by py-out-1112.google.com with SMTP id z59so1753386pyg.27 for ; Mon, 19 May 2008 12:59:24 -0700 (PDT) Message-ID: <4831DBDC.8000008@gmail.com> Date: Mon, 19 May 2008 15:58:20 -0400 From: Gregory Haskins MIME-Version: 1.0 To: Rune Torgersen Subject: Re: Oops with PREEMPT-RT on 2.6.25.4 References: <4831D527.2020907@freescale.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Scott Wood , linuxppc-dev@ozlabs.org, linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Reply-To: gregory.haskins@gmail.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Rune Torgersen wrote: > Scott Wood wrote: > >> You're recursively entering lock_timer_base, which does a >> spin_lock_irqsave(). Either interrupts are enabled when they should >> not be, or an interrupt was supposed to be threaded that isn't. > > Sort of figured. How do I figure out which one, and how to fix it? > I've never gotten any -rt patchsets to work on this CPU, and it always > seems to be related to the disk driver. > I've tried since 2.6.16 ppc.... (2.6.16, 2.6.18 on ppc, 2.6.24 and 25 on > powerpc) > > Even though this is a custom board, I'm pretty sure I can get it to fail > on a pq2fads board with the same disk controller. Im not sure if LOCKDEP is available for that architecture. Have you tried it? Its pretty good at flushing these kinds of issues out (assuming its available). -Greg