Bug 15414 - [Randr 1.3] X crash when run xrandr on 945GM
Summary: [Randr 1.3] X crash when run xrandr on 945GM
Status: VERIFIED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Keith Packard
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-08 19:51 UTC by WuNian
Modified: 2009-08-25 20:22 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg log file (57.92 KB, text/plain)
2008-04-08 19:51 UTC, WuNian
no flags Details

Description WuNian 2008-04-08 19:51:20 UTC
Created attachment 15773 [details]
xorg log file

Source:
xserver, libXrandr, randrproto, xrandr : transform-proposal branch
xf86-video-intel: projective-965 branch

My 945GM machine has three output:VGA, LVDS and TV.
If VGA not connected, X crashed when run xrandr commands, like "xrandr -q". Following is the backtrace info:

It seems that X stepped into dead loop:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209301312 (LWP 8208)]
0x080e8d26 in xf86RotateBlockHandler (screenNum=0, blockData=0x0,
    pTimeout=0xbff1c6a8, pReadmask=0x81ef0e0) at xf86Rotate.c:273
273     {
(gdb) bt
#0  0x080e8d26 in xf86RotateBlockHandler (screenNum=0, blockData=0x0,
    pTimeout=0xbff1c6a8, pReadmask=0x81ef0e0) at xf86Rotate.c:273
#1  0x080e8d68 in xf86RotateBlockHandler (screenNum=0, blockData=0x0,
    pTimeout=0xbff1c6a8, pReadmask=0x81ef0e0) at xf86Rotate.c:278
#2  0x080e8d68 in xf86RotateBlockHandler (screenNum=0, blockData=0x0,
    pTimeout=0xbff1c6a8, pReadmask=0x81ef0e0) at xf86Rotate.c:278

TV is always disconnected. If I connected VGA, then start Xorg, the bug does not exist. If I ignored VGA in xorg.conf, the bug also does not exist.
Comment 1 Gordon Jin 2009-08-25 20:21:55 UTC
I believe this has been fixed quite long time ago.


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.