[etherlab-users] INFO: task EtherCAT-EoE:4263 blocked for more than 120 seconds

[Gavin Lambert]

Try reconfiguring Etherlab with --enable-rtmutex.  This performs better in PREEMPT_RT mode anyway, and certainly will alter that particular code path.

Otherwise, be careful with your threading.  IIRC in RTAI mode you had to supply your own mutex callbacks; in user mode these should usually be removed because it will use standard Linux mutexes instead.  But you still need to be careful to use some APIs only from the RT cyclic thread and some APIs only when that thread is not running.

Unfortunately, I don’t use EoE myself, so I can't provide much further help.


Gavin Lambert
Senior Software Developer

 


COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand
Switchboard: +49 2630 96520 | https://www.tomra.com

The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication.
-----Original Message-----
From: Bilko AS, Oguz Dilmac
Sent: Tuesday, 21 May 2019 21:26
To: etherlab-users at etherlab.org
Subject: [etherlab-users] INFO: task EtherCAT-EoE:4263 blocked for more than 120 seconds

Hi,

We are moving from RTAI kernel space (2.6.32 32 bit kernel) application to PREEMPT-RT user space application. We are using Gavin's patch set on kernel 4.9.130 64bit kernel.

After around 15 hours of testing with servo drives, we see these kernel messages and our cyclic task hangs:

[62495.878833] INFO: task EtherCAT-EoE:4263 blocked for more than 120 seconds.
[62495.878848]       Tainted: G           OE   4.9.130-rt125 #2 [62495.878855] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
[62495.878861] EtherCAT-EoE    D    0  4263      2 0x00000000 [62495.878872]  ffff8a26b5b24200 ffff8a26b5b24200 ffff8a26bfc9cd40
ffff8a26b7175a00
[62495.878885]  ffff8a26b3da5a00 ffffaf52019bfd48 ffffffffba6cb64b
00ffaf52019bfd70
[62495.878923]  ffff8a26bfc9cd40 ffffaf52019bfd50 ffff8a26b3da5a00
ffff8a26b3e56080
[62495.878934] Call Trace:
[62495.878949]  [<ffffffffba6cb64b>] ? __schedule+0x24b/0x580 [62495.878956]  [<ffffffffba6cb9bd>] schedule+0x3d/0xd0 [62495.878962]  [<ffffffffba6ce85b>] schedule_timeout+0x29b/0x420 [62495.878969]  [<ffffffffba6ccf96>] __down+0x76/0xc0 [62495.878977]  [<ffffffffb9eb6d00>] ? cpu_cgroup_can_attach+0x80/0xb0 [62495.878984]  [<ffffffffb9ede2c1>] down+0x41/0x50 [62495.879014]  [<ffffffffc0696d06>] ec_master_eoe_thread+0xb6/0x210 [ec_master] [62495.879039]  [<ffffffffc0696c50>] ? ecrt_master_reset+0x40/0x40 [ec_master] [62495.879045]  [<ffffffffb9eaf1a8>] kthread+0xe8/0x100 [62495.879052]  [<ffffffffb9eaf0c0>] ? kthread_park+0x60/0x60 [62495.879057]  [<ffffffffba6d0477>] ret_from_fork+0x57/0x70

We didn't have such an error with RTAI.

What can I check?

Best regards,

Oguz.

--
Oguz Dilmac
ARGE Bolumu

Bilko AS, R&D Department
====================================
Perpa Ticaret Merkezi B Blok Kat 11 Nr. 1740
TR-34384 Okmeydani Istanbul Turkey
Tel : +90 212 220 07 40  Fax :   +90 212 210 47 01
e-mail : odilmac at bilko-automation.com
web site : https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bilko-automation.com&data=02%7C01%7Cgavin.lambert%40tomra.com%7C1ad9a4aedf5548404edf08d6ddce5636%7C4308d118edd143008a37cfeba8ad5898%7C0%7C1%7C636940275611306196&sdata=7g5uRE0%2F%2B4482iwmFHeMcKTWGmWEcp6SeuKC11VBnT4%3D&reserved=0


_______________________________________________
etherlab-users mailing list
etherlab-users at etherlab.org
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.etherlab.org%2Fmailman%2Flistinfo%2Fetherlab-users&data=02%7C01%7Cgavin.lambert%40tomra.com%7C1ad9a4aedf5548404edf08d6ddce5636%7C4308d118edd143008a37cfeba8ad5898%7C0%7C1%7C636940275611306196&sdata=ldCnKiKWk4%2BeIg7U2d0A4fyjEJOEuzlIzri1Duju5oU%3D&reserved=0