Ubuntu
linux package

Xorg freeze on xrandr --auto

Bug #693540 reported by Marius Gedminas on 2010-12-22

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

Binary package hint: xorg

After upgrading to Maverick, I've been noticing X freezes that happen after I unplug an external monitor and run xrandr --auto to reconfigure from dual-head to single-head mode. Symptoms include:
  * black screen
  * no reaction to CapsLock
  * working network
  * X.org eating 100% CPU
  * "[mi] EQ overflowing" in Xorg.0.log
  * "no error state collected" in /sys/kernel/debug/dri/0/i915_error_state
  * nothing out of the ordinary in dmesg

I've been running with Apport enabled in /etc/default/apport, in hopes that it will notice the freeze and collect a batchbuffer dump, as described in https://wiki.ubuntu.com/X/Troubleshooting/Freeze. This does not appear to be happening :(

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
DRM.card0.DVI.D.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1280x800
edid-base64: AP///////wAwrlBAAAAAAAAQAQOAIRV46rNwmVlTjScjUFQAAAABAQEBAQEBAQEBAQEBAQEBEhsAgFAgEDAYIEQAS88QAAAZcRYAgFAgEDAYIEQAS88QAAAZAAAADwCBCjKBCigUAQAyDAAAAAAA/gAxNTRXMDEtVExFNQogAFQ=
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Wed Dec 22 21:41:51 2010
DkmsStatus:
virtualbox-ose, 3.2.8, 2.6.32-25-generic, i686: built
virtualbox-ose, 3.2.8, 2.6.35-23-generic, i686: installed
virtualbox-ose, 3.2.8, 2.6.35-22-generic, i686: installed
virtualbox-ose, 3.2.8, 2.6.35-24-generic, i686: installed
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: LENOVO 646655G
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic root=UUID=4efb22e5-85e5-4a14-9eaa-4f4435e321c3 ro quiet splash
ProcEnviron:
LANGUAGE=lt_LT:lt:en_GB:en
LC_CTYPE=lt_LT.UTF-8
PATH=(custom, user)
LANG=lt_LT.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 12/06/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETA7WW (2.07 )
dmi.board.name: 646655G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETA7WW(2.07):bd12/06/2007:svnLENOVO:pn646655G:pvrThinkPadT61:rvnLENOVO:rn646655G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 646655G
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-24-generic

Tags:

Revision history for this message

Marius Gedminas (mgedmin) wrote on 2010-12-22:

BootDmesg.txt Edit (66.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (42.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (18.9 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (29.3 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (361.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (521 bytes, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (105.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (247.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (27.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (41.1 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (2.5 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (11.5 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (2.2 KiB, text/plain; charset="utf-8")
peripherals.txt Edit (1.6 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (275 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (9.7 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Marius Gedminas (mgedmin) wrote on 2010-12-22:

Oh, I forgot to mention: ssh'ing into the machine and doing a sudo killall Xorg is sufficient to make the system usable again -- I get a fresh gdm prompt. All my open programs and documents are gone, of course.

bugbot (bugbot) on 2010-12-23

affects:

xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)

Revision history for this message

Nilbus (nilbus) wrote on 2011-01-07:

I've been experiencing this since sometime after a 10.04 install. I did a fresh install of 10.10 and updated, and I still have this problem.

OS: Ubuntu 10.10 64bit Desktop
Video card: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Kernel: 2.6.35-24-generic
Running compiz

I also see "[mi] EQ overflowing. The server is probably stuck in an infinite loop" in my Xorg.0.log.old after a reboot.
I also can recover from the freeze killing X via SSH. X is always running at 100% CPU when the freeze occurs. Music still plays while X is frozen.

I cannot systematically reproduce this bug. It happens usually when I use xrandr to switch from dual-head to single. These are the commands I use:

Dual: xrandr --output LVDS1 --mode 1280x800 --output VGA1 --below LVDS1 --mode 1280x1024
Single: xrandr --output LVDS1 --mode 1280x800 --output VGA1 --off

When I run the Single script, my VGA1 monitor shuts off, and my LVDS1 laptop display freezes on an early frame in the compiz wobbly windows animation where all the windows that were on the external monitor are moving to the laptop display. The screen does not go black.

Revision history for this message

Nilbus (nilbus) wrote on 2011-02-09:

Easiest way to recover: alt+sysrq+k to restart X

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-02-19:

Hi,

Thanks for reporting this X gpu lockup bug in Ubuntu maverick.

In my opinion GPU lockups are one of the most frustrating kinds of bugs, both as a user and a developer. I want take a few moments of your time to explain the situation with these types of bugs.

For some reason, -intel has been plagued with these freeze bugs for a long time. In the past -intel has had options to switch to legacy memory or rendering technologies as workarounds, but Intel tends to drop obsolete code pretty aggressively and unfortunately in maverick these workarounds are not available.

As a policy, Intel engineers look only at bugs that are seen in the most recent release of their drivers. With older versions of their drivers, such as the version in maverick, we're on our own.

On the plus side, they provide good tools for gathering debug data about the bugs, such as the intel_gpu_dump too. Unfortunately, the version of Apport in maverick doesn't capture the dmesg or X logs correctly (it collects the files at the time of freeze, but then overwrites them with clean, unhelpful versions when it goes to file the report for you.)

The version of these diagnostic tools in natty has been fixed up, and is allowing us to analyze GPU lockups a lot easier. This has helped us solve several of the bugs, and given us a handle on some of the more challenging ones.

Backporting these fixes may not be feasible though; by their nature the fixes for these type of bugs tend to be very low level, esoteric, and risky of causing something else to regress. Because the freezes are often hard to reproduce, it's not always possible to verify fixes anyway. It may be that our best bet is to focus on natty.

But for now, since these freezes typically require kernel patches to solve, I'm moving your bug report to the kernel package. They may be able to point you to a newer kernel likely to help with this issue.

affects:

xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu)

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2011-02-22:

Hi Marius,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: needs-upstream-testing
tags:	added: kj-triage
Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-04-24:

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Xorg freeze on xrandr --auto

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package