eth0: transmit timed out

eth0: transmit timed out

[LEROY Christophe]

Hello,

It seems that the kernel cannot send on ethernet.
(transmit timed out).
What can be the source of such a problem ?

Thanks

C. Leroy



loaded at:     00410000 0041A58C
relocated to:  00300000 0030A58C
zimage at:     00417000 00482CDF
avail ram:     00483000 00800000

Linux/PPC load: nfsroot=/mcrlinux ip=192.168.2.50:192.168.2.51:::::
root=/dev/nfs
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.4.16 (root@localhost.localdomain) (gcc version 2.95.3
20010315 (release)) #209 jeu déc 27 10:09:34 CET 2001
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: nfsroot=/mcrlinux ip=192.168.2.50:192.168.2.51:::::
root=/dev/nfs
Decrementer Frequency = 150000000/60
Calibrating delay loop... 39.73 BogoMIPS
Memory: 6852k available (848k kernel code, 296k data, 44k init, 0k
highmem)
Dentry-cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode-cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0380 is a SMC
ttyS02 at 0x0100 is a SCC
ttyS03 at 0x0200 is a SCC
block: 64 slots per queue, batch=16
eth0: CPM ENET Version 0.2 on SCC1, 08:00:3e:01:00:17
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 512)
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.2.50, mask=255.255.255.0,
gw=255.255.255.255,
     host=192.168.2.50, domain=, nis-domain=(none),
     bootserver=192.168.2.51, rootserver=192.168.2.51, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.2.51
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
 Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
dc00 002a 001fde42
dc00 002a 001fdec2
dc00 002a 001fdf42
dc00 002a 001f60d2
dc00 002a 001f6152
dc00 002a 001f61d2
dc00 002a 001f6252
fc00 002a 001f62d2
9000 0000 00168000
9000 0000 00168800
9000 0000 00167000
9000 0000 00167800
9000 0000 00166000
9000 0000 00166800
9000 0000 00165000
b000 0000 00165800
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
 Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
dc00 002a 001fde42
dc00 002a 001fdec2
dc00 002a 001fdf42
dc00 002a 001f60d2
dc00 002a 001f6152
dc00 002a 001f61d2
dc00 002a 001f6252
fc00 002a 001f62d2
9000 0000 00168000
9000 0000 00168800
9000 0000 00167000
9000 0000 00167800
9000 0000 00166000
9000 0000 00166800
9000 0000 00165000
b000 0000 00165800
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
 Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
dc00 002a 001fde42
dc00 002a 001fdec2
dc00 002a 001fdf42
dc00 002a 001f60d2
dc00 002a 001f6152
dc00 002a 001f61d2
dc00 002a 001f6252
fc00 002a 001f62d2
9000 0000 00168000
9000 0000 00168800
9000 0000 00167000
9000 0000 00167800
9000 0000 00166000
9000 0000 00166800
9000 0000 00165000
b000 0000 00165800
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
 Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: eth0: transmit timed out

[David Ashley]

>Hello,
>
>It seems that the kernel cannot send on ethernet.
>(transmit timed out).
>What can be the source of such a problem ?
>
>Thanks
>
>C. Leroy
>
>
>
>eth0: CPM ENET Version 0.2 on SCC1, 08:00:3e:01:00:17


I was getting similiar messages on the fcc_enet.c driver from hhl 2.4.2
after I turned on bridge support (2 ethernet ports in the box) and
didn't have anything plugged into the other adapter. The solutions then
were to
1) Ignore the errors
2) Modify the driver so it doesn't make so much noise
3) Plug something into the port.

I don't know whether this applies to your situation though. BTW I
opted for #2.

-Dave


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: eth0: transmit timed out

[LEROY Christophe]

I found the problem. It what a misconfiguration of the routing of clock signals

Thanks

C.Leroy

LEROY Christophe a écrit :

