Bug 99129 - crash with intel-virtual-output in xf86RandR12CrtcComputeGamma()
Summary: crash with intel-virtual-output in xf86RandR12CrtcComputeGamma()
Status: RESOLVED DUPLICATE of bug 98855
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/RandR (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-17 16:45 UTC by Bruno Levy
Modified: 2016-12-17 16:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Bruno Levy 2016-12-17 16:45:15 UTC 
Experienced systematic crash with intel-virtual-output when starting some applications (e.g. emacs and all applications with 3D graphics).

distribution: Debian Stretch
xserver-xorg-core_2%3a1.19.0-2_amd64.deb
xserver-xorg-video-intel_2%3a2.99.917+git20161105-1+b1_amd64.deb
nvidia proprietary driver ver. 375.20-4

gdb reports the crash in xf86RandR12.c line 1263, in the function xf86RandR12CrtcComputeGamma(). 

If the function is commented-out, then the server no longer crashes.
Comment 1 Chris Wilson 2016-12-17 16:55:17 UTC 
commit 9ac7a3370ab265d4cbdbbf3dc588af88c37048e1
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Nov 29 22:01:21 2016 +0000

    sna: Handle xf86Randr12 gamma changes in xorg-xserver-1.19
    
    commit 17213b74fd7fc4c4e2fe7a3781e7422dd482a0ab
    Author: Michel Dänzer <michel.daenzer@amd.com>
    Date:   Tue Jun 21 16:44:20 2016 +0900
    
        xfree86/modes: Remove xf86RandR12CrtcGetGamma
    
    removed the randr_crtc->palettes allocation and initialisation causing a
    later dereference of the gamma table to crash. Looks like that was just
    ABI misuse.
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=98855
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

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

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.