|Summary:||[chv] GPU hangs/resets, sometimes locks completely, in kwin_x11|
|Component:||Drivers/DRI/i965||Assignee:||Intel 3D Bugs Mailing List <intel-3d-bugs>|
|Status:||RESOLVED MOVED||QA Contact:||Intel 3D Bugs Mailing List <intel-3d-bugs>|
|i915 platform:||i915 features:|
Description Alex 2018-03-29 15:18:59 UTC
Created attachment 138429 [details] dmesg A laptop sometimes hangs with GPU reset or might lock completely especially if I leave it turned on in sleep state over night. I'm not sure if it is the same issue because can't read dmesg output, the system doesn't react neither on sysrq nor ctrl-alt-f2, simply a blank screen. I tried to add "intel_iommu=igfx_off" to kernel options without any luck, the issue still persists.
Comment 2 Kenneth Graunke 2018-03-29 22:33:50 UTC
1. What version of Mesa are you using? 2. Do you have a HD 400 or HD 405? (running "glxinfo | grep Mesa" should give you the answer to both questions)
Comment 4 Alex 2018-03-30 03:38:53 UTC
(In reply to Kenneth Graunke from comment #2) > 1. What version of Mesa are you using? > 2. Do you have a HD 400 or HD 405? > > (running "glxinfo | grep Mesa" should give you the answer to both questions) /home/user$ glxinfo |grep Mesa client glx vendor string: Mesa Project and SGI Device: Mesa DRI Intel(R) HD Graphics (Cherrytrail) (0x22b0) OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Cherrytrail) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.7 OpenGL version string: 3.0 Mesa 17.3.7 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.3.7 Attached a whole glxinfo output just in case. Some more info that might be related: - I use UXA as an acceleration method in xorg.conf, SNA flickers all the time. - Maybe it is just a coincidence. The first hang or lock usually occurs after some time swap started to be used (I use only zram as a backend).
Comment 5 GitLab Migration User 2019-09-25 19:10:22 UTC
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1709.