astlinux-users

[Astlinux-users] NETDEV WATCHDOG: ethx: transmit timed out (net4801)

[anuar m. <an...@ro...>]

Hi All,
I just download and burn the image
AstLinux-0.4.4-net4801.img.gz

Then, I try to run few test. one,of them where I try
to download files (10M size) using ftp using the
configuration
below:

    ftp client ---[eth2][net4801][eth1]--- ftp server

Then I got lots of messages below and cause the
transfer very slow.
Does anyone know seen this problem before and how to
solve it?

I did not change any setting, I just use it as it is.

Thanks in advance.

pbx ~ # NETDEV WATCHDOG: eth2: transmit timed out
eth2: Transmit timed out, status 0x000000,
resetting...
eth2: DSPCFG accepted after 0 usec.
eth2: Setting full-duplex based on negotiated link
capability.
NETDEV WATCHDOG: eth2: transmit timed out
eth2: Transmit timed out, status 0x000000,
resetting...
eth2: DSPCFG accepted after 0 usec.
eth2: Setting full-duplex based on negotiated link
capability.
[deleted bunch of above messages]

----

pbx ~ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr
00:00:24:C7:80:70
          UP BROADCAST RUNNING MULTICAST  MTU:1500 
Metric:1
          RX packets:1103 errors:0 dropped:0
overruns:0 frame:0
          TX packets:111 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:105737 (103.2 KiB)  TX bytes:65490
(63.9 KiB)
          Interrupt:10 Base address:0x2000

pbx ~ # ifconfig eth1
eth1      Link encap:Ethernet  HWaddr
00:00:24:C7:80:71
          inet addr:192.168.2.1  Bcast:192.168.2.255 
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500 
Metric:1
          RX packets:5811 errors:0 dropped:0
overruns:0 frame:0
          TX packets:3833 errors:0 dropped:0
overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8737500 (8.3 MiB)  TX bytes:252799
(246.8 KiB)
          Interrupt:10 Base address:0x4000

pbx ~ # ifconfig eth2
eth2      Link encap:Ethernet  HWaddr
00:00:24:C7:80:72
          inet addr:192.168.3.1  Bcast:192.168.3.255 
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500 
Metric:1
          RX packets:3866 errors:0 dropped:0
overruns:0 frame:0
          TX packets:5770 errors:6 dropped:51
overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:256671 (250.6 KiB)  TX
bytes:8660850 (8.2 MiB)
          Interrupt:10 Base address:0x6000



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Astlinux-users] NETDEV WATCHDOG: ethx: transmit timed out (net4801)

[Darrick H. <dha...@dj...>]

anuar musa wrote:
> Hi All,
> I just download and burn the image
> AstLinux-0.4.4-net4801.img.gz
0.4.4 is an old release.  Please grab the latest 0.4.5 release from the 
sourceforge site.  Kristian is working on revising the www.astlinux.org 
website.  In its current state it's quite confusing.

If you're still experiencing problems with the 0.4.5 release, then we'll 
start troubleshooting.  No sense in playing with something that is old.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] NETDEV WATCHDOG: ethx: transmit timed out (net4801)

[anuar m. <an...@ro...>]

Hi,
I have download Astlinux-0.4.5.img.gz but it's still
have the same problem as I mentioned before.

I did make some change to configuration by enabling
packet forwarding to enable routing in net4801 besides
assigning IP address to eth1 and eth2. e.g.
pbx ~ # ifconfig eth1 192.168.3.1 netmask
255.255.255.0
pbx ~ # ifconfig eth2 192.168.2.1 netmask
255.255.255.0
pbx ~ # echo 1 >
/proc/sys/net/ipv4/conf/all/forwarding

Some more detail info:

Routing table:
pbx ~ # netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags 
 MSS Window  irtt Iface
192.168.3.0     0.0.0.0         255.255.255.0   U     
   0 0          0 eth1
192.168.2.0     0.0.0.0         255.255.255.0   U     
   0 0          0 eth2

pbx ~ # cat /proc/interrupts
           CPU0
  0:     793413          XT-PIC  timer
  2:          0          XT-PIC  cascade
  4:       1022          XT-PIC  serial
  5:          0          XT-PIC  ohci_hcd:usb1
  8:     796142          XT-PIC  rtc
 10:       2371          XT-PIC  eth0, eth1, eth2
 14:      23244          XT-PIC  ide0
NMI:          0
ERR:          1

Attached is the dmesg file.

Regards,
Anuar

--- Darrick Hartman <dha...@dj...> wrote:

> anuar musa wrote:
> > Hi All,
> > I just download and burn the image
> > AstLinux-0.4.4-net4801.img.gz
> 0.4.4 is an old release.  Please grab the latest
> 0.4.5 release from the 
> sourceforge site.  Kristian is working on revising
> the www.astlinux.org 
> website.  In its current state it's quite confusing.
> 
> If you're still experiencing problems with the 0.4.5
> release, then we'll 
> start troubleshooting.  No sense in playing with
> something that is old.
> 
> Darrick
> 
> -- 
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
> 
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2
> express and take
> control of your XML. No limits. Just data. Click to
> get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously
> accepted via PayPal to pa...@kr....
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Astlinux-users] NETDEV WATCHDOG: ethx: transmit timed out (net4801)

[Kristian K. <kri...@gm...>]

