From owner-freebsd-acpi@FreeBSD.ORG  Tue Nov 16 23:21:30 2004
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9B2A316A4CE; Tue, 16 Nov 2004 23:21:30 +0000 (GMT)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6287343D1D; Tue, 16 Nov 2004 23:21:30 +0000 (GMT)
	(envelope-from nate@root.org)
Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net
	[67.119.74.222])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNLQC4006089
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 16 Nov 2004 15:21:26 -0800
Message-ID: <419A8B75.4060000@root.org>
Date: Tue, 16 Nov 2004 15:21:25 -0800
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andrew Gallatin <gallatin@cs.duke.edu>
References: <200411111737.00537.jhb@FreeBSD.org>
	<200411161339.13818.jhb@FreeBSD.org>
	<16794.28367.159895.3565@grasshopper.cs.duke.edu>
	<200411161647.14543.jhb@FreeBSD.org>
	<16794.33094.416989.88341@grasshopper.cs.duke.edu>
In-Reply-To: <16794.33094.416989.88341@grasshopper.cs.duke.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-acpi@FreeBSD.org
cc: scottl@FreeBSD.org
cc: John Baldwin <jhb@FreeBSD.org>
Subject: Re: New ACPI PCI Link Routing code
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Nov 2004 23:21:30 -0000

Andrew Gallatin wrote:
> John Baldwin writes:
>  > On Tuesday 16 November 2004 04:19 pm, Andrew Gallatin wrote:
>  > > "panic: link_add_crs: too many interrupts"
>  > >
>  > > Full boot -v output at:
>  > > http://people.freebsd.org/~gallatin/pcilink.boot
>  > >
>  > > This is from a machine with an evil ACPI (but I don't want to mess
>  > > with it for fear of breaking the machine).
>  > 
>  > Ok, that's weird.  Can you hack the link_add_crs() function to print out the 
>  > number of interrupts before the KASSERT()'s if it is not 1?
> 
> There are 3 interrupts.  Eg:
> 
> pci_link1: <ACPI PCI Link LN00> on acpi0
> 3 interrupts
> panic: link_add_crs: too many interrupts
> 
> If you want me to extract any acpi info, just say the word (and let me
> know what the incantation is).  I have the asl and the dsdt I
> extracted ages ago saved in ~gallatin/trinity.tgz on freefall.

You'll need ASL to debug this, acpidump -t -d > trinity.asl
It seems very surprising that _CRS would return 3 interrupts.  I'm 
guessing the first is the active one?

-- 
Nate