Subject: Re: port-i386/37001 (acpi enabled kernel locks up bringing up fxp0 NIC)
To: None <gnats-bugs@NetBSD.org, joerg@NetBSD.org, gnats-admin@netbsd.org,>
From: Christos Zoulas <christos@zoulas.com>
List: netbsd-bugs
Date: 10/31/2007 18:57:13
On Oct 31, 9:50pm, mathias@woei.be (Mathias De Belder) wrote:
-- Subject: Re: port-i386/37001 (acpi enabled kernel locks up bringing up fxp
| 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: Wed, 31 Oct 2007 19:34:23 +0100
|
| On Tue, Oct 30, 2007 at 11:05:09PM +0000, Joerg Sonnenberger wrote:
| > > Synopsis: acpi enabled kernel locks up bringing up fxp0 NIC
| >
| > Please try the attached patch.
| >
| > Joerg
| >
| > --cvVnyQ+4j833TQvp
| > Content-Type: text/plain; charset=us-ascii
| > Content-Disposition: attachment; filename="acpi_pci_link.c.diff"
| >
| > Index: acpi_pci_link.c
| > ===================================================================
| > RCS file: /data/repo/netbsd/src/sys/dev/acpi/acpi_pci_link.c,v
| > retrieving revision 1.7
| > diff -u -r1.7 acpi_pci_link.c
| > --- acpi_pci_link.c 24 Sep 2006 06:03:20 -0000 1.7
| > +++ acpi_pci_link.c 30 Oct 2007 18:59:08 -0000
| > @@ -987,7 +987,7 @@
| > * If this is an ISA IRQ, try using the SCI if it is also an ISA
| > * interrupt as a fallback.
| > */
| > - if (link->l_isa_irq) {
| > + if (link->l_isa_irq && !PCI_INTERRUPT_VALID(best_irq)) {
| > pos_irq = AcpiGbl_FADT->SciInt;
| > pos_weight = pci_link_interrupt_weights[pos_irq];
| > if (pos_weight < best_weight) {
| >
| > --cvVnyQ+4j833TQvp--
|
| I have applied the attached patch against netbsd-4 sources updated 2
| days ago and rebuilt a kernel using an unaltered GENERIC config.
|
| Unfortunately, the problem still persists. The machine locks up right
| after bringing up fxp0. If you have any more ideas or patches to try
| out, I'll be happy to test them out.
Is that an SSP kernel? I have the same problem with an SSP kernel.
christos