Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62286 - [mesa] System not exiting from suspend
Attached to Project:
Arch Linux
Opened by Vladimir (Vlad1m1r) - Tuesday, 09 April 2019, 13:24 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 01 May 2019, 12:57 GMT
Opened by Vladimir (Vlad1m1r) - Tuesday, 09 April 2019, 13:24 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 01 May 2019, 12:57 GMT
|
Details* package version: mesa 19.0.1-2
Description: I am upgraded my system with pacman -Syu. After the upgrade, system does not exiting suspend mode. After pressing any key display turns on and freezes, no response to keystrokes occurs. Reboot is possible only with pressing power button. dmesg output in that time: ---reboot--- apr 09 12:08:41 wshost kernel: [drm] GPU recovery disabled. apr 09 12:08:41 wshost kernel: [drm] IP block:gfx_v8_0 is hung! apr 09 12:08:41 wshost kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 470 thread Xorg:cs0 pid 471 apr 09 12:08:41 wshost kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=53902, emitted seq=53906 I am downgraded mesa package to 18.3.4-1 version, and suspend became working well. Additional info: System: laptop HP-15bw660ur, graphics Radeon HD 8690M (Sun XT) kernel: linux-5.0.7.arch1-1 GUI: KDE Steps to reproduce: Choose Suspend to RAM (suspend) option on the start menu, or just close laptop cover. |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 01 May 2019, 12:57 GMT
Reason for closing: None
Additional comments about closing: User request
Wednesday, 01 May 2019, 12:57 GMT
Reason for closing: None
Additional comments about closing: User request
Comment by Vladimir (Vlad1m1r) -
Monday, 22 April 2019, 21:06 GMT
I'm downgraded linux kernel to 4.20.12 version, and the problem is gone. it seems like a problem in linux 5.x