kern/140970: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8

Benjamin Kormann kormann at itm.tum.de
Sat Nov 28 13:40:02 UTC 2009


>Number:         140970
>Category:       kern
>Synopsis:       [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 28 13:40:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Benjamin Kormann
>Release:        7.2 and 8
>Organization:
Technische Universität München (Technical University of Munich) Germany
>Environment:
>Description:
I have installed a FreeBSD 7.2 (and also FreeBSD 8) on our HP Bl460c G1 Blade system with two Xeon processors and 32 GB RAM. This blade comes with two embedded network controllers and in our case an additionally attached Mezzanine card for two more network controllers. Right after the first boot (GENERIC KERNEL) only the embedded network interfaces get properly configured for use. The additional Broadcom NetXtreme II family NICs of the Mezzanine card (HP NC382m DP 1GbE Multifunction BL-c Adapter) are correctly identified by the bce-driver, but lead to the following kernel debug output:

No PHY found on child MII bus

So the NICs are bound to a logical network card identifier like bce1, but they never become ready to be configured via ifconfig.

$ dmesg | grep bce1
bce1: <HP NC382m DP 1GbE Multifunction BL-c Adapter (C0)> mem 0xfc000000-0xfdffffff irq 18 at device 0.0 on pci16
bce1: /usr/src/sys/dev/bce/if_bce.c(1097): No PHY found on child MII bus!
device_attach: bce1 attach returned 6

partial output of:
$ pciconf -lv
pcib4 at pci0:6:0:0:       class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'Broadcom dual gigabit, pci bridge (BCM5715)'
    class      = bridge
    subclass   = PCI-PCI
bce0 at pci0:7:0:0:        class=0x020000 card=0x703b103c chip=0x16ac14e4 rev=0x12 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5708S Gigabit Ethernet'
    class      = network
    subclass   = ethernet
pcib8 at pci0:10:0:0:      class=0x060400 card=0x00000000 chip=0x01031166 rev=0xb4 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'Broadcom dual gigabit, pci bridge (BCM5715)'
    class      = bridge
    subclass   = PCI-PCI
pcib9 at pci0:11:4:0:      class=0x060400 card=0x00000000 chip=0x01041166 rev=0xb2 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'HT1000 PCI/PCI-X bridge'
    class      = bridge
    subclass   = PCI-PCI
bce1 at pci0:16:0:0:       class=0x020000 card=0x171d103c chip=0x163a14e4 rev=0x20 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5709S Gigabit Ethernet'
    class      = network
    subclass   = ethernet
bce2 at pci0:16:0:1:       class=0x020000 card=0x171d103c chip=0x163a14e4 rev=0x20 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5709S Gigabit Ethernet'
    class      = network
    subclass   = ethernet
pcib15 at pci0:2:0:0:      class=0x060400 card=0x00000000 chip=0x01031166 rev=0xc3 hdr=0x01
    vendor     = 'ServerWorks (Was: Reliance Computer Corp)'
    device     = 'Broadcom dual gigabit, pci bridge (BCM5715)'
    class      = bridge
    subclass   = PCI-PCI
bce3 at pci0:3:0:0:        class=0x020000 card=0x703b103c chip=0x16ac14e4 rev=0x12 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme II BCM5708S Gigabit Ethernet'
    class      = network
    subclass   = ethernet

>How-To-Repeat:
It occurs and remains always. There hasn't been a problem fix so far. Each fresh installation or reboot after the installation bring this issue up front.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list