Hi Salvatore,
Thank you for testing. And before 5.10.113 can you pin point to a version in which showed sensible versions? If so you have a starting point to bisect where the problem is introduced which would be very helpfull to determine the pontential issue.
A friend of mine did these tests and here are the results: 4.19.260 HAS NOT the bug 4.19.264 HAS NOT the bug 5.0.1 HAS the bug 5.1 HAS the bug So it looks like the bug appeared in kernel 5. Kind regards, Alexis Domjan
