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
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
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 Ubuntu
Bugs, which
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after update of
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]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929504
Title:
Add support for IO functions of AAEON devices
To manage notifications about this bug go to:
OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).
Worst of
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
Same on Ubuntu 20.04 both GA and HWE kernel.
Sure, it just takes this command to find which package has it:
$ apt-file search libbd_mdraid.so.2
And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it.
Depends on packages I don't need, MOST don't need:
$ apt show
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
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting.
Same problem too with Radeon RX 5500 XT. It worked on my Radeon RX 570
(AMD X570 + Ryzen 3950X). Using the generic ICD and Mesa OpenCL doesn't
work.
The easy fix that also gives better results on all benchmarks I've done
for Vulkan and OpenGL is installing the latest AMDGPU Pro driver
(version
FIX:
Finally found a solution that does not require me to disable screen
blanking and turning my monitors off physically:
1. Run dconf-editor
2. org > gnome > settings-daemon > plugins > power
3. "Set to Default" on ALL keys (this sets GNOME to never blank the screen
since
Running Alt + F2 and then "r" to restart GNOME Shell helps speed up
everything again, because AFAIK it restarts gnome-settings-daemon, but
after that it still uses relatively much more RAM than after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Running Valgrind as described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1321995
...I get the content in the attachment, not very helpful it seems? Also
see my screenshot above.
Note: It should be noted that I run a dual monitor setup with one
monitor on DVI and another on HDMI. Saw a
See attachment. gnome-settings-daemon eating 65 % of my 8 GB RAM less
than 24 hours after a reboot.
** Attachment added: "Bug.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+attachment/4827646/+files/Bug.png
--
You received this bug notification because
Same her on Ubuntu GNOME 16.04 64-bit with GNOME 3 Team PPA. gnome-
settings-daemon can eat up my 8 GB RAM after time, and then desktop 3D
animations are very slow/choppy. Solution is to log out and in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Having this problem on OS X when trying to boot Ubuntu 14.10 64-bit in
VirtualBox. Downloaded today from releases.ubuntu.com.
Screenshot:
http://i.imgur.com/ChcXFsY.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, so managed to get it to boot into the installer after like 5-6
reboots. Seemed totally random. Installed and booted into LightDM at
first try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380005
A workaround for me is to make the wallpaper readable only by the user.
So I have my wallpaper in the Pictures folder in my home folder, and by
giving it chmod 600 permissions (or my home folder 700 as I usually do),
LightDM can no longer access it and follows lightdm.conf instead.
--
You
Disabling guest login doesn't fix it for me (there's no guest login in
the login greeter anyway). Xubuntu 14.04 32-bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306362
Title:
AccountsService
Will this be fixed in Xubuntu 14.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306362
Title:
AccountsService conflicts with configured logon background
To manage notifications about this bug
Having the same problem on Ubuntu 14.04. Creating the connection
manually through nm-connection-editor works fine, but importing makes it
crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295439
24 matches
Mail list logo
