Created attachment 1921057 [details] journalctl -x -b -1 Description of problem: Whenever i start to screenshare and present something on browser (firefox and chromium both) or applications (discord, slack) the system freezes and i have to forcefully shutdown the machine as it becomes completely unresponsive and crashes. This issue persists everytime i perform screenshare. It can be reproduced when i start to screen share and present something. On going through the logs and taking community support it's been declared as [drm] Intel GPU Hang on gnome-session. Version-Release number of selected component (if applicable): How reproducible: This issue is reproducible everytime when i perform screenshare and present. Steps to Reproduce: 1.Share/present screen in browser or application 2.After a while, the system hangs and no input. Actual results: GPU hang and crash to the login screen. Expected results: The screensharing should work flawlessly and GPU shouldn't crash Additional info:
Same problem on f37. There is probably dupe bug 2155242. My GPU: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Affected version: mesa-dri-drivers-22.2.3-1.fc37 Unaffected version: mesa-dri-drivers-22.2.2-1.fc37
mesa-dri-drivers-22.3.1 is also affected. The machine is unusable after the update. Any app using accelerated video crashes the GPU.
For my problem I opened upstream issue: https://gitlab.freedesktop.org/drm/intel/-/issues/7718
For me the problem was resolved by upstream commit: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20267 The fix isn't yet even in the mesa-22.3.1. Could you backport it? The accelerated video is unusable without it on f37 - frequent periodical GPU hangs leading to black screen and machine freezes.
Hi, sorry for the delayed reply. Is this still an issue, if so I can look into trying to get it backported next chance I get (or find someone else who can)
(In reply to Lyude from comment #5) > Hi, sorry for the delayed reply. Is this still an issue, if so I can look > into trying to get it backported next chance I get (or find someone else who > can) Yes, this issue is still persisting in my system. I seek assistance to fix this issue. Thank you for your response.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.