From owner-freebsd-current@FreeBSD.ORG  Mon Sep 13 22:36:19 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 187AA16A4CE; Mon, 13 Sep 2004 22:36:19 +0000 (GMT)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C256A43D2D; Mon, 13 Sep 2004 22:36:18 +0000 (GMT)
	(envelope-from nate@root.org)
Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net
	[67.127.84.57])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i8DMaCDl007876;
	Mon, 13 Sep 2004 15:36:15 -0700
Message-ID: <414620DB.9070509@root.org>
Date: Mon, 13 Sep 2004 15:36:11 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: msch@snafu.de
References: <200408141854.38477.msch@snafu.de>
	<200408211927.36948.msch@snafu.de> <200409121046.02724.msch@snafu.de>
In-Reply-To: <200409121046.02724.msch@snafu.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
cc: andre@freebsd.org
Subject: Re: ISDN4BSD broken...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2004 22:36:19 -0000

Matthias Schuendehuette wrote:
>>>Aug 14 18:19:46 current kernel: FreeBSD 5.2-CURRENT #0: \
>>> Sat Aug 14 17:43:56 CEST 2004
>>>[...]
>>>Aug 14 18:19:46 current kernel: ACPI link \_SB_.PCI0.LNKA \
>>> has invalid initial irq 9, ignoring
>>>(this is a new message, which doesn't show up with my Aug 11
>>>kernel) [...]
>>>Aug 14 18:19:46 current kernel: isic0: [GIANT-LOCKED]
>>>Aug 14 18:19:46 current kernel: isic0 at port \
>>> 0x580-0x59f,0x180-0x19f,0x980-0x99f,0xd80-0xd9f \
>>> irq 10 flags 0x3 on isa0
>
>>>Any ideas? ACPI or IRQ-Routing related?

It's probably IRQ routing related.  Try changing the check in
acpi_pci_link_is_valid_irq() to this:

if (link->interrupts[i] == irq || AcpiGbl_FADT->SciInt == irq)

I've suspected that it should always be ok to load a device onto the SCI
since Windows does this for many systems.  However, this change would
break other systems that it's not valid for.  This hack should only be
done in the case where we're routing the initial IRQ.  If the initial
irq == the SCI then allow it, otherwise don't allow the SCI as valid.

-- 
Nate