Summary: | [ivb] Tried to flip to an unpinned bo | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Alexandru DAMIAN <alexandru.damian> | ||||
Component: | DRM/Intel | Assignee: | Damien Lespiau <damien.lespiau> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | low | CC: | intel-gfx-bugs | ||||
Version: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Alexandru DAMIAN
2014-01-09 14:28:05 UTC
The command that fails is 0x00006190: 0x0a000001: MI_DISPLAY_BUFFER_INFO 0x00006194: 0x00003c01: dword 1 0x00006198: 0x056bc000: dword 2 Since we have not yet flipped we cannot have unpinned the future fb, and so it should appear in the list of pinned bo. It does not. Nor does it pin a fence register. Is this readily reproducible or just a freak hang? If you can reproduce it it'll be interesting to figure out when this happens. Most likely we have a stray MMIO write somewhere that completes the flip too early. Otoh how that manged to kill ivb is beyond me, the scratch page ptes should saves us. Seen only once, I don't have a repro rule. I'll keep an eye open and report if it happens again. |
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.