> Hello,
>
> It seems that the kernel cannot send on ethernet.
> (transmit timed out).
> What can be the source of such a problem ?
>
> Thanks
>
> C. Leroy
>
> loaded at:     00410000 0041A58C
> relocated to:  00300000 0030A58C
> zimage at:     00417000 00482CDF
> avail ram:     00483000 00800000
>
> Linux/PPC load: nfsroot=/mcrlinux ip=192.168.2.50:192.168.2.51:::::
> root=/dev/nfs
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.4.16 (root@localhost.localdomain) (gcc version 2.95.3
> 20010315 (release)) #209 jeu déc 27 10:09:34 CET 2001
> On node 0 totalpages: 2048
> zone(0): 2048 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: nfsroot=/mcrlinux ip=192.168.2.50:192.168.2.51:::::
> root=/dev/nfs
> Decrementer Frequency = 150000000/60
> Calibrating delay loop... 39.73 BogoMIPS
> Memory: 6852k available (848k kernel code, 296k data, 44k init, 0k
> highmem)
> Dentry-cache hash table entries: 1024 (order: 1, 8192 bytes)
> Inode-cache hash table entries: 512 (order: 0, 4096 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Starting kswapd
> CPM UART driver version 0.03
> ttyS00 at 0x0280 is a SMC
> ttyS01 at 0x0380 is a SMC
> ttyS02 at 0x0100 is a SCC
> ttyS03 at 0x0200 is a SCC
> block: 64 slots per queue, batch=16
> eth0: CPM ENET Version 0.2 on SCC1, 08:00:3e:01:00:17
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 512 bind 512)
> IP-Config: Guessing netmask 255.255.255.0
> IP-Config: Complete:
>       device=eth0, addr=192.168.2.50, mask=255.255.255.0,
> gw=255.255.255.255,
>      host=192.168.2.50, domain=, nis-domain=(none),
>      bootserver=192.168.2.51, rootserver=192.168.2.51, rootpath=
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Looking up port of RPC 100003/2 on 192.168.2.51
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out.
>  Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
> dc00 002a 001fde42
> dc00 002a 001fdec2
> dc00 002a 001fdf42
> dc00 002a 001f60d2
> dc00 002a 001f6152
> dc00 002a 001f61d2
> dc00 002a 001f6252
> fc00 002a 001f62d2
> 9000 0000 00168000
> 9000 0000 00168800
> 9000 0000 00167000
> 9000 0000 00167800
> 9000 0000 00166000
> 9000 0000 00166800
> 9000 0000 00165000
> b000 0000 00165800
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out.
>  Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
> dc00 002a 001fde42
> dc00 002a 001fdec2
> dc00 002a 001fdf42
> dc00 002a 001f60d2
> dc00 002a 001f6152
> dc00 002a 001f61d2
> dc00 002a 001f6252
> fc00 002a 001f62d2
> 9000 0000 00168000
> 9000 0000 00168800
> 9000 0000 00167000
> 9000 0000 00167800
> 9000 0000 00166000
> 9000 0000 00166800
> 9000 0000 00165000
> b000 0000 00165800
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out.
>  Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
> dc00 002a 001fde42
> dc00 002a 001fdec2
> dc00 002a 001fdf42
> dc00 002a 001f60d2
> dc00 002a 001f6152
> dc00 002a 001f61d2
> dc00 002a 001f6252
> fc00 002a 001f62d2
> 9000 0000 00168000
> 9000 0000 00168800
> 9000 0000 00167000
> 9000 0000 00167800
> 9000 0000 00166000
> 9000 0000 00166800
> 9000 0000 00165000
> b000 0000 00165800
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out.
>  Ring data dump: cur_tx fa202950 (full) cur_rx fa202910.
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

eth0: transmit timed out

[Arne Kepp]

Hi,

I am running KVM 61 on CentOS 5.1 x86_64 (on a Dell PowerEdge 2950 
III).  I start my virtual machine as follows:
qemu-kvm -hda /dev/kvm_sdb/geust_root -m 1024 -net tap -net 
nic,vlan=0,macaddr=00:16:3e:00:00:02 -daemonize -nographic -smp 2

