Broadcom BCM5722 (tg3) acts weird on reboot

[Francesco Peeters]

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...)

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Francesco Peeters (francesco-fampeeters)]

IanW wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
>
>
It is a production-server... I cannot just install new releases, etc.

I will let you know once I do!

[Vide (vide80)]

Hi, I'm running Ubuntu Intrepid with kernel 2.6.27-11 and a Broadcom tg3 ethernet controller

02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787 Gigabit Ethernet PCI Express (rev 02)

and I have a similiar problem, but only with DHCP. I have to issue 2 consecutives DHCP requests before I get the IP, then all work correctly.
The problem happens both with networkmanager or classic /etc/network/interfaces configuration

[Vide (vide80)]

For the record, it's a Dell Optiplex 330 (a workstation)

[Josir (josir-jsk)]

Hi, folks.
IBM System x3200 M2
Intrepid 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64

I have the same problem with Broadcom BCM 5722 Gigabit Ethernet.
When I installed, it works fine. After a poweroff/on network is not working but I got no error message.

03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express
 Subsystem: IBM Device 0378
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 2298
 Region 0: Memory at e8200000 (64-bit, non-prefetchable) [disabled] [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: 00000000fee0f00c Data: 41a1
 Capabilities: [d0] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
   ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <4us, L1 <64us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [13c] Virtual Channel <?>
 Capabilities: [160] Device Serial Number bc-42-1f-fe-ff-64-1a-00
 Capabilities: [16c] Power Budgeting <?>
 Kernel driver in use: tg3
 Kernel modules: tg3

If you need any log or detail, I will be glad to help.
I can also do whatever patch/update if you need to debug this.
Josir

[Josir (josir-jsk)]

After 2 or 3 reboots, the network is working again. It seem that the error is randomic.
This is a running network lspci -vvv log:

03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express
 Subsystem: IBM Device 0378
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 2298
 Region 0: Memory at e8200000 (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: 00000000fee0f00c Data: 4189
 Capabilities: [d0] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
   ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 4096 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 <4us, L1 <64us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Capabilities: [13c] Virtual Channel <?>
 Capabilities: [160] Device Serial Number bc-42-1f-fe-ff-64-1a-00
 Capabilities: [16c] Power Budgeting <?>
 Kernel driver in use: tg3
 Kernel modules: tg3

Running a diff between two configs (first was the problematic one)

1st: Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
2nd:Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+

1st: Region 0: Memory at e8200000 (64-bit, non-prefetchable) [disabled] [size=64K]
2nd: Region 0: Memory at e8200000 (64-bit, non-prefetchable) [size=64K]

1st: Capabilities: [e8] ... Address: 00000000fee0f00c Data: 41a1
2nd: Capabilities: [e8] ... Address: 00000000fee0f00c Data: 4189

I'm not sure if this is really a Ubuntu bug or a Hardware problem.
Any tips?

[Onni (onno-nona-it)]

Hi, im running Ubuntu-9.04-desktop-i386 on a Dell OptiPlex GX620.

When i was installing the Broadcom - NetXtreme BCM5751 Gigabit Ethernet PCI Express was working fine but after the reboot the nic says no link detected.

Warm boot or cold boot make no difference, only some times (lets say one in the ten times, in 8.10 it was one on ten that fails, but always it was working after a warm boot) the nic is working.

When the nic fails it will always work after unloading the nic's driver module with the command "sudo rmmod tg3" and loading the nic's driver module again with the command "insmod /lib/modules/2.6.28-11-generic/kernel/drivers/net/tg3.ko" the nic starts working fine.

So it looks to me if there is a timing problem at startup when booting the machine.

Any tips ?, it's a strange problem.

[kernel-janitor (kernel-janitor)]

Hi francesco-fampeeters,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 231667

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Ryan Nowakowski (tubaman)]

Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=2bbf382e-4d23-4b11-9e9d-b763fce790e0
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 288157U
Package: linux-image-2.6.28-13-generic 2.6.28-13.45
PackageArchitecture: i386
ProcCmdLine: root=UUID=eead36f6-b02d-41d5-a95b-a410a9914aa4 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-13.45-generic
Uname: Linux 2.6.28-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Ryan Nowakowski (tubaman)]

I'm having the same issue as Vide above (comment #3)

[Ryan Nowakowski (tubaman)]

Scratch that... my issue on my BCM4901(using the tg3 driver) was that my Cisco switch was not set to fastboot(host mode) for that particular port so there was a 60 second delay after link before packets would flow. After setting my switch port to host mode, tg3 works fine! I suppose I only had problems with the tg3 driver and no others because tg3 obeys spanning port stuff perhaps?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]