From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew de Quincey Subject: Re: Re: Possible quick fix for ACPI routing problem on Nforce2 Date: Sun, 13 Jul 2003 20:35:17 +0100 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <200307132035.17596.adq_dvb@lidskialf.net> References: <200307122352.45704.adq_dvb@lidskialf.net> <200307130218.44398.adq_dvb@lidskialf.net> <20030713053913.GB1284@middle.of.nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20030713053913.GB1284-4cpIIuwL6H0O5nXqB3HebLNAH6kLmebB@public.gmane.org> Content-Disposition: inline Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: thunder7-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org > No joy on VIA KT400 chipset (bugzilla #678): ide0 get's IRQ 17, during > boot multiple oopses occur, starting with 'IRQ 17: nobody cared' right > after probing hda. Eventually it crashes hard, after probing hde. I think this is related to the same problem. I've looked at your DSDT dump. It doesn't have the same style of IRQ definitions that mine has... It defines most of your IRQs as being connected to specific global system interrupt numbers (p165, ACPI v2.0b) (Mine has all interrupts directed at link devices). However, IRQ 17 will be set up as a PCI-standard IRQ... So its _probably_ that the first IDE device is expecting a different signalling standard to that which it is getting... If you were able to get to a command prompt you'd probably see /proc/interrupts showing millions of spurious IRQs like I did. ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1