It will work fine for ET1100 or ET1100 based ESC slaves. For several FPGA based 
ESC like the one in your SanyoDenki, Maxon Maxpos... you may get trouble. The 
point is, tx burst dma buffer for r8169 driver is too small (for these slaves), 
looking at the r8169...ethercat.c you  can see this line
#define TX_DMA_BURST    7       /* Maximum PCI burst, '7' is unlimited */
The explanation '/* Maximum PCI burst, '7' is unlimited */'  is not true, in 
fact this number causes Tx ring full issue. Increase this number to about 9 (or 
10) your problem will be absplutely gone.
Hope this help.
--
Ho Tam,
www.neuromeka.com
www.TheEtherCat.com




Sent from the Works Mail app.

-----Original Message-----
From: <[email protected]>
To: <[email protected]>
Sent: 2017.01.11 오후 08:00:01
Subject: etherlab-users Digest, Vol 115, Issue 4



Send etherlab-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.etherlab.org/mailman/listinfo/etherlab-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of etherlab-users digest..."


Today's Topics:

   1. BUG! Tx Ring full when queue awake! using ec_r8169
      (Raimarius Delgado)


----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Jan 2017 12:56:48 +0900
From: Raimarius Delgado <[email protected]>
To: [email protected]
Subject: [etherlab-users] BUG! Tx Ring full when queue awake! using
        ec_r8169
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi everyone,
I am experiencing problems regarding realtek r8169. My system is flooded 
with:
[   98.153777] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.164732] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.175721] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.185671] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.196641] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.207627] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.218587] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.229550] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.240504] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.251454] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.262402] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.273349] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!
[   98.284296] ec_r8169 0000:01:00.0 (unregistered net_device): BUG! Tx 
Ring full when queue awake!

I am running IgH EtherCAT 1.5.2 on top of Linux 3.14.15 using the 
real-time co-kernel Xenomai 2.6.5. The error occurs when the ec_r8169 is 
loaded and the master is connected with different products that I have 
tested:
Sanyo Sansmotion R
Maxon EPOS3

However, the error does not occur for the following servo drives though:
LS Mecapion L7
Panasonic


Does anyone have an idea what seem to be the problem?

Raimarius Delgado



------------------------------

Subject: Digest Footer

_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users


------------------------------

End of etherlab-users Digest, Vol 115, Issue 4
**********************************************

_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users

Reply via email to