The problem is that when the guest (also CentOS 5.1 x86_64) utilizes the 
network heavily (scp to a machine on the same switch, around 12 mbyte/s) 
the network on the virtual machine just drops out.

I can no longer ping the virtual machine, and any existing SSH sessions 
die. If I connect to the virtual machine using VNC everything looks okay 
(eth0 is up, routes are okay), but I still cannot connect to anything. 
All other virtual machines on the same host continue to work as if 
nothing has happened. The same problem occurred in -58 and -59.

/var/log/messages on the guest says:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: link up, 100Mbps, full-duplex, lpa 0x05E1

Any suggestions (permanent fixes or temporary workarounds, I'll take 
what you got) would be much appreciated.

Thanks for all the great work :)
-Arne

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: eth0: transmit timed out

[david ahern]

I presume you are using the default rtl8139 nic. Correct?

What does 'ethtool -S eth0' show when the network locks up? Many months ago
adding 'noapic' to the (guest) kernel boot parameters helped, but that option is
not currently helping with my RHEL4 networking issues.

A thread for this issue is at:
http://sourceforge.net/tracker/index.php?func=detail&aid=1802082&group_id=180599&atid=893831

david


Arne Kepp wrote:
> Hi,
> 
> I am running KVM 61 on CentOS 5.1 x86_64 (on a Dell PowerEdge 2950 
> III).  I start my virtual machine as follows:
> qemu-kvm -hda /dev/kvm_sdb/geust_root -m 1024 -net tap -net 
> nic,vlan=0,macaddr=00:16:3e:00:00:02 -daemonize -nographic -smp 2
> 
> The problem is that when the guest (also CentOS 5.1 x86_64) utilizes the 
> network heavily (scp to a machine on the same switch, around 12 mbyte/s) 
> the network on the virtual machine just drops out.
> 
> I can no longer ping the virtual machine, and any existing SSH sessions 
> die. If I connect to the virtual machine using VNC everything looks okay 
> (eth0 is up, routes are okay), but I still cannot connect to anything. 
> All other virtual machines on the same host continue to work as if 
> nothing has happened. The same problem occurred in -58 and -59.
> 
> /var/log/messages on the guest says:
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
> 
> Any suggestions (permanent fixes or temporary workarounds, I'll take 
> what you got) would be much appreciated.
> 
> Thanks for all the great work :)
> -Arne
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: eth0: transmit timed out

[Arne Kepp]

Thanks David,

Yes, I am using rtl8139 and it is running 2.6.18-53.1.13.el5 (Red Hat 
kernel, CentOS).

ethtool -S eth0  on the guest says, when locked up:
NIC statistics:
  early_rx: 0
  tx_buf_mapped: 0
  tx_timeouts: 4
  rx_lost_in_ring: 0

It appears that 'noapic' did the trick, which is great, thanks! I am 
somewhat worried I'll be missing out on some SMP performance? But that's 
secondary.

Please let me know if there is anything I can do to gather any more info 
to help debug the problem.

-Arne

