From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762936AbYESViT (ORCPT ); Mon, 19 May 2008 17:38:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756273AbYESViJ (ORCPT ); Mon, 19 May 2008 17:38:09 -0400 Received: from az33egw01.freescale.net ([192.88.158.102]:36894 "EHLO az33egw01.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755440AbYESViI (ORCPT ); Mon, 19 May 2008 17:38:08 -0400 Message-ID: <4831F364.8020702@freescale.com> Date: Mon, 19 May 2008 16:38:44 -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> <4831ECF0.5090101@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: >> 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. > > Disk is on a muxed PCI interrupt. None of the other interrupts on the > mux is fireing at the time. Regardless of whether they're firing, any request_irq with IRQF_NODELAY will turn off threading for all handlers. > Is is possible that the demuxer is not set up right? It is based loosely > on pq2-pci-pic.c Try calling irq_set_chip_and_handler() with handle_level_irq, rather than irq_set_chip(). The -rt patch doesn't seem to have threadified the __do_IRQ() path. -Scott