Created attachment 136570 [details] /sys/class/drm/card0/error Versions: linux 4.14.10-1 xf86-video-vesa 2.3.4-4 mesa 17.3.1-2 The display freezes for 5-20 seconds, but sometimes music keeps playing. Dmesg: [ 2282.601131] [drm] GPU HANG: ecode 6:0:0x84fefff8, in java [2056], reason: Hang on rcs0, action: reset [ 2282.601132] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2282.601133] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2282.601133] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2282.601134] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 2282.601134] [drm] GPU crash dump saved to /sys/class/drm/card0/error
I was using a lenovo T420s
Hello Baltazar, Could you give it a try to branch https://cgit.freedesktop.org/mesa/mesa/ and if still reproducible, attach a new error state? You mentioned that is easier to reproduce while gameplay, do you have any steps to reliably reproduce it?? Thank you.
(In reply to Elizabeth from comment #2) > Hello Baltazar, > Could you give it a try to branch https://cgit.freedesktop.org/mesa/mesa/ > and if still reproducible, attach a new error state? > You mentioned that is easier to reproduce while gameplay, do you have any > steps to reliably reproduce it?? > Thank you. I don't have a reliable way to reproduce it, even when I was trying to reproduce it for this post, I was about to close minecraft when it finally forze again. (minecraft is the most reliable in my experience, but it happened with a lot of games too.) Could you clarify which version should I branch?
Sorry, I meant which branch should I build? Should it be branch 17.3 or HEAD?
Head if possible. Thanks.
Created attachment 137050 [details] /sys/class/drm/card0/error (using new build) Finally I have managed to reproduce it, this time it happened while playing factorio.
Thanks for the update. By the log, I can guess it took a long time before it was reproduced, isn't it? If you could get an easy way to reproduce or get an apitrace, it will be really helpful.
Forget to ask, what version/commit did you build? 18.0?
(In reply to Elizabeth from comment #8) > Forget to ask, what version/commit did you build? 18.0? I have built it from arch's AUR, using this version: mesa-git 17.4.0_devel.99215.63b231309e-1
Baltazár, Could you please note what versions of Minecraft and Factorio did you use to reproduce the bug? As far it couldn't be reproduced in a set of Mesa/Kernel/Minecraft I have.
(In reply to Vladimir Los from comment #10) > Baltazár, Could you please note what versions of Minecraft and Factorio did > you use to reproduce the bug? > As far it couldn't be reproduced in a set of Mesa/Kernel/Minecraft I have. I can't remember, but I think it happened in muldiple different versions and definitely not just in factorio or minecraft. But it hasn't happened again since I'm using the mesa-git package. I can switch back to the stable relase if it helps.
-- 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/1670.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.