Ubuntu
linux-source-2.6.15 package

tg3 module does not work in Latitude D400

Bug #22636 reported by André Anjos on 2005-09-27

Affects		Status	Importance	Assigned to	Milestone
	linux-source-2.6.15 (Ubuntu)	Invalid	Medium	Ben Collins

Bug Description

The tg3 module does not work correctly for my laptop. It is a Dell Latitude
D400, with a builtin gigabit NIC called NetXtreme BCM5705M (from Broadcom). An
lspci is attached to show that the card is detected by the system. The messages
that show up in my 'dmesg' output are (after modprobe -r tg3 && modprobe tg3):

[4296379.676000] ACPI: PCI interrupt for device 0000:01:00.0 disabled
[4296587.169000] tg3.c:v3.31 (June 8, 2005)
[4296587.169000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKC] -> GSI 11
(level, low) -> IRQ 11
[4296598.510000] eth0: Tigon3 [partno(BCM95705A50) rev 3001 PHY(5705)]
(PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:0d:56:4e:2c:99
[4296598.510000] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0]
WireSpeed[1] TSOcap[1]
[4296598.510000] eth0: dma_rwctrl[763f0000]
[4296598.602000] tg3: tg3_reset_hw timed out for eth0, firmware will not restart
magic=4b657654

...and this last message continues on and on.

Which I don't know what means. The card works nicely under windows and used to
work with 2.4.X kernels on other distributions. I'm not sure what the problem
is. Trying to use the broadcom module (distributed by them) makes the machine hang.

The device manager can also detect the card and see it is a network interface,
but that is all. I cannot use it. An interesting behavior is that when I
modprobe the module, the machine freezes temporarily. I'm also not sure what it
means. I wonder if one can get this fixed for the Breezy release still.

The version of the kernel shipped with Hoary also doesn't work. I've tested them
all. Currently I have the latest (as of today) linux kernel module available for
Breezy.

Revision history for this message

André Anjos (andre.anjos-deactivatedaccount-deactivatedaccount) wrote on 2005-09-27:

Output of the command 'lspci -vv' Edit (10.1 KiB, text/plain)

Created an attachment (id=4120)
Output of the command 'lspci -vv'

Revision history for this message

André Anjos (andre.anjos-deactivatedaccount-deactivatedaccount) wrote on 2005-10-27:

Today I found a comparable bug in the Debian lists. It seems unresolved:
http://lists.debian.org/debian-kernel/2004/10/msg00373.html

The original bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278119, still unsolved.

Revision history for this message

Ben Collins (ben-collins) wrote on 2005-12-11:

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Revision history for this message

André Anjos (andre.anjos-deactivatedaccount-deactivatedaccount) wrote on 2005-12-12:

So, I've just got the opportunity to do it:

$ uname -a
Linux jasmim 2.6.15-7-686 #1 SMP PREEMPT Tue Dec 6 18:19:44 UTC 2005 i686 GNU/Linux

But still the same problem. For booting, it takes like 30 seconds once the
kernel is trying to load the module. The whole machines hangs frozen for this
period. I can send any other information from this or the previous kernel if you
would like so.

This is the configuration on /etc/network/interfaces:

$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# This is a list of hotpluggable network interfaces.
# They will be activated automatically by the hotplug subsystem.
mapping hotplug
script grep
map eth1

# The primary network interface
iface eth1 inet dhcp

iface eth0 inet dhcp

auto eth1

auto eth0

Revision history for this message

Ben Collins (ben-collins) wrote on 2006-01-07:

Have you done a firmware upgrade to this card?

Revision history for this message

Ben Collins (ben-collins) wrote on 2006-01-09:

Someone from broadcom noted that the lspci output and dmesg output from the
driver has a partno mismatch. This appears to be incorrect or corrupt firmware.
In either case, it's not a kernel driver bug. You probably need to update with
the correct firmware for your card.