Re: 6.19.0-rc6 CAN regression

[Oliver Hartkopp <socketcan@hartkopp.net>]

If you can't apply the fix or you want to stay on the 6.19-rc6 upstream 
kernel, it is also possible to make a workaround with the "ip" tool you 
use for the bitrate configuration.

The issued does not show up, when the ctrlmode is changed(!), e.g. when 
you enable triple-sampling, one-shot or cc-len8-dlc mode:

Instead of

# ip link set can0 type can bitrate 500000

try

# ip link set can0 type can bitrate 500000 cc-len8-dlc on

But the fix will be in the mainline repo soon.

Best regards,
Oliver


On 19.01.26 08:52, Oliver Hartkopp wrote:
> Hello Francesco,
> 
> On 19.01.26 08:17, Francesco Dolcini wrote:
>> Hello,
>> there is some issue with CAN on the latest linux 6.19 RC,
>> canfdtest fails with `send failed: Invalid argument` fails on various
>> SoC (NXP i.MX8MP, i.MX8QM, i.MX6 ... and TI AM62 and maybe more).
>>
>> Is this known and already being addressed? I have seen some recent PR
>> and patches, but I am not sure they are fixing this issue.
> 
> Yes, this is already fixed here:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git/log/? 
> h=testing
> 
> in this patch:
> "can: dev: alloc_candev_mqs(): add missing default CAN capabilities"
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git/ 
> commit/?h=testing&id=375629c92fd842bc2a229bb34c4453f62e097169
> 
> The PR is waiting for upstream:
> https://lore.kernel.org/linux-can/20260116200323.366877-1- 
> mkl@pengutronix.de/
> 
> When you apply the above patch, it should just work again.
> 
> Best regards,
> Oliver