Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 19 Mar 2003 18:10:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 19 Mar 2003 18:10:15 -0500 Received: from modemcable092.130-200-24.mtl.mc.videotron.ca ([24.200.130.92]:27269 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Wed, 19 Mar 2003 18:10:14 -0500 Date: Wed, 19 Mar 2003 18:17:42 -0500 (EST) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: Linux Kernel cc: Linus Torvalds , Ingo Molnar , Andi Kleen Subject: Re: [PATCH][2.5] Fail setup_irq for unconfigured IRQs In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1016 Lines: 25 On Wed, 19 Mar 2003, Zwane Mwaikambo wrote: > This patch makes us bail out in case we may have an interrupt which > couldn't be associated with an interrupt controller. Without this we allow > unconfigured interrupts to be assigned and then later on we get > "unexpected IRQ trap at vector xx" during the ack phase. > > scenario: > This can occur if we fail irq setup during setup_IO_APIC_irqs for some > reason or other and then miss getting assigned a vector. Later on we then > get assigned no_irq_type as our handler. Here is a sample /proc/interrupts from an affected system... 41: 1313 796 1298 1380 IO-APIC-level qlogicisp 89: 0 0 0 0 none qlogicisp Please apply, Zwane - 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/