| Summary: | [BAT APL] gem_exec_suspend/basic-S3: GPU hang | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Imre Deak <imre.deak> | ||||||
| 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 | ||||||
| Version: | DRI git | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | BXT | i915 features: | GPU hang | ||||||
| Attachments: |
|
||||||||
|
Description
Imre Deak
2016-10-28 13:51:12 UTC
That hang is right in the middle of suspend. So should be near the start since we flush the active rendering early on. I wonder if it happens to be something like we stop listening to an irq too early? The error state might be interesting. Created attachment 127588 [details] GPU error state (In reply to Chris Wilson from comment #1) > That hang is right in the middle of suspend. So should be near the start > since we flush the active rendering early on. I wonder if it happens to be > something like we stop listening to an irq too early? Could be. I also noticed hpet1: lost 7161 rtc interrupts errors starting to appear after the problem. > The error state might be interesting. Attached. The render ring is off in a world of its own, flying through space, blt, bsd, vebox all coincidentally wrapped at exactly the same time with just before the breadcrumb for idling on suspend - and on all 3 rings it parsed the MI_FLUSH_DW command but did not execute the seqno write. Otherwise they look solid, all the pointers (acthd, faddr, ring start match). Oh my. Reference to Imre's patchset: https://patchwork.freedesktop.org/series/14789/ Fix merged to -nightly. (In reply to Imre Deak from comment #5) > Fix merged to -nightly. closing as fixed |
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.