Subject: Re: port-i386/37001 (acpi enabled kernel locks up bringing up fxp0
To: None <joerg@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: Mathias De Belder <mathias@woei.be>
List: netbsd-bugs
Date: 11/09/2007 19:05:04
The following reply was made to PR port-i386/37001; it has been noted by GNATS.
From: Mathias De Belder <mathias@woei.be>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-i386/37001 (acpi enabled kernel locks up bringing up fxp0
NIC)
Date: Fri, 9 Nov 2007 20:01:17 +0100
On Thu, Nov 08, 2007 at 10:25:04PM +0000, Joerg Sonnenberger wrote:
> On Thu, Nov 08, 2007 at 09:05:15PM +0000, Mathias De Belder wrote:
>> It is picking a different IRQ number now, but the machine still locks up
>> when bringing up fxp0. I've attached the dmesg output of boot -v and a
>> pcidump with your attached patch on top of rev 1.9:
>
> Just to rule out other changes, does a CURRENT kernel work on this
> machine or not? I'm running out of ideas what is broken here.
I just built and tested two CURRENT kernels (with sources of today), but
they exhibit exactly the same problem. When your patch is applied to
acpi_pci_link.c, the IRQ assigned to fxp0 (and auich0) is 5. Without
the patch, it is 9. This is the same as on a netbsd-4 kernel. When a
kernel with no acpi support is booted, the IRQ assigned to fxp0 (as well
as auich0, fwohci0, uhci0-2, ehci0 and cbb0) is 11.
Mathias