Hi List,

I've run into an issue trying to install a new PowerEdge R720 server that arrived this week. It is equipped with a broadcom 5720 quad port network interface daughter card. I installed wheezy on it. No problems! The network interface works, and does not require any non-free firmware.

Then I installed a xen kernel, and because of that update-initramfs was ran. I noticed these warnings:

root@server:~# update-initramfs -uk all
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3

These files are listed in the firmware-linux-nonfree package description for squeeze, I thought I'd give this package a try and install it.

From that moment on eth0 is not working anymore. I get these kernel messages:

[ 1796.583881] tg3 0000:01:00.0: eth0: transmit timed out, resetting
[ 1797.840909] tg3 0000:01:00.0: eth0: 0x00000000: 0x165f14e4, 0x00100406, 0x02000000, 0x00800010 [ 1797.841066] tg3 0000:01:00.0: eth0: 0x00000010: 0xd91a000c, 0x00000000, 0xd91b000c, 0x00000000
....
[ 1797.935588] tg3 0000:01:00.0: eth0: 0x00007030: 0x000e0000, 0x0000486c, 0x00170030, 0x00000000 [ 1797.935745] tg3 0000:01:00.0: eth0: 0: Host status block [00000005:00000003:(0000:0000:0000):(0000:0000)] [ 1797.935911] tg3 0000:01:00.0: eth0: 0: NAPI info [00000003:00000003:(0000:0000:01ff):0000:(00e9:0000:0000:0000)] [ 1797.936070] tg3 0000:01:00.0: eth0: 1: Host status block [00000001:0000001c:(0000:0000:0000):(001b:0000)] [ 1797.936226] tg3 0000:01:00.0: eth0: 1: NAPI info [0000000c:0000000c:(0000:0000:01ff):000b:(000b:000b:0000:0000)] [ 1797.936383] tg3 0000:01:00.0: eth0: 2: Host status block [00000001:00000003:(0002:0000:0000):(0000:0000)] [ 1797.936540] tg3 0000:01:00.0: eth0: 2: NAPI info [00000001:00000001:(0001:0000:01ff):0000:(0000:0000:0000:0000)] [ 1797.936697] tg3 0000:01:00.0: eth0: 3: Host status block [00000001:0000000e:(0000:0000:0000):(0000:0000)] [ 1797.936853] tg3 0000:01:00.0: eth0: 3: NAPI info [0000000c:0000000c:(0000:0000:01ff):000b:(000b:000b:0000:0000)] [ 1797.937012] tg3 0000:01:00.0: eth0: 4: Host status block [00000001:00000011:(0000:0000:0010):(0000:0000)] [ 1797.937168] tg3 0000:01:00.0: eth0: 4: NAPI info [0000000c:0000000c:(0000:0000:01ff):000b:(000b:000b:0000:0000)]
[ 1797.980164] tg3 0000:01:00.0: eth0: Link is down
[ 1802.092252] tg3 0000:01:00.0: eth0: Link is up at 1000 Mbps, full duplex
[ 1802.092257] tg3 0000:01:00.0: eth0: Flow control is on for TX and on for RX
[ 1802.092261] tg3 0000:01:00.0: eth0: EEE is disabled
[ 1807.591630] tg3 0000:01:00.0: eth0: transmit timed out, resetting
... and so on

I tried the debian installer again, but even then it's not able to get a DHCP IP address using eth0. eth1 is working fine.

I booted back into the machine, purged the firmware-linux-nonfree package and am currently using eth1, that is still working:

[ 1856.825856] tg3 0000:01:00.1: eth1: Link is up at 1000 Mbps, full duplex

Now what happened?

My *guess* is that the Broadcom 5720 for some reason is detected as one of these cards
 * Broadcom BCM5703/BCM5704 TSO firmware for tigon/tg3_tso.bin)
 * Broadcom BCM5701A0 firmware (tigon/tg3.bin)
 * Broadcom BCM5705 TSO firmware (tigon/tg3_tso5.bin)

Then it loads that firmware blob onto the network card, breaking it.

And now what?

I have a bricked eth0. I really like to repair before the machine goes into production. Suggestions anyone?

Should a debian package be fixed? It appears that the Broadcom 5720 does not need a firmware blob to operate. http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/tigon has the same files as the firmware-linux-nonfree package plus one added 7 days ago for '57766 cards'. So nothing important there.

There must be some code somewhere that decides what firmware to use. Possibly the tg3.ko driver in linux-image-3.2.0-4-amd64?

Hope you can help me and avoid more broken Broadcom 5720's.

Greetings, Casper

Reply via email to