Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262303AbVAEJkR (ORCPT ); Wed, 5 Jan 2005 04:40:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262307AbVAEJkR (ORCPT ); Wed, 5 Jan 2005 04:40:17 -0500 Received: from webapps.arcom.com ([194.200.159.168]:23556 "EHLO webapps.arcom.com") by vger.kernel.org with ESMTP id S262303AbVAEJkI (ORCPT ); Wed, 5 Jan 2005 04:40:08 -0500 Message-ID: <41DBB5F6.6070801@cantab.net> Date: Wed, 05 Jan 2005 09:40:06 +0000 From: David Vrabel User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-os@analogic.com CC: Bjorn Helgaas , aryix , lug-list@lugmen.org.ar, Linux kernel Subject: Re: dmesg: PCI interrupts are no longer routed automatically......... References: <20041229095559.5ebfc4d4@sophia> <1104862721.1846.49.camel@eeyore> <1104867678.1846.80.camel@eeyore> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Jan 2005 09:43:22.0703 (UTC) FILETIME=[FF061DF0:01C4F30A] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 592 Lines: 15 linux-os wrote: > > For instance, Level interrupts from PLX chips on the PCI bus > can (read do) generate interrupts when some of the BARS are > being configured. Once you get an unhandled interrupt, you > are dead because there's nothing to reset the line. Why not unconditionally clear all interrupts after configuring the chip? David Vrabel - 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/