[Bug 1980933] Re: Blanked screen doesn't wake up after put into powersave
Out of the system journal I think these are the smoking guns: Jul 06 23:14:20 Excelsior kernel: INFO: task firefox:cs0:6721 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:firefox:cs0 state:D stack:0 pid: 6721 ppid: 3462 flags:0x0220 Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_timeout+0xfb/0x140 Jul 06 23:14:20 Excelsior kernel: ? __wake_up_locked+0x16/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_default_wait+0x1c4/0x1f0 Jul 06 23:14:20 Excelsior kernel: ? dma_fence_free+0x20/0x20 Jul 06 23:14:20 Excelsior kernel: dma_fence_wait_timeout+0xb7/0xd0 Jul 06 23:14:20 Excelsior kernel: gmc_v10_0_flush_gpu_tlb+0x285/0x310 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_gart_invalidate_tlb+0x43/0x60 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_ttm_alloc_gart+0x150/0x1a0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_parser_bos+0x406/0x4e0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_ib_fill+0x1e3/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_cs_ioctl+0xf8/0x230 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_ioctl_kernel+0xae/0xf0 [drm] Jul 06 23:14:20 Excelsior kernel: drm_ioctl+0x264/0x4b0 [drm] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_cs_vm_handling+0x420/0x420 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? __seccomp_filter+0x4a/0x4a0 Jul 06 23:14:20 Excelsior kernel: amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Jul 06 23:14:20 Excelsior kernel: __x64_sys_ioctl+0x91/0xc0 Jul 06 23:14:20 Excelsior kernel: do_syscall_64+0x5c/0xc0 Jul 06 23:14:20 Excelsior kernel: ? exit_to_user_mode_prepare+0x92/0xb0 Jul 06 23:14:20 Excelsior kernel: ? syscall_exit_to_user_mode+0x27/0x50 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: ? do_syscall_64+0x69/0xc0 Jul 06 23:14:20 Excelsior kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Jul 06 23:14:20 Excelsior kernel: RIP: 0033:0x7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RSP: 002b:7fa95f32fa18 EFLAGS: 0246 ORIG_RAX: 0010 Jul 06 23:14:20 Excelsior kernel: RAX: ffda RBX: 7fa95f32fa80 RCX: 7fa97fc3a3ab Jul 06 23:14:20 Excelsior kernel: RDX: 7fa95f32fa80 RSI: c0186444 RDI: 0026 Jul 06 23:14:20 Excelsior kernel: RBP: c0186444 R08: 7fa95f32fbb0 R09: 0020 Jul 06 23:14:20 Excelsior kernel: R10: 7fa95f32fbb0 R11: 0246 R12: 7fa969dd7e00 Jul 06 23:14:20 Excelsior kernel: R13: 0026 R14: R15: 7fa916022090 Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: INFO: task kworker/13:0:20618 blocked for more than 120 seconds. Jul 06 23:14:20 Excelsior kernel: Tainted: P C O 5.15.0-40-generic #43-Ubuntu Jul 06 23:14:20 Excelsior kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 06 23:14:20 Excelsior kernel: task:kworker/13:0state:D stack:0 pid:20618 ppid: 2 flags:0x4000 Jul 06 23:14:20 Excelsior kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] Jul 06 23:14:20 Excelsior kernel: Call Trace: Jul 06 23:14:20 Excelsior kernel: Jul 06 23:14:20 Excelsior kernel: __schedule+0x23d/0x590 Jul 06 23:14:20 Excelsior kernel: schedule+0x4e/0xb0 Jul 06 23:14:20 Excelsior kernel: schedule_preempt_disabled+0xe/0x10 Jul 06 23:14:20 Excelsior kernel: __mutex_lock.constprop.0+0x263/0x490 Jul 06 23:14:20 Excelsior kernel: __mutex_lock_slowpath+0x13/0x20 Jul 06 23:14:20 Excelsior kernel: mutex_lock+0x34/0x40 Jul 06 23:14:20 Excelsior kernel: dm_suspend+0xaa/0x270 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? nv_common_set_clockgating_state+0x9f/0xb0 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? amdgpu_device_set_cg_state+0x12f/0x280 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend_phase1+0xa3/0x180 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_ip_suspend+0x21/0x70 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_pre_asic_reset+0xdd/0x480 [amdgpu] Jul 06 23:14:20 Excelsior kernel: ? drm_fb_helper_set_suspend_unlocked+0x33/0xa0 [drm_kms_helper] Jul 06 23:14:20 Excelsior kernel: amdgpu_device_gpu_recover.cold+0x6ec/0x8f8 [amdgpu] Jul 06 23:14:20 Excelsior kernel: amdgpu_job_timedout+0x14f/0x170 [amdgpu] Jul 06 23:14:20 Excelsior kernel: drm_sched_job_timedout+0x6f/0x110 [gpu_sched] Jul 06 23:14:20 Excelsior kernel: process_one_work+0x22b/0x3d0 Jul 06 23:14:20 Excelsior kernel: worker_thread+0x53/0x410 Jul
[Bug 1980933] Re: Blanked screen doesn't wake up after put into powersave
** Attachment added: "output of journalctl --user --no-pager (XZipped to match the system journal)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+attachment/5601834/+files/user-journal.log.xz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1980933 Title: Blanked screen doesn't wake up after put into powersave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980933] [NEW] Blanked screen doesn't wake up after put into powersave
Public bug reported: This is *similar* to #1968040 but I'm raising it as a separate issue as the workarounds there do not work for my system suggesting that this is indeed a separate bug. When allowing the system to blank the screen, it becomes impossible to awaken the screen some unknown length of time after DPMS poweroff is triggered. Neither the keyboard nor the mouse can be used to trigger the screens to power back on again once powered down by DPMS. My system is a custom-build desktop PC with a discrete AMD 6600XT GPU and two external 4k monitors. I have tried the workarounds in the above bug and neither worked. Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with ctrl+alt) does not bring the monitors back to life, and adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change the behaviour in any way. The system is still responsive to the network and I can SSH into the box to investigate when in this scenario. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 7 09:32:16 2022 InstallationDate: Installed on 2022-05-11 (56 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "output of journalctl --system --no-pager (XZipped due to being huge - ~900MB)" https://bugs.launchpad.net/bugs/1980933/+attachment/5601831/+files/system-journal.log.xz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1980933 Title: Blanked screen doesn't wake up after put into powersave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample]
** Tags added: jammy ** Tags added: xorg-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1266496] Re: extra "fi" in file
This issue is for Trusty Tahr, which ended mainstream support in 2019 and exits ESM in 2022. I vote we close this issue as WONTFIX for those distributions (I don't have permission to set WONTFIX status on this issue). Is this still relevant on any currently-supported releases of Ubuntu? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1266496 Title: extra "fi" in file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1266496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 508220] Re: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic
This issue is for Lucid Lynx, which reached EOL in 2013 for desktop packages. I vote we close this issue as WONTFIX (I don't have permission to set WONTFIX status on this issue). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/508220 Title: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/508220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
