Repro on Ubuntu 22.04.1, Lenovo ThinkPad P5. If I try to change volume,
I get "Dummy Output". Similar report:
https://askubuntu.com/questions/1191649/no-sound-on-wake-dummy-output-
always-takes-over-pulseaudio-k-the-fix
--
You received this bug notification because you are a member of Kernel
Pack
That other issue could be the same, I just wish someone there would have
reproduced the exact stack trace attached by Boris here to be more
certain, which I reproduce as:
WARNING: CPU: 0 PID: 18016 at
/var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:3935
nv_restore_user_channels+0xce/0xe0 [nvidia]
BTW, the workaround from: https://forums.developer.nvidia.com/t/fixed-
suspend-resume-issues-with-the-driver-
version-470/187150/3?u=cirosantilli worked for me. I wouldn't expect
that workaround to be affected by lightdm vs gdm3, but maybe it is:
sudo systemctl stop nvidia-suspend.service
sudo sys
Repro same stack traces on 510 after some trial and error at:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510/+bug/1953674
Key discovery there: it reproduces almost every time when my laptop is
on battery power with the power cord unplugged, otherwise it generally
only happe
*** This bug is a duplicate of bug 1946303 ***
https://bugs.launchpad.net/bugs/1946303
OK, now noticed that my error lines are exactly the same as:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470/+bug/1946303 it's just I wasn't getting the logs
consistently before I had
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1946303
Title:
No v
*** This bug is a duplicate of bug 1946303 ***
https://bugs.launchpad.net/bugs/1946303
Then, re-enabled Wayland with NVIDIA purged, and suspend works there.
Then, re-installed and reenabled NVIDIA 510 (which blakclists Wayland
and puts me in X11 since no Wayland support yet), and boom problem
Dumping a bit more debug log before I forget:
I disabled NVIDIA from the software & updates. If I try to suspend:
- it immediately wakes up into lock screen
- I can't login anymore: after password, goes into black kernel log screen as
in boot
That was in Wayland, the new default. So I blacklist
I should also mention, I'm seeing a bunch of non-nvidia ACPI errors of
type:
Feb 09 06:58:43.863108 ciro-p51 kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM:
Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
(20210331/nsarguments-61)
Feb 09 06:58:44.131354 ciro-p51 kernel: ACPI
Repro on 510. Stack traces that happens some times:
Feb 09 06:30:47.610121 ciro-p51 kernel: WARNING: CPU: 0 PID: 18016 at
/var/lib/dkms/nvidia/510.47.03/build/nvidia/nv.c:3935
nv_restore_user_channels+0xce/0xe0 [nvidia]
Feb 09 06:30:47.610508 ciro-p51 kernel: Call Trace:
Feb 09 06:30:47.610527 ci
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1953674
Title:
Scre
Other bugs about wakeup not working, but I don't reproduce their main
error messages:
-
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055
-
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303
--
You received this bug notification
Public bug reported:
After upgrading to 21.10 from 21.04 this problem started happening.
It does not happen every time I suspend, and it usually happens after
suspending for a longer time. After suspending for a longer time, it
tends to happen most of the time.
I can SSH into the computer, so it
I'm on Ubuntu 20.10, default desktop, nvidia-driver-460, Quadro M1200
GPU, and VLC also crashes for me whenever I try to take a snapshot.
However, I don't get the gl information logs mentioned by OP, is just
says "segmentation fault".
I tried reverting to 450, and it still segfaults.
The `--verb
$ sudo dpkg-statoverride --add root root 0644 /boot/vmlinux-$(uname -r)
dpkg-statoverride: error: --add needs four arguments
only updated for a single kernel, and apparently not the one virt-make-
fs is using.
I then did:
sudo chmod +r /boot/vmlinuz-*
and virt-make-fs was happy.
--
You receiv
15 matches
Mail list logo
