[Bug 1960242] Re: [amdgpu] kernel fault on monitor wakeup, only reboot recovers.
I've been encountering this problem with an RX 6600 using linux- image-5.15.0-22-lowlatency and linux-image-5.15.0-23-generic on Jammy. This had not been happening with linux-image-5.13.0-37-lowlatency on Impish. [78421.618570] INFO: task gnome-shell:2364 blocked for more than 241 seconds. [78421.618575] Not tainted 5.15.0-23-generic #23-Ubuntu [78421.618577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [78421.618578] task:gnome-shell state:D stack:0 pid: 2364 ppid: 2194 flags:0x4002 [78421.618581] Call Trace: [78421.618583] [78421.618585] __schedule+0x23d/0x590 [78421.618590] schedule+0x4e/0xb0 [78421.618591] schedule_preempt_disabled+0xe/0x10 [78421.618593] __mutex_lock.constprop.0+0x263/0x490 [78421.618596] __mutex_lock_slowpath+0x13/0x20 [78421.618597] mutex_lock+0x34/0x40 [78421.618598] amdgpu_dm_atomic_commit_tail+0x5a5/0x1430 [amdgpu] [78421.618737] ? dcn30_calculate_wm_and_dlg_fp+0x7b0/0xac0 [amdgpu] [78421.618861] ? hubbub3_get_dcc_compression_cap+0x92/0x2d0 [amdgpu] [78421.618995] ? dcn20_get_dcc_compression_cap+0x23/0x30 [amdgpu] [78421.619126] ? fill_gfx9_plane_attributes_from_modifiers+0x217/0x2e0 [amdgpu] [78421.619240] ? dcn30_validate_bandwidth+0x1a0/0x340 [amdgpu] [78421.619355] ? ttm_bo_mem_compat+0x30/0x90 [ttm] [78421.619359] ? fill_plane_buffer_attributes+0x137/0x290 [amdgpu] [78421.619470] ? __cond_resched+0x1a/0x50 [78421.619472] ? __wait_for_common+0x3e/0x150 [78421.619474] ? dm_plane_helper_prepare_fb+0x236/0x290 [amdgpu] [78421.619579] ? usleep_range_state+0x90/0x90 [78421.619581] ? wait_for_completion_timeout+0x1d/0x20 [78421.619583] commit_tail+0xc5/0x170 [drm_kms_helper] [78421.619593] ? drm_atomic_helper_swap_state+0x246/0x370 [drm_kms_helper] [78421.619601] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper] [78421.619608] drm_atomic_commit+0x4a/0x50 [drm] [78421.619623] drm_mode_atomic_ioctl+0x530/0x740 [drm] [78421.619636] ? drm_plane_create_color_properties.cold+0x48/0x48 [drm] [78421.619650] ? drm_atomic_set_property+0x150/0x150 [drm] [78421.619661] drm_ioctl_kernel+0xae/0xf0 [drm] [78421.619673] drm_ioctl+0x264/0x4b0 [drm] [78421.619683] ? drm_atomic_set_property+0x150/0x150 [drm] [78421.619695] ? recalibrate_cpu_khz+0x10/0x10 [78421.619697] ? ktime_get_mono_fast_ns+0x52/0xa0 [78421.619699] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [78421.619770] __x64_sys_ioctl+0x91/0xc0 [78421.619773] do_syscall_64+0x5c/0xc0 [78421.619776] ? syscall_exit_to_user_mode+0x27/0x50 [78421.619777] ? do_syscall_64+0x69/0xc0 [78421.619778] ? syscall_exit_to_user_mode+0x27/0x50 [78421.619779] ? do_syscall_64+0x69/0xc0 [78421.619781] ? do_syscall_64+0x69/0xc0 [78421.619782] ? do_syscall_64+0x69/0xc0 [78421.619783] ? irqentry_exit_to_user_mode+0x9/0x20 [78421.619784] ? irqentry_exit+0x19/0x30 [78421.619785] ? sysvec_apic_timer_interrupt+0x4e/0x90 [78421.619786] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [78421.619788] entry_SYSCALL_64_after_hwframe+0x44/0xae [78421.619789] RIP: 0033:0x7fd826692aff [78421.619791] RSP: 002b:7ffed2c1a150 EFLAGS: 0246 ORIG_RAX: 0010 [78421.619793] RAX: ffda RBX: 7ffed2c1a1f0 RCX: 7fd826692aff [78421.619794] RDX: 7ffed2c1a1f0 RSI: c03864bc RDI: 0009 [78421.619794] RBP: c03864bc R08: 000f R09: 000f [78421.619795] R10: 0007 R11: 0246 R12: 561f321406c0 [78421.619796] R13: 0009 R14: 561f33630420 R15: 561f349c6660 [78421.619797] [78421.619966] INFO: task kworker/4:1:96189 blocked for more than 241 seconds. [78421.619968] Not tainted 5.15.0-23-generic #23-Ubuntu [78421.619969] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [78421.619970] task:kworker/4:1 state:D stack:0 pid:96189 ppid: 2 flags:0x4000 [78421.619972] Workqueue: events drm_sched_job_timedout [gpu_sched] [78421.619976] Call Trace: [78421.619977] [78421.619977] __schedule+0x23d/0x590 [78421.619980] schedule+0x4e/0xb0 [78421.619981] schedule_preempt_disabled+0xe/0x10 [78421.619983] __mutex_lock.constprop.0+0x263/0x490 [78421.619985] __mutex_lock_slowpath+0x13/0x20 [78421.619986] mutex_lock+0x34/0x40 [78421.619987] dm_suspend+0xaa/0x270 [amdgpu] [78421.620118] ? nv_common_set_clockgating_state+0x9f/0xb0 [amdgpu] [78421.620201] ? amdgpu_device_set_cg_state+0x12f/0x280 [amdgpu] [78421.620274] amdgpu_device_ip_suspend_phase1+0xa7/0x190 [amdgpu] [78421.620345] amdgpu_device_ip_suspend+0x21/0x70 [amdgpu] [78421.620415] amdgpu_device_pre_asic_reset+0xdd/0x480 [amdgpu] [78421.620485] ? drm_fb_helper_set_suspend_unlocked+0x33/0xa0 [drm_kms_helper] [78421.620493] amdgpu_device_gpu_recover.cold+0x6ec/0x8f8 [amdgpu] [78421.620621] amdgpu_job_timedout+0x14f/0x170 [amdgpu] [78421.620722] drm_sched_job_timedout+0x6f/0x110 [gpu_sched] [78421.620724] process_one_work+0x22b/0x3d0 [78421.620727] worker_thread+0x53/0x410 [7842
[Bug 1063890] [NEW] GNOME clock applet shows wrong (next) month
Public bug reported: When clicking on the GNOME clock applet in the panel, the pop-up calendar automatically selects the same day of the next (following) month, not the current month. Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=862081 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-panel 1:3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 12:05:49 2012 GsettingsChanges: InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: gnome-panel UpgradeStatus: Upgraded to quantal on 2012-09-26 (11 days ago) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063890 Title: GNOME clock applet shows wrong (next) month To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1063890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059554] Re: "Google Docs" is a deprecated term, nowadays its name is "Google Drive"
** Also affects: webapps-applications Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059554 Title: "Google Docs" is a deprecated term, nowadays its name is "Google Drive" To manage notifications about this bug go to: https://bugs.launchpad.net/app-install-data-ubuntu/+bug/1059554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
