In fact, restarting the ethercat service doesn't work because kernel objects ec_e1000e and ec_master are still in use. I kill them with « rmmod -f » and restart the ethercat service and it works.
In my project hardware architecture is not defined. Could you advise me a network card model in PCIe which is compatible with etherlab ? Regards Vincent BUSSIERES Responsable Technique Logiciel [1572337113342] ZE Ma Campagne 36, Impasse Félix Nadar 16000 ANGOULEME Tel: 33 (0)9.72.40.35.08 www.hemeria-group.com<https://webmail.nexeya.fr/owa/redir.aspx?C=GK_BqKCZef7LtPZnqnd_LGYr1NG9sz4Smy3iKIwO-pXqtJC7VgzXCA..&URL=http%3a%2f%2fwww.hemeria-group.com%2f> P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Ce message et les fichiers pouvant être attachés sont confidentiels, réservés à l'usage unique des destinataires et n'engagent HEMERIA sous aucune forme que ce soit. This email and any files transmitted with it are confidential, intented solely for the unique use of the recipients and don't commit HEMERIA. De : Gavin Lambert <gavin.lamb...@tomra.com> Envoyé : vendredi 17 avril 2020 01:40 À : BUSSIERES Vincent <vincent.bussie...@hemeria-group.com>; etherlab-users@etherlab.org Objet : RE: Problem at unplug and reconnection of network cable with Etherlab master patchset 20190904 The udev rule is intended for motherboards with onboard e1000e only, due to an adverse interaction between the MEI power-saving and E1000E. I don't think it will help with add-in cards - but then, in my testing none of the add-in cards that I had were affected by the issue either, since they shouldn't be interacting with the MEI. As noted in the docs, restarting the ethercat service (thereby reloading the driver) should also recover from the fault, though obviously that's not an acceptable workaround in practice. The good news is that (if it's the same issue) if you switch to the generic driver then the problem should go away. The bad news is that this may limit your real-time performance. Another option is to drop back to Debian 8, or at least a pre-4.4 Linux kernel. Gavin Lambert Senior Software Developer [cid:image002.png@01D614A7.F36E89D0] [TOMRA]<http://www.compacsort.com>[Facebook]<https://www.facebook.com/Compacsort>[Linkedin]<https://www.linkedin.com/company/compac-sorting-equipment/>[Youtube]<https://vimeo.com/compacsort>[twitter]<https://twitter.com/compacsort>[instagram]<https://www.instagram.com/compacsort/> COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand Switchboard: +64 96 34 00 88 | tomra.com<http://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. From: BUSSIERES Vincent Sent: Friday, 17 April 2020 11:23 To: etherlab-users@etherlab.org<mailto:etherlab-users@etherlab.org> Subject: [etherlab-users] Problem at unplug and reconnection of network cable with Etherlab master patchset 20190904 Dear Etherlab users, I am developing a software using Etherlab master patchset 20190904 for recent kernels. My environment is Linux Debian 9.5 with 4.9.0-8-amd64 kernel. I am using a add-in network card, Kernel driver in use is ec_e100e. I connect only one slave to the master. I noticed strange behaviours when I unplug and reconnect network cable. First times everythings is OK, I can see state link jump from up to down and down to up, communication resumes. But sometimes my software doesn't respond neither ethercat tools. Communication is break down, command etherlab master doesn't work too. I must reboot computer to make it works again. As advised in the patch documentation, I add a rule with the following content : ACTION=="add",KERNEL=="mei0",ATTR{../../power/control}="on" but that didn't solve the problem. I didn't notice something wrong in dmesg log below. [ 171.720209] EtherCAT DEBUG: 0C D1 00 00 00 00 1D 00 00 00 00 00 00 00 00 00 [ 171.720214] EtherCAT DEBUG: 00 00 00 00 00 00 0F 00 00 00 00 00 00 00 00 00 [ 171.720218] EtherCAT DEBUG: 00 08 00 38 C0 37 06 00 00 00 00 00 [ 171.721186] EtherCAT DEBUG 0: Datagram ffff8cb3d35a93d8 already queued (skipping). [ 171.721187] EtherCAT DEBUG 0: ec_master_send_datagrams(device_index = 0) [ 171.721187] EtherCAT DEBUG 0: Adding datagram 0xD2 [ 171.721188] EtherCAT DEBUG 0: frame size: 46 [ 171.721188] EtherCAT DEBUG 0: Sending frame: [ 171.721188] EtherCAT DEBUG: FF FF FF FF FF FF 68 05 CA 8B CE EB 88 A4 29 10 [ 171.721192] EtherCAT DEBUG: 0C D2 00 00 00 00 1D 00 00 00 00 00 00 00 00 00 [ 171.721196] EtherCAT DEBUG: 00 00 00 00 00 00 0F 00 00 00 00 00 00 00 00 00 [ 171.721200] EtherCAT DEBUG: 00 08 00 38 C0 37 06 00 00 00 00 00 [ 171.722184] EtherCAT DEBUG 0: Datagram ffff8cb3d35a93d8 already queued (skipping). [ 171.722185] EtherCAT DEBUG 0: ec_master_send_datagrams(device_index = 0) [ 171.722185] EtherCAT DEBUG 0: Adding datagram 0xD3 [ 171.722186] EtherCAT DEBUG 0: frame size: 46 [ 171.722186] EtherCAT DEBUG 0: Sending frame: [ 171.722186] EtherCAT DEBUG: FF FF FF FF FF FF 68 05 CA 8B CE EB 88 A4 29 10 [ 171.722190] EtherCAT DEBUG: 0C D3 00 00 00 00 1D 00 00 00 00 00 00 00 00 00 [ 171.722194] EtherCAT DEBUG: 00 00 00 00 00 00 0F 00 00 00 00 00 00 00 00 00 [ 171.722198] EtherCAT DEBUG: 00 08 00 38 C0 37 06 00 00 00 00 00 [ 171.723188] EtherCAT DEBUG 0: Datagram ffff8cb3d35a93d8 already queued (skipping). [ 171.723189] EtherCAT DEBUG 0: ec_master_send_datagrams(device_index = 0) [ 171.723189] EtherCAT DEBUG 0: Adding datagram 0xD4 [ 171.723190] EtherCAT DEBUG 0: frame size: 46 [ 171.723190] EtherCAT DEBUG 0: Sending frame: [ 171.723190] EtherCAT DEBUG: FF FF FF FF FF FF 68 05 CA 8B CE EB 88 A4 29 10 [ 171.723194] EtherCAT DEBUG: 0C D4 00 00 00 00 1D 00 00 00 00 00 00 00 00 00 [ 171.723198] EtherCAT DEBUG: 00 00 00 00 00 00 0F 00 00 00 00 00 00 00 00 00 [ 171.723202] EtherCAT DEBUG: 00 08 00 38 C0 37 06 00 00 00 00 00 [ 171.723898] EtherCAT 0: 0 slave(s) responding on main device. [ 171.723899] EtherCAT 0: Stopping EoE thread. Does anybody has got an idea ? Thanks a lot. Best regards Vincent BUSSIERES Responsable Technique Logiciel [1572337113342] ZE Ma Campagne 36, Impasse Félix Nadar 16000 ANGOULEME Tel: 33 (0)9.72.40.35.08 www.hemeria-group.com<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebmail.nexeya.fr%2Fowa%2Fredir.aspx%3FC%3DGK_BqKCZef7LtPZnqnd_LGYr1NG9sz4Smy3iKIwO-pXqtJC7VgzXCA..%26URL%3Dhttp%253a%252f%252fwww.hemeria-group.com%252f&data=02%7C01%7Cgavin.lambert%40tomra.com%7C2c447d40584940fbfee408d7e25d18e4%7C4308d118edd143008a37cfeba8ad5898%7C0%7C1%7C637226761787161172&sdata=KmXKbTM9rW6HzFe%2FZA8lPLxvTb%2BtdgxKVXY1rYlJSEY%3D&reserved=0> P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité. Ce message et les fichiers pouvant être attachés sont confidentiels, réservés à l'usage unique des destinataires et n'engagent HEMERIA sous aucune forme que ce soit. This email and any files transmitted with it are confidential, intented solely for the unique use of the recipients and don't commit HEMERIA.
_______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
