Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755992AbXKKVVR (ORCPT ); Sun, 11 Nov 2007 16:21:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753532AbXKKVVF (ORCPT ); Sun, 11 Nov 2007 16:21:05 -0500 Received: from py-out-1112.google.com ([64.233.166.178]:21322 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753440AbXKKVVC (ORCPT ); Sun, 11 Nov 2007 16:21:02 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=thMVv+rxvGSb8uxb0pzOHVb3XZY5tSJSSBl/oeASVc7V05ye8BmPyGhDFZ6Ha7Z+xfWqG3SxYQh97mckUpFU9iX5YKsjtDRHjorH9R3FU4LurcS2UGq59fzTHnyjJiyK9BcVOxEaeXADt4iX+wb8A8vRNruriDVvLfvUL39LLIU= Message-ID: <8b67d60711111321j293a0a81r41cf4c604f47932c@mail.gmail.com> Date: Sun, 11 Nov 2007 21:21:01 +0000 From: "Adrian McMenamin" To: "Dmitry Adamushko" Subject: Re: Race in setup_irq? Cc: linux-kernel@vger.kernel.org, linuxsh-dev@lists.sourceforge.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8b67d60711111152he10da17o44bb124e96373ebc@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1472 Lines: 41 On 11/11/2007, Dmitry Adamushko wrote: > On 11/11/2007, Adrian McMenamin wrote > > I am writing a device driver for the Dreamcast CD Drive (the "GD Rom") > > and I am hitting what looks like some sort of race in > > kernel/irq/manage.c. Can anybody point me in the right direction or is > > there a bug here? > > > > This never seems to return in setup_irq: > > > > spin_unlock_irqrestore(&desc->lock, flags); > > > > (line 597) > > I guess, you are referring to setup_irq() (the line without a > particular kernel version doesn't make much sense). > Sorry, it was in the config: 2.6.24-rc2 > What do you mean by "never seems to return"? Does your machine hang? > > If so, the reason might be some kind of (logical) error in your ISR. > spin_unlock_irqrestore() unmasks the interrupts and your target device > might have already generated an interrupt by this moment (sure, it > depends on the initialization logic of your code and device spec.)... > --> ISR runs and due to some error e.g. loops endlessly/deadlocks/etc. > > Tried placing printk() at the beginning of ISR? > You are absolutely right. Sorry for wasting evetybody's time and thanks for the tip! - 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/