| Summary: | GPU hangs on opening chromium | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Eli Edrian Tan <eliedrian1996> | ||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | intel-gfx-bugs, Manuel.h87, senior-pimiento | ||||||||
| Version: | unspecified | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | SNB | i915 features: | GPU hang | ||||||||
| Attachments: |
|
||||||||||
Sep 29 00:49:40 mithrandir kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Sep 29 00:49:40 mithrandir kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Sep 29 00:49:40 mithrandir kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Sep 29 00:49:40 mithrandir kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Sep 29 00:49:40 mithrandir kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Another issue, now the gpu crashes with the downgraded package. Attaching gpu error log. Created attachment 118519 [details]
Gpu crash log
Created attachment 118520 [details]
Gpu crash log
Uploaded a wrong file
Chromium doesn't crash if AccelMethod is switched to UXA, however the GPU is still reporting to have crashed. *** Bug 92190 has been marked as a duplicate of this bug. *** Switching back to the default (SNA) and rebooting seems to fix the problem temporarily. Turning the laptop off for a while seems to cause this hanging to come back. (In reply to Eli Edrian Tan from comment #7) > Switching back to the default (SNA) and rebooting seems to fix the problem > temporarily. Turning the laptop off for a while seems to cause this hanging > to come back. We seem to have neglected the bug a bit, apologies. Hang is not happening in render ring so updating your kernel may fix the issue here. Indeed, there were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. (In reply to yann from comment #8) > (In reply to Eli Edrian Tan from comment #7) > > Switching back to the default (SNA) and rebooting seems to fix the problem > > temporarily. Turning the laptop off for a while seems to cause this hanging > > to come back. > > We seem to have neglected the bug a bit, apologies. > > Hang is not happening in render ring so updating your kernel may fix the > issue here. > > Indeed, there were improvements pushed in kernel and Mesa that will benefit > to your system, so please re-test with latest kernel & Mesa to see if this > issue is still occurring. Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system. |
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.
Created attachment 118498 [details] Full journalctl output On running startx to start i3, the system becomes unresponsive for a while (except for the mouse cursor). When the system finally becomes responsive, upon opening chromium X crashes. The logs contain references to the gpu hanging too fast Steps to reproduce: 1) run startx from a tty 2) attempt to start chromium Actual results: chromium hangs (does not even draw its contents), and X crashes. Expected: chromium starts up, with no hangs. Hardware and Build: Intel HD Graphics 3000, i915, Arch Linux Additional information: I have isolated the problem to the latest xorg-xinit package on Arch Linux (1.3.4-3). Downgrading to 1.3.4-2 resolves this problem. I do not think it is a packaging error, so I reported the bug here, and not on Arch's bug tracker. Attached is a full log containing the gpu hanging messages.