Bug 687989 - [Sandy_Bridge] X server crash on resize
Summary: [Sandy_Bridge] X server crash on resize
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-intel
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 600438
TreeView+ depends on / blocked
 
Reported: 2011-03-15 23:09 UTC by Mark Gordon
Modified: 2013-07-28 23:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 19:44:42 UTC
Target Upstream Version:


Attachments (Terms of Use)
X log showing segfault (91.45 KB, text/plain)
2011-03-15 23:09 UTC, Mark Gordon
no flags Details

Description Mark Gordon 2011-03-15 23:09:10 UTC
Created attachment 485617 [details]
X log showing segfault

Description of problem:
If I resize the display, either via gnome-display-properties or xrandr -s, the X server crashes, and I'm bounced back to gdm.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.14.0-1.el6
xorg-x11-server-Xorg-1.7.7-28.el6

How reproducible:
100%

Steps to Reproduce:
1. xrandr -s 1024x768 (your available resolutions may vary)
  
Actual results:
Kaboom, gdm

Expected results:
Resize

Additional info:
X log shows segfault, see attachment

Comment 2 Matěj Cepl 2011-03-17 11:14:25 UTC
Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x4a2948]
1: /usr/bin/Xorg (0x400000+0x69fc9) [0x469fc9]
2: /lib64/libpthread.so.0 (0x3ce7800000+0xf520) [0x3ce780f520]
3: /usr/lib64/libpixman-1.so.0 (0x3cee000000+0x51066) [0x3cee051066]
4: /usr/lib64/libpixman-1.so.0 (0x3cee000000+0x5158e) [0x3cee05158e]
5: /usr/lib64/libpixman-1.so.0 (pixman_fill+0x3d) [0x3cee03112d]
6: /usr/lib64/xorg/modules/libfb.so (fbFill+0x2b6) [0x7f67120b0016]
7: /usr/lib64/xorg/modules/libfb.so (fbPolyFillRect+0x1da) [0x7f67120b04ba]
8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f6712ce8000+0x2f921) [0x7f6712d17921]
9: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f6712ce8000+0x26b01) [0x7f6712d0eb01]
10: /usr/bin/Xorg (0x400000+0xd513b) [0x4d513b]
11: /usr/bin/Xorg (miPaintWindow+0x1aa) [0x45ca2a]
12: /usr/bin/Xorg (miWindowExposures+0xc8) [0x45cdc8]
13: /usr/bin/Xorg (miHandleValidateExposures+0x2b) [0x54bc5b]
14: /usr/bin/Xorg (0x400000+0x85a77) [0x485a77]
15: /usr/bin/Xorg (0x400000+0x125690) [0x525690]
16: /usr/bin/Xorg (0x400000+0x12417d) [0x52417d]
17: /usr/bin/Xorg (ProcRRSetScreenConfig+0x4d0) [0x4c3290]
18: /usr/bin/Xorg (0x400000+0xba979) [0x4ba979]
19: /usr/bin/Xorg (0x400000+0x4ae7c) [0x44ae7c]
20: /usr/bin/Xorg (0x400000+0x2208a) [0x42208a]
21: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3ce741ec9d]
22: /usr/bin/Xorg (0x400000+0x21c49) [0x421c49]
Segmentation fault at address 0x7f6710e80010

Comment 3 Xiao, Hui 2011-03-24 07:30:48 UTC
Hi,

We have verified the graphic feature of:
[1] 
  PCI:*(0:0:2:0) 8086:0102:8086:2210 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller rev 9 on
 
  Sugar Bay (Sandy Bridge D1, Cougar Point B0) with

  image 2.6.32-118.el6.x86_64 

[2]
  PCI:*(0:0:2:0) 8086:0116:17aa:3975 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller rev 9 on 

  Huron River Production "Lenovo v470G-ISE" with

  image 2.6.32-118.el6.i686

no such issue occured.

From the log you seems using Integrated Graphics Controller rev 4? Can you tell more infor about:

[1] What platform are you using?
[2] What's the Processor/Chipset stepping?

Thanks

Comment 4 Mark Gordon 2011-03-24 19:17:31 UTC
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 04) (prog-if 00 [VGA controller])
        Subsystem: Intel Corporation Device [8086:2210]

Digital Home
Sandy Bridge C0 / Cougar Point B0

2.6.32-122.el6.x86_64

Comment 5 Xiao, Hui 2011-03-25 02:56:55 UTC
Hi,

we recommend to use the newer machine for all the tests. Could you please try to find a Sandy Bridge D stepping machine instead of C? :-)

Thanks

Comment 6 John Villalovos 2011-03-25 16:22:36 UTC
Mark,

Our SugarBay systems at Red Hat should be D stepping machines.

Which Sandy Bridge system are you using for your testing?

Comment 7 Mark Gordon 2011-03-31 19:44:42 UTC
Never mind.  Updated MB/CPU acquired & installed, and the problem can no longer be reproduced.  Closing.


Note You need to log in before you can comment on or make changes to this bug.