emanuele-f

Recently the `linux-dtb-legacy-sunxi64` package has been updated to 23.8.1, which uses kernel `5.15.127-legacy-sunxi64` and freezes started to happen again. To address the issue, I've used armbian-config to downgrade to `linux-image-legacy-sunxi64=21.02.3`, which has kernel 5.4.88, and board is running fine again now.

Using internal emmc. After another week of usage no problems to report with the legacy kernel. Yeah, if I'm the only one to report this than this must be something related to my board. I will report here if I have new info

This should be solved in https://github.com/armbian/build/pull/3697 (see https://github.com/jwrdegoede/rtl8189ES_linux/pull/71)

Sorry for the minimal info provided in this report but, due to the possible data corruption which the bug may cause, I'm not willing to reproduce this again on my board which runs in production. One week ago, I experienced data corruption happening on the nanopi. Actually it was some time (more than one month) that I saw the board acting weird: - long ssh transfers would sometime brake (via https://github.com/dooblem/bsync) - `apt update` reported invalid keys for the official armbian repository - on rare occasions, the board would freeze (not respond to ssh, requiring manual power cycle) After experiencing data corruption, I though the board was broken but decided to switch to the legacy image via `armbian-config` as a last resort. When running `armbian-config` and selecting "Other" to switch kernel, the kernel crashed. I tried again and I was successful. With the legacy image `5.4.88-sunxi64 #21.02.3` the board works great, and all the reported issues do not occur any more. So it seems like there is a bug in the "current" image (it should be version 5.15.25), possibly in a module linked to the encryption. This is all the info I can provide for this report. Hope it helps

Compilation was easy and painless, great work! Please check out https://github.com/armbian/build/pull/2277.

Thanks for your prompt reply. I can see that the kernel module option is present in other families (e.g. https://github.com/armbian/build/blob/master/config/kernel/linux-rockchip64-current.config) and I assume that adding such option does not introduce a performance impact unless it is manually activated by running the "tc filter add.." command. I can try to build the kernel and the image and provide a pull request but it will take some time as it is my first time building armbian.

Running latest armbian buster on nanopi neo plus2 (https://www.armbian.com/nanopi-neo-plus2). Trying to set up a tc filter results in a "Error: TC classifier not found". The error can be reproduced by running: tc qdisc add dev eth0 root handle 1:0 htb default 10 tc class add dev eth0 parent 1:0 classid 1:10 htb rate 200mbit ceil 200mbit burst 15k tc qdisc add dev eth0 parent 1:10 sfq perturb 10 tc filter add dev eth0 parent 1:10 protocol all handle 0x310 flow hash keys nfct-src divisor 1024 According to https://stackoverflow.com/questions/61799390/enable-tc-of-iproute2-package-on-yocto, the CONFIG_NET_CLS_U32 is missing from the kernel configuration, verified with: zcat /proc/config.gz | grep NET_CLS_U32 # CONFIG_NET_CLS_U32 is not set The CONFIG_NET_CLS_U32 option is usually present in normal linux distributions, can you add it?