Netdev Watchdog Eth0 Transmit Timed Out
Spatial screwdriver Compactness of the open and closed unit intervals Electrical Propulsion Thrust Ultimate Australian Canal Bash remembers wrong path to an executable that was moved/deleted Custom ColorFunction for GeoGraphics plot I have a > Broadcom NetXtreme card which have locked up twice within 13 days. Jul 9 09:22:27 Alatheia kernel: [ 4839.722449] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Jul 9 09:22:27 Alatheia kernel: [ 4839.722497] br0: port 1(eth1) entering learning state Jul 9 09:22:35 Alatheia kernel: [ Does anyone have any experiences regarding firmware upgrades on these cards? Source
mwait_idle+0x55/0xa0 Jul 8 17:07:09 Alatheia kernel: [10054.000237] [
Netdev Watchdog Eth0 Transmit Timed Out
But I do not understand why this box was so rock solid until I upgraded from 2.6.22-hardened-r8 to 2.6.25-hardened-r8. The log > entries from both episodes are identical. > > Any hints? The driver doesn't seem to be borked with my card. Additional info, ifdown/ifup does not fix the > situation, both take pretty long > > # ifdown eth0 > tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear > MAC_TX_MODE=ffffffff
The setup I have is as follows: Remote client for VPN -> Internet -> Router with port forwarded -> Ubuntu server 10.04LTS (the one in question) -> LAN clients (Windows machines) It would be important to know if the card is connected to a hub, or a switch(ing-hub)? 1.) There can be a defective device on the subnet, which is connected to I also upgraded the kernel to 2.6.25-hardened-r11 from 2.6.25-hardened-r8. And if the tg3 driver did not change, I've simply been way to lucky to not experience that for over 13 months with the 2.6.22 kernel.
I also know that the TX and RX values >> was above 3-4GB, but don't remember which was what. >> >> Could this be an overflow bug of some kind? >> Tg3_abort_hw Timed Out Device 0000 Capabilities: [a0] Power Management version 2 Capabilities:  Virtual Channel > Capabilities:  Root Complex Link > Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.5 PCI bridge: Intel Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Why do the physical properties of an egg shell change when the egg shell is exposed to vinegar for a week?
Additional info, ifdown/ifup does not fix the situation, both take pretty long # ifdown eth0 tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff # ifup eth0 tg3 0000:03:04.0: The > switchport bounces a couple of times though. > > Steps to reproduce: > Comment 3 Michael Chan 2009-03-16 14:29:55 UTC On Sun, 2009-03-15 at 14:32 -0700, Andrew Morton wrote: sudo apt-get dist-upgrade should do the trick. The firmware I upgraded to can be found here: http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5070004&brandind=5000008 This update upgraded the network card firmware "bootcode" from 3.61 to 3.65 and the "IPMI" from 6.20 to 6.25.
Tg3_abort_hw Timed Out
diff -Nrup 1/drivers/net/tg3.c 2/drivers/net/tg3.c --- 1/drivers/net/tg3.c 2009-02-20 14:41:27.000000000 -0800 +++ 2/drivers/net/tg3.c 2009-03-19 09:51:17.000000000 -0700 @@ -7799,6 +7799,12 @@ static void tg3_timer(unsigned long __op /* This part only runs once per second. http://thedroidblog.com/timed-out/ntp-request-timed-out.html I also know that the TX and RX values was above 3-4GB, but don't remember which was what. Here's my ifconfig output for reference: bond0 Link encap:Ethernet HWaddr 00:10:18:06:ce:24 inet addr:22.214.171.124 Bcast:126.96.36.199 Mask:255.255.255.192 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:9285671 errors:0 dropped:0 overruns:0 frame:0 TX packets:1681056 errors:0 If not, please provide lspci -vvvxxx on the eth0 device after the failure.
- szboardstretcher View Public Profile View LQ Blog View Review Entries View HCL Entries Visit szboardstretcher's homepage!
- Add a comment Show form to leave a comment Name E-Mail (hidden) Website* Location* Comment Answer this On which planet do you live? (no capital letters) *optional Comments (newest first):
- Nov 28 13:09:03 linuxbox [51330.696020] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff ------------------------------------------------------------------------ atoth at atoth Nov28,2008,6:02AM Post #2 of 6 (7563 views) Permalink Re: tg3 driver - transmit
- The server is located >> 2000km away from me, and I >> usually call a guy (who is not a technician)to go in and press >> CTRL-ALT-DEL on a keyboard.
- The first time it happened, it was no > problems for about 28 days.
- Device 0000 > Capabilities: [a0] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Capabilities:  Virtual Channel > >
- The 3.0.24 and below tree had this error but as Ubuntu now has support for a 3.0.25-40 kernel the bug has been fixed.
- Showing results for Search instead for Do you mean Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking
- Item #20 talks the details of how this problem was discovered by working back from the development kernels 3.4, 3.3, and 3.2 and how it was discovered what the tg3_stop_block_error means.
- Contact Gossamer Threads Web Applications & Managed Hosting Powered by Gossamer Threads Inc.
mwait_idle+0x55/0xa0 Jul 8 12:43:24 Alatheia kernel: [ 502.000232] [
Why isn't the religion of R'hllor, The Lord of Light, dominant? LinuxQuestions.org > Forums > Linux Forums > Linux - Networking tg3_stop_block timed out User Name Remember Me? Skip to ContentSkip to FooterSolutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small
The other, eth1, is on-board.
This bug report seems to be a copy of https://access.redhat.com/site/solutions/69382, but unfortunately the solution on the RedHat site can only be seen with a valid subscription. Probably the most helpful bug report was here, on Arch https://bugs.archlinux.org/task/19369 No solution for you , but a nice list of the various bug reports across the various distros. What can I do to prevent this in the future? I upgraded to the 2.6.25-hardened-r8 kernel mid-october, and have a feeling this upgrade introduced this issue.
The new kernel driver obviously does something it didn't do before. knock on wood) have gone away. The tx_timeout code in tg3 would not be able to reset the chip if that bit was cleared. Check This Out This restart gives me minimal downtime.
© Copyright 2017 thedroidblog.com. All rights reserved.