PEAK-System Forum

We've been running the same test on Linux 4.17 over the weekend and couldn't reproduce the error. It really seems to be fixed. I'd be interesting to see how the fix looks like but we're working around the issue by sorting frames at the receiver for now.

thanks for your support!

Thanks, that's interesting. Have you tried to reproduce it on Linux 4.9?

Hi,

FYI we run a test for 2 days now with a modified candump that must stop when it reads a timestamp older than the previous one... While we aren't able to reproduce this issue, could you please check whether it exists any BIOS upgrade for your PC? This issue might also come from your USB chipset ...

FWIW, another example I can trigger pretty quickly, after about half an hour at 125000 kbit/s. I now have a larger random (known) response and send it from an STM32 using only one of the driver's "mailboxes", really ensuring that I put frames on the bus _sequentially_.

Again, I paste the last good ...

Hi,

The question is: does the last frame really arrives before the previous one or is last timestamp wrong?
Can you check the sequence of the frames with the content of the data byte?

— Stéphane

Hi Stéphane,

Yes I can. I know the timestamps aren't wrong. I can also send the (known) frames from ...

Hi,

I seem to have almost the exact same problem. I need frames to work FIFO but
(after running a simple tx/response at 115000 kbit/s for some time) I see an
out-of-order error, see below. Please note that "hours" may not be enough for
it to trigger but we can repeatedly trigger it. run at least ...