Bug 77977

Summary: [gm45 regression] BIOS vs ringbuffer fight after hibernate
Product: DRI Reporter: Bjørn Mork <bjorn>
Component: DRM/IntelAssignee: Ben Widawsky <ben>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
/sys/class/drm/card0/error none

Description Bjørn Mork 2014-04-26 17:53:34 UTC 
Got this after resuming from hibernate on v3.15-rc2:

[drm] stuck on render ring
[drm] GPU HANG: ecode 0:0xf7e5ecbe, in Xorg [3503], reason: Ring hung, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 Bjørn Mork 2014-04-26 17:57:16 UTC 
Created attachment 98052 [details]
/sys/class/drm/card0/error

Attaching gpu crash dump
Comment 2 Daniel Vetter 2014-05-19 10:48:35 UTC 
Bjorn, any chance for a bisect, or is this only sporadic?
Comment 3 Bjørn Mork 2014-05-19 10:59:46 UTC 
Sorry, this has only happened once.  So I am not even sure it is a regression. Don't think I added that label on this bug report?
Comment 4 Daniel Vetter 2014-05-19 11:36:06 UTC 
I added it since presumably you'd have reported it earlier if it wasn't a regression ;-) Also we've frobbed around the gpu memory layout a bit in 3.15 which would make your bug more likely.

I think we'll keep this open for a bit longer, but if you can't reproduce we need to close it due to insufficient data unfortunately.
Comment 5 Chris Wilson 2014-05-19 11:45:19 UTC 
On second thoughts, this is bug 76554 as the ring failed to start properly. Notice that the registers read back garbage, and those garbage reads occurred during ring-init upon resume: ring->head: 0xffe00000

*** This bug has been marked as a duplicate of bug 76554 ***

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.