kern/134658: [bce] bce driver fails on PowerEdge m610 blade.
Oliver Fromme
olli at lurza.secnetix.de
Thu Jan 21 19:11:49 UTC 2010
David Christensen wrote:
> Oliver Fromme wrote:
> > While trying to debug the same issue I stumbled across this
> > thread ... We've got HS22 blades (IBM BladeCenter) which
> > habe the BCM5709S and suffer from exactly the same problem.
> >
> > Dave, are there any news regarding the PHY implementation?
> >
> > If there's decent documentation I might even give it a try
> > myself, provided that it's not too complex. (I've done
> > hardware programming before, but I've never touched a NIC/PHY
> > driver, except for very trivial fixes.)
> >
>
> Pyunh has taken an active interest in this effort and sent out
> a patch yesterday, though he doesn't have hardware to test. I'm
> planning on giving his patch a try today to see how close he got
> on his first attempt.
Thank you very much to both of you!
With that patch applied, the 5709S PHY is correctly attached
by brgphy and "seems to work". I can't test it thoroughly
right now, though, because there is no cable attached to the
port ... The machine is located in a customer's datacenter
in a different city and I'll have to ask someone to connect
the ports. This is a little bit complicated in that company. :-)
I will continue testing as soon as there's a physical link.
For now, this is what ifconfig says (bce0 only; bce1 is the
same):
bce0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
capabilities=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:21:5e:98:f6:6c
media: Ethernet autoselect (autoselect <half-duplex>)
status: no carrier
supported media:
media autoselect
media 1000baseSX mediaopt full-duplex
media none
Here's an excerpt from dmesg (verbose boot):
bce0: <Broadcom NetXtreme II BCM5709 1000Base-SX (C0)> mem 0x92000000-0x93ffffff irq 30 at device 0.0 on pci16
bce0: attempting to allocate 1 MSI vectors (16 supported)
msi: routing MSI IRQ 260 to local APIC 0 vector 112
bce0: using IRQ 260 for MSI
miibus2: <MII bus> on bce0
brgphy2: <BCM5709S 1000/2500baseSX PHY> PHY 2 on miibus2
brgphy2: OUI 0x0050ef, model 0x003f, rev. 0
brgphy2: 1000baseSX-FDX, auto
bce0: bpf attached
bce0: Ethernet address: 00:21:5e:98:f6:6c
bce0: [MPSAFE]
bce0: [ITHREAD]
bce0: ASIC (0x57092000); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.0.6); Flags (MSI|MFW); MFW (NCSI 2.0.3)
And relevant parts from devinfo -rv:
pcib6 pnpinfo vendor=0x8086 device=0x340e subvendor=0x1014 subdevice=0x340e class=0x060400 at slot=7 function=0 handle=\_SB_.PCI0.ETH1
pci16
bce0 pnpinfo vendor=0x14e4 device=0x163a subvendor=0x1014 subdevice=0x0370 class=0x020000 at slot=0 function=0
Interrupt request lines:
260
I/O memory addresses:
0x92000000-0x93ffffff
miibus2
brgphy2 pnpinfo oui=0x50ef model=0x3f rev=0x0 at phyno=2
Finally pciconf -lcv:
bce0 at pci0:16:0:0: class=0x020000 card=0x03701014 chip=0x163a14e4 rev=0x20 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme II BCM5709S Gigabit Ethernet'
class = network
subclass = ethernet
cap 01[48] = powerspec 3 supports D0 D3 current D0
cap 03[50] = VPD
cap 05[58] = MSI supports 16 messages, 64 bit enabled with 1 message
cap 11[a0] = MSI-X supports 9 messages in map 0x10
cap 10[ac] = PCI-Express 2 endpoint max data 256(512) link x4(x4)
The complete files (dmesg etc.) can be found here:
http://www.secnetix.de/olli/dmesg/hs22/
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"IRIX is about as stable as a one-legged drunk with hypothermia
in a four-hundred mile per hour wind, balancing on a banana
peel on a greased cookie sheet -- when someone throws him an
elephant with bad breath and a worse temper."
-- Ralf Hildebrandt
More information about the freebsd-net
mailing list