Bug 24199 - Regression: Segfault with xorg-server-1.6.4 and xf86-video-intel-2.8.1
Summary: Regression: Segfault with xorg-server-1.6.4 and xf86-video-intel-2.8.1
Status: RESOLVED DUPLICATE of bug 24200
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-28 11:57 UTC by Nick Bowler
Modified: 2009-09-28 14:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log (12.28 KB, text/plain)
2009-09-28 11:58 UTC, Nick Bowler 		no flags Details
View All

Description Nick Bowler 2009-09-28 11:57:23 UTC 
With xf86-video-intel-2.8.1, after upgrading to xorg-server-1.6.4, the server now segfaults immediately on startup.  I've attached the Xorg log.  1.6.3.901 worked fine, so I did a git bisect and it pointed at the following commit:

507e57381fea6334f7dc8da6925e53d2c76fddcb is first bad commit
commit 507e57381fea6334f7dc8da6925e53d2c76fddcb
Author: Keith Packard <keithp@keithp.com>
Date:   Fri Sep 18 21:12:17 2009 -0700

    xfree86/modes: Remove all framebuffer support from DGA
    
    This removes all rendering and mapping code from xf86DiDGA, leaving
    just mode setting and raw input device access. The mapping code didn't
    have the offset within /dev/mem for the frame buffer and the pixmap
    support assumed that the framebuffer was never reallocated.
    (cherry picked from 0b7c6c728c2e2d8433a188315cc591308a89cd85)
    
    Signed-off-by: Keith Packard <keithp@keithp.com>
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

:040000 040000 dca6c41b0d19df38bc3dd066611862972761bd34 80f3b373313a67a75d923ff5334b3a8874412e52 M	hw
Comment 1 Nick Bowler 2009-09-28 11:58:19 UTC 
Created attachment 29922 [details]
Xorg.0.log
Comment 2 Julien Cristau 2009-09-28 14:34:42 UTC 

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

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.