From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762921AbYESVKn (ORCPT ); Mon, 19 May 2008 17:10:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758738AbYESVKe (ORCPT ); Mon, 19 May 2008 17:10:34 -0400 Received: from az33egw01.freescale.net ([192.88.158.102]:52427 "EHLO az33egw01.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758559AbYESVKe (ORCPT ); Mon, 19 May 2008 17:10:34 -0400 Message-ID: <4831ECF0.5090101@freescale.com> Date: Mon, 19 May 2008 16:11:12 -0500 From: Scott Wood User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Rune Torgersen CC: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: Oops with PREEMPT-RT on 2.6.25.4 References: <4831D527.2020907@freescale.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Almost certainly the latter. Is the disk interrupt shared with any other interrupts, that are marked IRQF_NODELAY? The -rt patch doesn't seem to handle mixing the two well. Oh, and just to be sure: you do have CONFIG_PREEMPT_RT turned on, and not just CONFIG_PREEMPT, right? The non-preempt-rt versions in the -rt patch don't look like they disable interrupts, though I may just be getting lost in a sea of underscores and ifdefs. -Scott