Bug 11107 - tg3: NC150T stops working after some time
Summary: tg3: NC150T stops working after some time
Status: CLOSED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-17 01:49 UTC by C. Fischer
Modified: 2012-05-22 12:54 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.22
Tree: Mainline
Regression: No


Attachments

Description C. Fischer 2008-07-17 01:49:33 UTC
Latest working kernel version: ?
Earliest failing kernel version: 2.6.22
Distribution: Ubuntu
Hardware Environment: NT150T (chip set: Broadcom Corporation NetXtreme BCM5705_2 Gigabit Ethernet (rev 03))
Software Environment:
Problem Description:

After some time (30 seconds to some hours) the NIC stops working. If there is high traffic load then this happens earlier. 

dmesg:
[  619.746271] NETDEV WATCHDOG: eth0: transmit timed out
[  619.746277] tg3: eth0: transmit timed out, resetting
[  619.747946] tg3: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000000]
[  619.749817] tg3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000004]
[  619.753766] PM: Writing back config space on device 0000:01:0c.0 at offset b (was 165314e4, writing 3226103c)
[  619.753782] PM: Writing back config space on device 0000:01:0c.0 at offset 3 (was 0, writing 2008)
[  619.753789] PM: Writing back config space on device 0000:01:0c.0 at offset 2 (was 2000000, writing 2000003)
[  619.753796] PM: Writing back config space on device 0000:01:0c.0 at offset 1 (was 2b00000, writing 2b00006)
[  619.753803] PM: Writing back config space on device 0000:01:0c.0 at offset 0 (was 165314e4, writing 165414e4)
[  619.769658] tg3: eth0: Link is down.
[  619.779151] PM: Writing back config space on device 0000:01:0c.0 at offset b (was 165314e4, writing 3226103c)
[  619.779167] PM: Writing back config space on device 0000:01:0c.0 at offset 3 (was 0, writing 2008)
[  619.779174] PM: Writing back config space on device 0000:01:0c.0 at offset 2 (was 2000000, writing 2000003)
[  619.779180] PM: Writing back config space on device 0000:01:0c.0 at offset 1 (was 2b00000, writing 2b00006)
[  619.779187] PM: Writing back config space on device 0000:01:0c.0 at offset 0 (was 165314e4, writing 165414e4)
[  622.594086] tg3: eth0: Link is up at 1000 Mbps, full duplex.
[  622.594090] tg3: eth0: Flow control is on for TX and on for RX.
[  917.538854] NETDEV WATCHDOG: eth0: transmit timed out
[  917.538860] tg3: eth0: transmit timed out, resetting
[  917.542855] tg3: DEBUG: MAC_TX_STATUS[00000008] MAC_RX_STATUS[00000000]
[  917.547116] tg3: DEBUG: RDMAC_STATUS[00000000] WDMAC_STATUS[00000004]
[  917.553465] PM: Writing back config space on device 0000:01:0c.0 at offset b (was 165314e4, writing 3226103c)
[  917.553481] PM: Writing back config space on device 0000:01:0c.0 at offset 3 (was 0, writing 2008)
[  917.553488] PM: Writing back config space on device 0000:01:0c.0 at offset 2 (was 2000000, writing 2000003)
[  917.553495] PM: Writing back config space on device 0000:01:0c.0 at offset 1 (was 2b00000, writing 2b00006)
[  917.553502] PM: Writing back config space on device 0000:01:0c.0 at offset 0 (was 165314e4, writing 165414e4)
[  917.569375] tg3: eth0: Link is down.


Steps to reproduce:
Comment 1 Alan 2012-05-22 12:54:24 UTC
Closing as obsolete, please reopen and update the kernel version if still seen

Note You need to log in before you can comment on or make changes to this bug.