Ubuntu
linux package

  1. Bug #1937897
  2. Comment #18

Comment 18 for bug 1937897

Revision history for this message
Ole Jon Bjørkum (olejonbj) wrote (last edit ):

To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal / 20.04 HWE LTS)

Well Ubuntu Kernel Bot, that's exactly what I did in comment #14 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14

Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio errors and warnings in dmesg and "journalctl -b" as with the current 5.11 HWE kernel.

X570 Motherboard
Ryzen 9 3950X Zen2 CPU

Same error appears twice during boot. Here's the output from "journalctl -b"

---
sep. 12 15:37:43 tux kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines
sep. 12 15:37:43 tux kernel: gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
sep. 12 15:37:43 tux kernel: gpio-aaeon: probe of gpio-aaeon.0 failed with error -22
sep. 12 15:37:44 tux kernel: gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines
sep. 12 15:37:44 tux kernel: gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
sep. 12 15:37:44 tux kernel: gpio-aaeon: probe of gpio-aaeon.0 failed with error -22
---

They're both "gpiochip1 - GPIOs 0..-1", so why try again right after the first fails?

Does NOT appear on my Intel NUC Core i3. It's a 2013 model but runs the exact same kernel at least. Likely not on any Intel based motherboards.