kern/91594: [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/1000 MT 4-port NIC in PCI slot 3 of DL380 G4 [regression]

John Baldwin jhb at freebsd.org
Tue Jun 7 18:07:02 UTC 2011


On Tuesday, June 07, 2011 10:20:08 am Rudolf Polzer wrote:
> The following reply was made to PR kern/91594; it has been noted by GNATS.
> 
> From: Rudolf Polzer <rpolzer at mucke-novak.de>
> To: "bug-followup at FreeBSD.org" <bug-followup at FreeBSD.org>, "bad at bsd.de"
> 	<bad at bsd.de>
> Cc:  
> Subject: Re: kern/91594: [em] FreeBSD &gt; 5.4 w/ACPI fails to detect Intel
>  Pro/1000 MT 4-port NIC in PCI slot 3 of DL380 G4 [regression]
> Date: Tue, 7 Jun 2011 16:10:44 +0200
> 
>  Hi,
>  
>  I just tried this on a such a server, and get the same issue even with the =
>  snapshot of 8-STABLE on the freebsd ftp server. However, 9-CURRENT kernel p=
>  anics from a possibly related, possibly unrelated issue:
>  
>  The trace is:
>  
>  kdb_enter() at kdb_enter+0x3b
>  panic() at panic+0x180
>  rman_init() at rman_init+0x17c
>  pcib_alloc_window() at pcib_allow_window+0x9f
>  pcib_attach_common() at pcib_attach_common+0x457
>  acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x1c
>  device_attach() at device_attach+0x69
>  bus_generic_attach() at bus_generic_attach+0x1a

Can you get the panic message?   This seems really odd as rman_init() will
only panic if rm_type is set to an invalid setting, but it should always be
correct in this case:

        w->rman.rm_type = RMAN_ARRAY;
        snprintf(buf, sizeof(buf), "%s %s window",
            device_get_nameunit(sc->dev), w->name);
        w->rman.rm_descr = strdup(buf, M_DEVBUF);
        error = rman_init(&w->rman);

-- 
John Baldwin


More information about the freebsd-acpi mailing list