| Summary: | [gen4] GPU hang in chrome | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Adam <bugzilla> |
| Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | kern.log | ||
Comment on attachment 108702 [details]
kern.log
These are the relevant lines:
Oct 30 17:24:52 toughy kernel: [ 508.804037] [drm] stuck on render ring
Oct 30 17:24:52 toughy kernel: [ 508.804045] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Oct 30 17:24:52 toughy kernel: [ 508.804048] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Oct 30 17:24:52 toughy kernel: [ 508.804051] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Oct 30 17:24:52 toughy kernel: [ 508.804053] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Oct 30 17:24:52 toughy kernel: [ 508.804056] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Oct 30 17:24:52 toughy kernel: [ 508.805072] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x7908000 ctx 0) at 0x7908ed0
Oct 30 17:24:53 toughy kernel: [ 508.864192] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
Oct 30 17:24:53 toughy kernel: [ 509.312159] [drm:i915_reset] *ERROR* Failed to reset chip.
|
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 108702 [details] kern.log To reproduce the error I start Chrome (Version 38.0.2125.111 (64-bit)) and start the Tweetdeck App I have installed. Whenever I click the "New Tweet" button, the system freezes for about a second and then the screen blacks out. While the rest of the system is still running, there is no way re-enabling ANY graphics output from the Intel graphics adapter. I can only ssh into the machine and do a controlled reboot to regain any output. I have attached the kern.log as instructed by the log entry. The /sys/class/drm/card0/error file only contains the following line: no error state collected Any clues for me? Adam