Kluas

Thanks for clarification.

To my understanding it was introduced by kernel commit 91562895f803, which was accepted by kernel team https://lore.kernel.org/linux-ext4/87bkbbijwt.fsf@doe.com/T/ I didn't find any changelogs for the kernel on my Armbian host. I looked into these changelogs, but didn't find any data: zless /usr/share/doc/linux-dtb-current-meson64/changelog.gz zless /usr/share/doc/linux-image-current-meson64/changelog.gz --> I'm unsure, if I'm affected. FUD., On the other side, on the Debian Users ML are reports, that Debian Bookworm is affected: https://lists.debian.org/debian-user/2023/12/msg00500.html More FUD on my site. As I don't have a changelog, and people are saying that my distribution (bookworm) is affected, I can only assume that Armbian is very likely affected too. But I'm glad to here, that I'm not. Thank you.

Please move this message to correct folder, if I used the wrong one. There is a grave bug in the ext4 FS, which was introduced in kernel around 6.1.55 and is fixed in kernel 6.1.66. The bug is causing data coruption and data loss, like new packages aren't installed properly. A fix was introduced today into kernel, in version 6.1.66 Armbian Bookworm 23.11.1 (Debian) comes with 6.1.63 and, according to my knowledge, is affected. When will new kernel packages from armbian be available? References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 https://fulda.social/@Ganneff/111551628003050712

Ok found it after a while: Added usbcore.autosuspend=-1 as kernel parameter by /boot/armbianEnv.txt file. Eg.: extraargs=usbcore.autosuspend=-1 Works fine now.

Today I installed packages (apt-get upgrade): armbian-config armbian-firmware linux-buster-root-current-odroidc2 linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidc2-current and rebooted the system. Afterwards no more USB devices were found: Active USB Hub, USB Hd, USB mouse, USB memorystick Regardless if connected via USB Hub or directly. lsusb doesn't show any devices. Any hints? Thanks in advance