Confirmed! Finally. With the latest HWE:
$ apt show linux-image-5.11.0-37-generic
Package: linux-image-5.11.0-37-generic
Version: 5.11.0-37.41~20.04.2
...
No errors or warnings in dmesg or journalctl -b seen on my statem
anymore.
Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021)
CPU: Ryzen
This bug was fixed in the package linux - 5.11.0-37.41
---
linux (5.11.0-37.41) hirsute; urgency=medium
* hirsute/linux: 5.11.0-37.41 -proposed tracker (LP: #1944180)
* CVE-2021-41073
- io_uring: ensure symmetry in handling iter types in loop_rw_iter()
* Packaging resync
Hi,
Focal HWE kernel 5.11.0-36.40~20.04.1 does *not* contain the fix for
this bug. The kernel version currently in focal-proposed
(5.11.0-35.37~20.04.1) contains the fix but it is getting re-spun and
will be updated to a new version in a couple of hours. Please test
version 5.11.0-35.37~20.04.1
Confirmed. Just updated and same.
Can you backport the fix to the 20.04 HWE kernel? I mean that's the one
Canonical recommends has as first choice if downloading Ubuntu from
ubuntu.com, for years now. And they've become more stable in my
experience than the ones between LTS versions, which is
Yes I can confirm that the updated HWE kernel
5.11.0-36.40~20.04.1-generic didn't work; same log errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in
I've just updated to kernel 5.11.0-36.40~20.04.1 (I'm on HWE stack on
Linux Mint 20.2). I'm still getting the same log errors as OP reported.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in
20.04.4? Kinda need to use LTS versions, us that need that stability at
least.
Not really interested in fixes for 21.10 or something... Focal.
--
You received this bug notification because you are a member of Kernel
Packages,
This bug was fixed in the package linux - 5.13.0-16.16
---
linux (5.13.0-16.16) impish; urgency=medium
* impish/linux: 5.13.0-16.16 -proposed tracker (LP: #1942611)
* Miscellaneous Ubuntu changes
- [Config] update toolchain in configs
* Miscellaneous upstream changes
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
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg
On todays updated kernel 5.11.0-34-generic is next message:
[7.284731] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[7.284753] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to
register, -22
--
You received this bug notification because you
The Hirsute kernel to be verified is: 5.11.0-35.37 or the current
hwe-5.11 (5.11.0-35.37~20.04.1) kernel for focal. The Impish work (5.13)
is still in progress.
** Tags removed: verification-failed-hirsute
** Tags added: verification-needed-hirsute
--
You received this bug notification because
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Added tag 'verification-failed-hirsute'. Enabled proposed and installed
package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4'
on my 20.04.3 LTS, and still get in dmesg:
[1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[1.228732]
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This is NOT fix-released, yet.
** Changed in: linux (Ubuntu Hirsute)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after
These two error messages display when booting and closing live disk
media using 'safe graphics'
gpio gpiochip: (gpio_aaeon): tried to insert a GPIO chip with zero lines
gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22
they do not seem to upset the processes of the
** Description changed:
[Impact]
- After upgrade kernel to 5.11.0-25, user encounters below errors
+ After upgrade kernel to 5.11.0-25 which introduce some ODM patches from
AAEON, user encounters below errors
[ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with
zero
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1937897
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
OOps, this this isn't the same kernel!? Ignore my comment then!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after update of kernel
No it unfortunately did not work. With the new HWE kernel Ubuntu
5.11.0-27.29~20.04.1-generic (same as above?).
The failing lines are at two places in the log. Boot is very quick
though but it is annoying seeing the red lines.
--
You received this bug notification because you are a member of
Hi,
This is the test kernel which should fix this issue, please give it a try.
Thanks.
https://people.canonical.com/~acelan/bugs/lp1937897/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
+ After upgrade kernel to 5.11.0-25, user encounters below errors
+ [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
+ [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to
register, -22
+ [
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
No, I can't, because there isn't a single module loaded with even the
name "gpio" in it.
So running: $ lsmod|grep gpio == No result
It's in the kernel, not a module. I reverted to the GA kernel and
although with that I've had some issue with on headless *Intel* NUC
running Virtual Machines that
27 matches
Mail list logo