david ahern wrote:
> I presume you are using the default rtl8139 nic. Correct?
>
> What does 'ethtool -S eth0' show when the network locks up? Many months ago
> adding 'noapic' to the (guest) kernel boot parameters helped, but that option is
> not currently helping with my RHEL4 networking issues.
>
> A thread for this issue is at:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1802082&group_id=180599&atid=893831
>
> david
>
>
> Arne Kepp wrote:
>   
>> Hi,
>>
>> I am running KVM 61 on CentOS 5.1 x86_64 (on a Dell PowerEdge 2950 
>> III).  I start my virtual machine as follows:
>> qemu-kvm -hda /dev/kvm_sdb/geust_root -m 1024 -net tap -net 
>> nic,vlan=0,macaddr=00:16:3e:00:00:02 -daemonize -nographic -smp 2
>>
>> The problem is that when the guest (also CentOS 5.1 x86_64) utilizes the 
>> network heavily (scp to a machine on the same switch, around 12 mbyte/s) 
>> the network on the virtual machine just drops out.
>>
>> I can no longer ping the virtual machine, and any existing SSH sessions 
>> die. If I connect to the virtual machine using VNC everything looks okay 
>> (eth0 is up, routes are okay), but I still cannot connect to anything. 
>> All other virtual machines on the same host continue to work as if 
>> nothing has happened. The same problem occurred in -58 and -59.
>>
>> /var/log/messages on the guest says:
>> NETDEV WATCHDOG: eth0: transmit timed out
>> eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
>>
>> Any suggestions (permanent fixes or temporary workarounds, I'll take 
>> what you got) would be much appreciated.
>>
>> Thanks for all the great work :)
>> -Arne
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> kvm-devel mailing list
>> kvm-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>
>>     
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
> !DSPAM:4038,47c22d43155652085621377!
>
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: eth0: transmit timed out

[david ahern]

Those stats suggest you are using the 8139too nic driver. You should switch to
the 8139cp driver.

david


Arne Kepp wrote:
> Thanks David,
> 
> Yes, I am using rtl8139 and it is running 2.6.18-53.1.13.el5 (Red Hat
> kernel, CentOS).
> 
> ethtool -S eth0  on the guest says, when locked up:
> NIC statistics:
>  early_rx: 0
>  tx_buf_mapped: 0
>  tx_timeouts: 4
>  rx_lost_in_ring: 0
> 
> It appears that 'noapic' did the trick, which is great, thanks! I am
> somewhat worried I'll be missing out on some SMP performance? But that's
> secondary.
> 
> Please let me know if there is anything I can do to gather any more info
> to help debug the problem.
> 
> -Arne
> 
> david ahern wrote:
>> I presume you are using the default rtl8139 nic. Correct?
>>
>> What does 'ethtool -S eth0' show when the network locks up? Many
>> months ago
>> adding 'noapic' to the (guest) kernel boot parameters helped, but that
>> option is
>> not currently helping with my RHEL4 networking issues.
>>
>> A thread for this issue is at:
>> http://sourceforge.net/tracker/index.php?func=detail&aid=1802082&group_id=180599&atid=893831
>>
>>
>> david
>>
>>
>> Arne Kepp wrote:
>>  
>>> Hi,
>>>
>>> I am running KVM 61 on CentOS 5.1 x86_64 (on a Dell PowerEdge 2950
>>> III).  I start my virtual machine as follows:
>>> qemu-kvm -hda /dev/kvm_sdb/geust_root -m 1024 -net tap -net
>>> nic,vlan=0,macaddr=00:16:3e:00:00:02 -daemonize -nographic -smp 2
>>>
>>> The problem is that when the guest (also CentOS 5.1 x86_64) utilizes
>>> the network heavily (scp to a machine on the same switch, around 12
>>> mbyte/s) the network on the virtual machine just drops out.
>>>
>>> I can no longer ping the virtual machine, and any existing SSH
>>> sessions die. If I connect to the virtual machine using VNC
>>> everything looks okay (eth0 is up, routes are okay), but I still
>>> cannot connect to anything. All other virtual machines on the same
>>> host continue to work as if nothing has happened. The same problem
>>> occurred in -58 and -59.
>>>
>>> /var/log/messages on the guest says:
>>> NETDEV WATCHDOG: eth0: transmit timed out
>>> eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
>>>
>>> Any suggestions (permanent fixes or temporary workarounds, I'll take
>>> what you got) would be much appreciated.
>>>
>>> Thanks for all the great work :)
>>> -Arne
>>>
>>> -------------------------------------------------------------------------
>>>
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> kvm-devel mailing list
>>> kvm-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>>
>>>     
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> kvm-devel mailing list
>> kvm-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>
>> !DSPAM:4038,47c22d43155652085621377!
>>
>>   
> 
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/