Issue with possible data corruption runing Linux version 5.10.12-imx6 over network nfs share.. maybe

Hi Guys,

  First thanks fo rthe hard work, but as in other threads here every now and again we get an issue moving up kernel versions.

  Mostly this is a post to flag up I had issues, so might you and that reverting the kernel fixed it for me.

  I did an apt-get update; apt dist-upgrade (I run this every other day normaly) and it did a kernal update

from

   Linux cubox 5.9.14-imx6 #20.11.3 SMP Fri Dec 11 20:57:51 CET 2020 armv7l GNU/Linux

to

   Linux version 5.10.12-imx6

It appears to all work.... however I use my Cubox-i to be a server for Kodi.

When I play flac files (which are quite big) it down loads them and uncompresses them and plays them ( kodi 2.2.6 on a rpi3B)

But I get what sounds like scrathes and static in the play back on 5.10.12 but not on 5.9.14.

Now the file system on the server is Btrfs, and kodi uses NFS to mount the files is plays.

I did run a memory test on the rpi runing kodi all good, I did a btrfs scrub (verifies the data on disk) and even an md5sun between my master file copy and one on server all OK.

Nothing in syslog, or kernel log nor anywhere else I looked :-(

Hence I revert back to the previous kernel 5.9.14 and Kodi plays my flac files all good again !!!

I do notice quite a few fixes landing still for 5.10, so we might get a working version in a while, but I can only test by trying it out as no errors reported on Kodi nor cubox-i server.

-----

So my question I did search for a nightly option, I can see one in armbian-config, but how do I find out what version of the kernel it would install before I do so?

Otherwise I'll just stick on 5.9.14 until 5.11 comes out (I see some ethernet driver fixes applied for cubox as in the other thread here, maybe they are related... but things not as 5.9.14 runs for me)

-----

Again I would like to thank all at Armbian for the Cubox-i builds I have been using them for many years and they are GREAT, but as Igor has stated before every now and again the upstream kernel  breaks something. I just want to sahre my experience in case someone else is strugling with an issue and is thing is them, as no one has said they see an issue.. I did :-)

JB