Netdev Watchdog Transmit Queue 0 Timed Out
TSR=0x3, ISR=0x3, t=88. [11920.966603] NETDEV WATCHDOG: eth1: transmit timed out [11920.966613] eth1: Tx timed out, lost interrupt? Affecting: linux (Ubuntu) Filed here by: Kent Baxley When: 2014-06-18 Confirmed: 2014-06-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. P67A-UD4-B3/P67A-UD4-B3, BIOS F8 03/21/2012 [357265.116120] ffffffff817c6e95 ffff880217403da8 ffffffff8149f7cc 0000000000000001 [357265.116124] ffff880217403df8 ffff880217403de8 ffffffff81047410 ffffffff81272be0 [357265.116128] 0000000000000000 ffff8800e2232000 0000000000000001 0000000000000000 [357265.116132] Call Trace: [357265.116135]
I'm using the e100 and velocity interfaces, with the Rhine now disconnected. copy_user_generic_string+0x2d/0x40 Aug 28 14:16:27 bond-111 kernel: [ 519.336647] [
Netdev Watchdog Transmit Queue 0 Timed Out
It seems unrelated to the version of kernel running, xen-version running, amount of VM's running, firmwares and revisions running, etc... Kent Baxley (kentb) wrote on 2014-06-20: #18 Understood. TSR=0x3, ISR=0x3, t=315. [11938.549894] NETDEV WATCHDOG: eth1: transmit timed out [11938.549904] eth1: Tx timed out, lost interrupt? Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains.
As of right now, the stable kernel that I can run and not have this problem is 220.127.116.11. http://bugzilla.kernel.org/show_bug.cgi?id=6138 http://lkml.org/lkml/2004/5/24/4 http://lkml.org/lkml/2004/11/1/9 I am not quite good to trace above threads. Anyhow, every time I connect via ssh I get random "Connection reset by peer" errors. Eth0 Transmit Timed Out Resetting dmi.bios.version: 2.1.2 dmi.board.name: 0JD6X3 dmi.board.vendor: Dell Inc.
TSR=0x3, ISR=0x3, t=264. [11948.340596] NETDEV WATCHDOG: eth1: transmit timed out [11948.340606] eth1: Tx timed out, lost interrupt? I restarted in windows and the switch port where the card was connected started flashing. Join our community today! https://access.redhat.com/solutions/303453 enqueue_entity+0x122/0x2b0 May 13 05:14:18 pinky kernel: [23718.804218] [
I found several posts which say that apic is related. -> with kernel option "noapic", situation got worse. Vmxnet3 Tx Hang After bootup it randomly gets the following errors after a few hours or a few days and the network looses connection. Comment 12 Jan Joris Vereijken 2009-05-18 04:55:52 UTC I have the same issue on an Intel D945GCLF2 MB with embedded NIC. Christopher M.
Netdev Watchdog Eth0 Transmit Timed Out Redhat
same for eth1 Same behaviour, it crashes within the same time-interval. http://superuser.com/questions/776079/what-is-the-reason-for-an-error-eth0-transmit-timeout-in-dmesg The error sometimes didn't occur for 24 hours, sometimes in 30 minutes, and under varying traffic loads, day or night. Netdev Watchdog Transmit Queue 0 Timed Out Thanks, - Jan Joris - From dmesg: [ 3.399902] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 3.399944] r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ Netdev Watchdog Transmit Timed Out Vmware I have then updated the tg3 driver to version 3.137h, but the issue was still reproducible.
Also, i'm enabled debug in driver and build kernel with full debug. have a peek at these guys Also, I can't see what firmware version you have on the NIC. linux networking dmesg share|improve this question asked Jul 2 '14 at 14:39 Alex 1141825 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote I have not Comment 13 rm+bko 2009-09-24 13:24:53 UTC I also have this issue with the latest 2.6.31 kernel, Realtek 8111B (on-board at Gigabyte GA-MA790FX) and MTU 4000. Netdev Watchdog Eth0 (e1000) Transmit Queue 0 Timed Out
cpuidle_enter_state+0x55/0xc0 [357265.116211] [
John Muir (john-muir) wrote on 2008-10-29: #29 lshw when all is ok Edit (18.9 KiB, text/plain) As of today, with all updates, this is still a problem. Linux Netdev Watchdog TSR=0x3, ISR=0x3, t=77. [11921.765843] NETDEV WATCHDOG: eth1: transmit timed out [11921.765853] eth1: Tx timed out, lost interrupt? Changed in linux-source-2.6.20: importance: Undecided → Medium status: Unconfirmed → Needs Info Sebastien Bacher (seb128) wrote on 2007-03-20: #3 with "irqpoll" the computer freeze during the GNOME login Ben Collins (ben-collins)
strlcpy+0x4a/0x60 May 13 05:14:18 pinky kernel: [23718.804203] [
physical id: 7 bus info: [email protected]:07.0 logical name: eth0 version: 10 serial: 00:a0:d1:2e:b1:ea size: 10MB/s capacity: 100MB/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd eth0: Tx descriptor 0 is 0008a03c. (queue head) eth0: Tx descriptor 1 is 0008a03c. This bug does not appear on Knoppix 5.1 KM (ubuntubug-acrasis) wrote on 2007-06-23: #9 Download full text (3.3 KiB) Similar here too. this content It is very reproducible; when I put full load on it, it occurs about once a minute.
RTL-8139/8139C/8139C+ (rev 10) lshw says Code: *-network:1 description: Ethernet interface product: RTL-8139/8139C/8139C+ vendor: Realtek Semiconductor Co., Ltd. Additionally, I can tell you the iSCSI target is also a linux machine, running debian squeeze, and LIO as iSCSI target. try_to_wake_up+0xf1/0x270 [ 7251.780192] [
The chip version is a bnx2-5708 I see the transmit timed out whilst loading vmlinuz from my boot media. This computer had Windows before and ran fine. http://www.linuxquestions.org/questi...d.php?t=515819 I somewhat think this may be intrinsic to hardware.... I'd say try setting debug verbosity to max (16), and set kernel verbosity to max (dmesg -n 7).
After traffic freeze, ping says: ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available 2) on Kent Baxley (kentb) wrote on 2014-06-20: #16 Bernard, I may also want to go ahead and get a soup-to-nuts list of how to set up a machine to reproduce this. abloylas (abloylas) wrote on 2007-08-02: #13 Disabling ACPI support in the BIOS solved my problem. Comment 8 Roman Timofeev 2008-06-11 06:15:46 UTC Bug found in latest kernels(2.6.26-rcXX too).
So I have removed this useless directive from my menu.lst. Do you totally disagree, or do you think this could be the reason? Then I have tried Debian Jessie (kernel 3.16, tg3 3.137) and the issue is not reproducible. [email protected]:~# uname -a Linux hostname 3.13.0-29-generic #53~precise1-Ubuntu SMP Wed Jun 4 22:06:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [email protected]:~# dmesg | grep tg3 [ 65.567717] tg3.c:v3.134 (Sep 16, 2013) [ 65.580967]
Status: RESOLVED OBSOLETE Product: Drivers Classification: Unclassified Component: Network Hardware: All Linux Importance: P1 normal Assigned To: Francois Romieu URL: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: It must be something with the driver not able to establish initial communication on the network interface after some strange event happens like power outage or irregular system power off which