[sandybridge-gt1] Xorg freeze

[Edmund Mergl]

Binary package hint: xorg

system freezes every few hours. Mouse can still be moved, but anything else including the keyboard ist not functional.
Xorg.log ends with: Fatal server error:
[ 79.552] xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

All this started when I moved to a Sandy Bridge system with integrated graphics.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
Architecture: amd64
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.3:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x960 1280x720 1024x768 1024x768 800x600 800x600 720x480 640x480 640x480 720x400
 edid-base64: AP///////wAebVdW1ycDAAESAQOANCB46lrVp1ZLmyQTUFSlSwCpQIGPswCBT4GAAQEBAQEBKDyAoHCwI0AwIDYAsEQRAAAaSD9AMGKwMkBAwBMAsEQRAAAeAAAA/QA4Sx5TEQAKICAgICAgAAAA/ABMMjQ2V0gKICAgICAgAakCAxxxSZAFBAMBHxQSEyMJBweDAQAAZQMMABAAAjqAGHE4LUBYLEUABkQhAAAeAR2AGHEcFiBYLCUABkQhAACeAR0AclHQHiBuKFUABkQhAAAejArQiiDgLRAQPpYABkQhAAAeAjqA0HI4LUAQLEUgBkQhAAAeAAAAAAAAAAAAvQ==
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Sat Mar 5 18:24:21 2011
DkmsStatus:
 nvidia-current, 260.19.06, 2.6.35-25-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.35-24-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.35-23-generic, x86_64: installed
GdmLog1: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-25-generic root=UUID=c3d9a6c7-0286-4ae1-b7c3-c9887bd1b517 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 11/02/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: H67A-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H67A-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-25-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Giga-byte Technology Device [1458:d000]

[Dave Gilbert (ubuntu-treblig)]

bottom of xorg.log.0.old has:

[ 24789.331] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 24789.331]
Backtrace:
[ 24789.334] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c5a8]
[ 24789.334] 1: /usr/bin/X (mieqEnqueue+0x1f4) [0x458ea4]
[ 24789.334] 2: /usr/bin/X (xf86PostMotionEventP+0xc4) [0x488d74]
[ 24789.334] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f0ebbbc3000+0x5319) [0x7f0ebbbc8319]
[ 24789.334] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f0ebbbc3000+0x5a0e) [0x7f0ebbbc8a0e]
[ 24789.334] 5: /usr/bin/X (0x400000+0x6d4e7) [0x46d4e7]
[ 24789.334] 6: /usr/bin/X (0x400000+0x1161a3) [0x5161a3]
[ 24789.334] 7: /lib/libpthread.so.0 (0x7f0ebfd64000+0xfb40) [0x7f0ebfd73b40]
[ 24789.334] 8: /usr/bin/X (0x400000+0x64a40) [0x464a40]
[ 24789.334] 9: /lib/libpthread.so.0 (0x7f0ebfd64000+0xfb40) [0x7f0ebfd73b40]
[ 24789.334] 10: /usr/lib/libpixman-1.so.0 (0x7f0ebfb05000+0x486f0) [0x7f0ebfb4d6f0]
[ 24789.334] 11: /usr/lib/libpixman-1.so.0 (0x7f0ebfb05000+0x51058) [0x7f0ebfb56058]
[ 24789.334] 12: /usr/lib/libpixman-1.so.0 (pixman_blt+0x78) [0x7f0ebfb35b98]
[ 24789.334] 13: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x2b2) [0x7f0ebcacc472]
[ 24789.335] 14: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0ebcee7000+0x32839) [0x7f0ebcf19839]
[ 24789.335] 15: /usr/bin/X (miCopyRegion+0xa5) [0x55c2a5]
[ 24789.335] 16: /usr/bin/X (miDoCopy+0x43a) [0x55c93a]
[ 24789.335] 17: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0ebcee7000+0x323be) [0x7f0ebcf193be]
[ 24789.335] 18: /usr/bin/X (0x400000+0xdf664) [0x4df664]
[ 24789.335] 19: /usr/bin/X (0x400000+0x3e599) [0x43e599]
[ 24789.335] 20: /usr/bin/X (0x400000+0x3f979) [0x43f979]
[ 24789.335] 21: /usr/bin/X (0x400000+0x2187b) [0x42187b]
[ 24789.335] 22: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f0ebeccfd8e]
[ 24789.335] 23: /usr/bin/X (0x400000+0x21409) [0x421409]

[Edmund Mergl (e-mergl)]

The freeze occurs when I switch the workspace, but it's not reproducible.

[Edmund Mergl (e-mergl)]

The freeze disappeared after I switched to another videocard.

[bugbot (bugbot)]

Hey Edmund,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.