Re: [etherlab-users] Unmatched/Skipped Datagrams

2019-12-16 Thread Gavin Lambert
Another possible cause is if your cyclic loop timing is off somehow, and you're calling ecrt_master_receive too soon after ecrt_master_send so that the packet hasn't had time to make it back to the master yet. The timing code you have below looks correct, but bear in mind that the way wakeup_ti

Re: [etherlab-users] Unmatched/Skipped Datagrams

2019-12-16 Thread Gavin Lambert
There's a 4.19 version of all drivers (except r8169, because reasons), including igb, in the unofficial patchset (https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/). It can be normal to see a small number of unmatched datagrams when you're starting your app up (and it's transit

Re: [etherlab-users] Unmatched/Skipped Datagrams

2019-12-16 Thread Gary Grobe
The ec_igb doesn't seem to be available for 4.19. If nothing else works, I may try to roll back the kernel as a last resort, but according to recent mailings, it would appear that others are running 4.19 LTS w/o issue. I did just give things a try on new hardware: - Linux 4.19.82-rt30 #1 SMP P