Summary: | [ivb/bsw regression] WARN_ON(obj->frontbuffer_bits) | ||
---|---|---|---|
Product: | DRI | Reporter: | Chris Wilson <chris> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs, jwboyer |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Chris Wilson
2014-12-12 07:54:10 UTC
Is this happening without any other error before? By https://bugs.freedesktop.org/attachment.cgi?id=112115 I'd just say the disable flow without plane being updated is broken but nothing wrong with this frontbuffer tracking warn in general. But anyway I'm not sure this warn here is useful or if we should flush the frontbuffer instead of warning... Is this happening without any other error before? By https://bugs.freedesktop.org/attachment.cgi?id=112115 I'd just say the disable flow without plane being updated is broken but nothing wrong with this frontbuffer tracking warn in general. But anyway I'm not sure this warn here is useful or if we should flush the frontbuffer instead of warning... *** Bug 89189 has been marked as a duplicate of this bug. *** Now affecting linus/master. Does this still blow up with latest -nightly? I looked a bit at Steven Rostedts report for 4.0 and had no clue what's going wrong ... I used to be able to trigger it with a killall -9 Xorg, but no more. Ok let's tentatively close it then. Bug is probably still around though, just hiding :( |
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.