On 5/22/07, anuar musa <an...@ro...> wrote:
> Hi,
> I have download Astlinux-0.4.5.img.gz but it's still
> have the same problem as I mentioned before.
>
> I did make some change to configuration by enabling
> packet forwarding to enable routing in net4801 besides
> assigning IP address to eth1 and eth2. e.g.
> pbx ~ # ifconfig eth1 192.168.3.1 netmask
> 255.255.255.0
> pbx ~ # ifconfig eth2 192.168.2.1 netmask
> 255.255.255.0
> pbx ~ # echo 1 >
> /proc/sys/net/ipv4/conf/all/forwarding
>
> Some more detail info:
>
> Routing table:
> pbx ~ # netstat -nr
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags
>  MSS Window  irtt Iface
> 192.168.3.0     0.0.0.0         255.255.255.0   U
>    0 0          0 eth1
> 192.168.2.0     0.0.0.0         255.255.255.0   U
>    0 0          0 eth2
>
> pbx ~ # cat /proc/interrupts
>            CPU0
>   0:     793413          XT-PIC  timer
>   2:          0          XT-PIC  cascade
>   4:       1022          XT-PIC  serial
>   5:          0          XT-PIC  ohci_hcd:usb1
>   8:     796142          XT-PIC  rtc
>  10:       2371          XT-PIC  eth0, eth1, eth2
>  14:      23244          XT-PIC  ide0
> NMI:          0
> ERR:          1
>
> Attached is the dmesg file.
>
> Regards,
> Anuar
>

Anuar,

  The last time I saw something like this on a Soekris it was because
of the NS DP83815 short cable issues.  Evidently the DP83815 had some
problems figuring out the proper attenuation on various cable lengths.
 It caused all sorts of problems.

  I could swear that I also saw it with some DP83816s a couple of
years ago.  Driver updates have been able to work around the issue
(for the most part) and I have not heard of this in years.

  Unfortunately, the natsemi driver does not distinguish between the
83815 and the 83816 (which fixed the issue - supposedly).  Can you
open your case and read the DP8381x part number off of your ethernet
chips?

  Also, try this:

1)  Use longer or shorter ethernet cables (trial and error) on both
ethernet interfaces (although eth1 seems to be the culprit).

2)  Is your switch managed?  See if there are an excessive number of
link state changes and/or input errors on the connected ethernet port.
 Also check and make sure that it is negotiating the same speed
(100/full).

3)  Have you tried a different switch?  Try inserting another switch
in between the systems or use a different switch completely.

  Of course it could always be something simple (like a bad cable),
but step #1 should cross that off the list too.

-- 
Kristian Kielhofner

Re: [Astlinux-users] NETDEV WATCHDOG: ethx: transmit timed out (net4801)

[anuar m. <an...@ro...>]

--- Kristian Kielhofner
<kri...@gm...> wrote:

Thanks Kristian,
See comments below.

> 
> Anuar,
> 
>   The last time I saw something like this on a
> Soekris it was because
> of the NS DP83815 short cable issues.  Evidently the
> DP83815 had some
> problems figuring out the proper attenuation on
> various cable lengths.
>  It caused all sorts of problems.
> 
>   I could swear that I also saw it with some
> DP83816s a couple of
> years ago.  Driver updates have been able to work
> around the issue
> (for the most part) and I have not heard of this in
> years.
> 
>   Unfortunately, the natsemi driver does not
> distinguish between the
> 83815 and the 83816 (which fixed the issue -
> supposedly).  Can you
> open your case and read the DP8381x part number off
> of your ethernet
> chips?

Part number: DP83816AVNG

> 
>   Also, try this:
> 
> 1)  Use longer or shorter ethernet cables (trial and
> error) on both
> ethernet interfaces (although eth1 seems to be the
> culprit).
> 
I have try numbers of cables from 0.5 meter to 3
meters   but the problem is still there. I am pretty
sure the cables are ok.

> 2)  Is your switch managed?  See if there are an
> excessive number of
> link state changes and/or input errors on the
> connected ethernet port.
>  Also check and make sure that it is negotiating the
> same speed
> (100/full).
> 
I am not using any switch in between the PC1 <-->
Net4801 <--> PC2; all are directly connected.

> 3)  Have you tried a different switch?  Try
> inserting another switch
> in between the systems or use a different switch
> completely.
> 
I cannot test this configuration since I don't have a
switch. I will try to find somebody to borrow from.

>   Of course it could always be something simple
> (like a bad cable),
> but step #1 should cross that off the list too.
> 
> -- 

I found some interesting, since I using vsftp as a
server and by default local authenticated user get
unlimited transfer rate.

By setting "local_max_rate=1000000" bytes/second in
/etc/vsftpd/vsftpd.conf for example to limit the
transfer rate. Restart vsftpd and re-run the ftp test
again, the no issue. I got about 5464 Kbytes/sec which
is quite good. 

If I set to unlimited transfer rate (local_max_rate=0)
and restart vsftpd and re-run the test I got time out
again. I seem that the driver has some problem
handling high traffic rate. 

Anyway, I try to switch different ports for example
using eth0 and eth2, eth0 and eth1, etc but using
unlimitted transfer rate the problem persist.

Any pointers appreciated becuase in real world one
cannot control other people ftp server or other server
for that matters.

Thanks,
Anuar

> Kristian Kielhofner
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2
> express and take
> control of your XML. No limits. Just data. Click to
> get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously
> accepted via PayPal to pa...@kr....
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com