Bug 27725 - segfault if the option NoAccel is added to xorg.conf
Summary: segfault if the option NoAccel is added to xorg.conf
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/geode (show other bugs)
Version: 7.5 (2009.10)
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-18 11:02 UTC by Martin-Éric Racine
Modified: 2010-08-15 21:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.log with backtrace (17.94 KB, text/x-log)
2010-04-18 11:02 UTC, Martin-Éric Racine
no flags Details
Fix the crash (874 bytes, patch)
2010-04-28 21:35 UTC, Mart Raudsepp
no flags Details | Splinter Review

Description Martin-Éric Racine 2010-04-18 11:02:18 UTC
Created attachment 35145 [details]
Xorg.log with backtrace

When fed a minimal xorg.conf as follow:

Section "Device"
 Identifier "Geode Video"
 Driver "geode"
 Option "NoAccel" "true"
EndSection

xf86-video-geode 2.11.8 running on an X server 1.7 crashes with a segfault. Xorg.log including the backtrace is attached.

PS: never mind the 2.11.7 version in the log. This really is a 2.11.8 driver.
Comment 1 Mart Raudsepp 2010-04-28 21:35:07 UTC
Created attachment 35326 [details] [review]
Fix the crash

This is a trivial patch to fix the crash, but it doesn't seem as simple as that to get NoAccel to work right again after RANDR1.2 code introduction.
I get a black screen after starting up LXDE. Everything seems to work fine without accel only after switching back to console and then back to X again - then display appears and things work.
Comment 2 Mart Raudsepp 2010-08-15 21:25:20 UTC
Couldn't reproduce the issue myself anymore either, as well as many others. So even if in some circumstances the initialization fails without forcing it with a VT switch, the crash fix is still worth it, as it will work for most people then, if not all.
So I've pushed this.


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.