Summary: | [SNA] segfault in git master (b3d3c0e8e75) | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Sree Harsha Totakura <freedesktop> | ||||
Component: | Driver/intel | Assignee: | Chris Wilson <chris> | ||||
Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | blocker | ||||||
Priority: | medium | ||||||
Version: | git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Sree Harsha Totakura
2014-06-21 11:27:23 UTC
What's the display configuration at that moment? Can you also please attach your Xorg.0.log? The bug is that is dies trying to perform TearFree rotation on a disabled crtc. The crash fix looks easy, but I actually need to find out why the transform flag is still set I think. Argh, I wonder... I think the right fix is: diff --git a/src/sna/sna_display.c b/src/sna/sna_display.c index c540799..d05305e 100644 --- a/src/sna/sna_display.c +++ b/src/sna/sna_display.c @@ -1410,7 +1410,10 @@ sna_crtc_disable(xf86CrtcPtr crtc) sna->mode.dirty = true; } + sna_crtc->transform = false; + assert(sna_crtc->dpms_mode == DPMSModeOff); + assert(!sna_crtc->shadow); } commit 2046a49be59866a16db776ba53a588dbf6c02b12 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Sat Jun 21 15:43:32 2014 +0100 sna: Clear the transform flag on disabling the CRTC In places, we assume that if the flag is set, we must have an active CRTC. However, we were not clearing when disabling the CRTC. Reported-by: Sree Harsha Totakura <freedesktop@h.totakura.in> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=80325 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> I am pretty sure that is the fix for that crash. Please do let me know if there is anything else. > I am pretty sure that is the fix for that crash. Please do let me know if
> there is anything else.
Fix confirmed. Thank you.
|
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.