Public bug reported:
Hardy Heron, 2.6.24-17-server, BCM5722 (driver TG3 on Dell PowerEdge
T105) has a weird issue:
If I reboot or remove/reload tg3 with cable connected, the network doesn't
work, even though the system thinks it is up, and link is established.
If I do same with network cable removed, and *then* connect, it works fine!
lspci -vvv:
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit
Ethernet PCI Express
Subsystem: Dell Unknown device 0225
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 219
Region 0: Memory at d0200000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at <ignored> [disabled]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [58] Vendor Specific Information
Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable+
Address: 00000000fee0300c Data: 4162
Capabilities: [d0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <4us, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
Link: Latency L0s <4us, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
dmesg:
[ 33.874633] tg3.c:v3.86 (November 9, 2007)
[ 33.874754] ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 19
[ 33.874756] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK2] -> GSI 19
(level, low) -> IRQ 20
[ 33.874761] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 33.927953] eth0: Tigon3 [partno(BCM95722) rev a200 PHY(5722/5756)] (PCI
Express) 10/100/1000Base-T Ethernet 00:1e:c9:31:be:70
[ 33.927958] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1]
TSOcap[1]
[ 33.927960] eth0: dma_rwctrl[76180000] dma_mask[64-bit]
...
[ 80.866000] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 80.866003] tg3: eth0: Flow control is on for TX and on for RX.
[ 81.797716] NET: Registered protocol family 17
...
(Those lines are repeated several times)
/var/log/daemon.log: (Right after reboot, cable connected!)
May 18 10:27:48 akp-ubu01 NetworkManager: <info> eth0: Device is
fully-supported using driver 'tg3'.
May 18 10:27:48 akp-ubu01 NetworkManager: <info> nm_device_init(): waiting for
device's worker thread to start
May 18 10:27:48 akp-ubu01 NetworkManager: <info> nm_device_init(): device's
worker thread started, continuing.
May 18 10:27:48 akp-ubu01 NetworkManager: <info> Now managing wired Ethernet
(802.3) device 'eth0'.
May 18 10:27:48 akp-ubu01 NetworkManager: <info> Deactivating device eth0.
May 18 10:27:48 akp-ubu01 NetworkManager: <info> Will activate wired
connection 'eth0' because it now has a link.
May 18 10:27:49 akp-ubu01 dhcpd: All rights reserved.
May 18 10:27:49 akp-ubu01 dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Will activate wired
connection 'eth0' because it now has a link.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> SWITCH: no current
connection, found better connection 'eth0'.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Will activate connection
'eth0'.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Device eth0 activation
scheduled...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) started...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) scheduled...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) started...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) scheduled...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) complete.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) starting...
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) successful.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) scheduled.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) complete.
May 18 10:27:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) started...
May 18 10:27:51 akp-ubu01 NetworkManager: <info> Activation (eth0) Beginning
DHCP transaction.
May 18 10:27:51 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) complete.
May 18 10:27:51 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 12
(successfully started) for interface eth0
May 18 10:27:52 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface eth0
May 18 10:27:52 akp-ubu01 dhclient: DHCPREQUEST of 10.50.164.15 on eth0 to
255.255.255.255 port 67
May 18 10:28:13 akp-ubu01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 8
May 18 10:28:21 akp-ubu01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 14
May 18 10:28:35 akp-ubu01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 9
May 18 10:28:44 akp-ubu01 dhclient: No DHCPOFFERS received.
May 18 10:28:44 akp-ubu01 dhclient: Trying recorded lease 10.50.164.15
May 18 10:28:57 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 8
(timeout) for interface eth0
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Timeout) scheduled...
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Timeout) started...
May 18 10:28:57 akp-ubu01 NetworkManager: <info> No DHCP reply received.
Automatically obtaining IP via Zeroconf.
May 18 10:28:57 akp-ubu01 NetworkManager: <info> avahi-autoipd running on
eth0, assuming IPv4LL address
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) scheduled...
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Timeout) complete.
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) started...
May 18 10:28:57 akp-ubu01 NetworkManager: <info> not touching eth0
configuration, was configured externally
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) successful,
device activated.
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Finish
handler scheduled.
May 18 10:28:57 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) complete.
May 18 10:28:57 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 9
(fail) for interface eth0
May 18 10:28:57 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 14
(normal exit) for interface eth0
/var/log/daemon.log: (Same thing, but first rmmod tg3, diconnect cable,
modprobe tg3, connect cable)
May 18 13:22:41 akp-ubu01 NetworkManager: <info> eth0: Device is fully-supporte
d using driver 'tg3'.
May 18 13:22:41 akp-ubu01 NetworkManager: <info> nm_device_init(): waiting for
device's worker thread to start
May 18 13:22:41 akp-ubu01 NetworkManager: <info> nm_device_init(): device's wor
ker thread started, continuing.
May 18 13:22:41 akp-ubu01 NetworkManager: <info> Now managing wired Ethernet (8
02.3) device 'eth0'.
May 18 13:22:41 akp-ubu01 NetworkManager: <info> Deactivating device eth0.
May 18 13:22:41 akp-ubu01 NetworkManager: <info> Will activate wired
connection 'eth0' because it now has a link.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Will activate wired
connection 'eth0' because it now has a link.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> SWITCH: no current
connection, found better connection 'eth0'.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Will activate connection
'eth0'.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Device eth0 activation
scheduled...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) started...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) scheduled...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) started...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) scheduled...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 1 of
5 (Device Prepare) complete.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) starting...
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) successful.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) scheduled.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 2 of
5 (Device Configure) complete.
May 18 13:22:44 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) started...
May 18 13:22:46 akp-ubu01 NetworkManager: <info> Activation (eth0) Beginning
DHCP transaction.
May 18 13:22:46 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 3 of
5 (IP Configure Start) complete.
May 18 13:22:46 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 12
(successfully started) for interface eth0
May 18 13:22:47 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface eth0
May 18 13:22:49 akp-ubu01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 5
May 18 13:22:49 akp-ubu01 dhclient: DHCPOFFER of 10.50.164.15 from 10.50.164.1
May 18 13:22:49 akp-ubu01 dhclient: DHCPREQUEST of 10.50.164.15 on eth0 to
255.255.255.255 port 67
May 18 13:22:49 akp-ubu01 dhclient: DHCPACK of 10.50.164.15 from 10.50.164.1
...
<snipped avahi crud>
...
May 18 13:22:49 akp-ubu01 NetworkManager: <info> DHCP daemon state is now 2
(bound) for interface eth0
May 18 13:22:49 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Get) scheduled...
May 18 13:22:49 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Get) started...
May 18 13:22:49 akp-ubu01 dhclient: bound to 10.50.164.15 -- renewal in 1751
seconds.
May 18 13:22:50 akp-ubu01 NetworkManager: <info> Retrieved the following IP4
configuration from the DHCP daemon:
May 18 13:22:50 akp-ubu01 NetworkManager: <info> address 10.50.164.15
May 18 13:22:50 akp-ubu01 NetworkManager: <info> netmask 255.255.255.224
May 18 13:22:50 akp-ubu01 NetworkManager: <info> broadcast 10.50.164.31
May 18 13:22:50 akp-ubu01 NetworkManager: <info> gateway 10.50.164.1
May 18 13:22:50 akp-ubu01 NetworkManager: <info> nameserver 10.50.164.22
May 18 13:22:50 akp-ubu01 NetworkManager: <info> nameserver 10.50.164.5
May 18 13:22:50 akp-ubu01 NetworkManager: <info> domain name
'fampeeters.com'
May 18 13:22:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) scheduled...
May 18 13:22:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 4 of
5 (IP Configure Get) complete.
May 18 13:22:50 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) started...
May 18 13:22:51 akp-ubu01 NetworkManager: <info> Activation (eth0) successful,
device activated.
May 18 13:22:51 akp-ubu01 NetworkManager: <info> Activation (eth0) Finish
handler scheduled.
May 18 13:22:51 akp-ubu01 NetworkManager: <info> Activation (eth0) Stage 5 of
5 (IP Configure Commit) complete.
Somehow I don't like the idea of a server (which will be running mostly
unattended) having an issue that will make it unavailable for remote
intervention everytime it reboots.
(I will try adding a simple Realtek pci card to see if that has the same
issue, but I would prefer to just use the built in NIC...)
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: bcm5722 bcm57xx broadcom tg3
--
Broadcom BCM5722 (tg3) acts weird on reboot
https://bugs.launchpad.net/bugs/231667
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
