Well OK there is a module with that name, however I did blacklist it and same error still occurs. It happens very early in the boot process. Now maybe it tries to load gpio-aaeon, but still early to load modules I would say, it's still doing say GRUB kernel parameters like fsck ones.
Now I have confirmed it does slow down boot pretty badly, however the HWE stack just got kernel 5.11 and although it has the same error it does seem to *almost* boot as fast as without any error. Now I tried to actually load that module, so the reverse. It simply says that no such device exists. Conclusion/TLDR: So it shouldn't try to load it in the first place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
