Here's my update:
First of all a new finding: The server has two Broadcom NICs on board - both
driven by the tg3 kernel module. eth0 is the one I have trouble with, eth1
works without problems - quite strange...
Second, I've upgraded to 3.2.0-20.32 as I noticed its release - but
there's no change in behavior.
Third, I've installed the mainline/vanilla linux package linux-
image-3.3.0-030300-generic_3.3.0-030300.201203182135_amd64.deb and it
fixes this bug completely - no register dumps, no DMA errors and two
working NICs :)
Finally here are my steps to reproduce the problem about beeing not able to
pass any traffic via the (first) NIC - actually quite straight forward:
1. Set the interface up (ip link set dev eth0 up)
2. Assign an IP address - either manually (ip addr add dev eth0 192.0.0.1/24)
or by running dhclient -v eth0 (but dhclient fails to get any DHCP lease)
3. ping a host on the same subnet -> No reply received and no entry in the ARP
cache (ip neig)
Oh, and I use the same network cable, connected to the same switch port, for
all the tests. So I'm quite sure it's not related to stupid things like a
broken network cable or defective switch port.
The USB NIC you saw was just a quick workaround to be able to upload
debug information for this bug before I was aware eth1 is actually
working.
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961239
Title:
Broadcom NIC (tg3) not working with DMA errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961239/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
