[G33] X freezes about a second after running "strace glxgears"

[Dima Ryazanov]

Run "strace glxgears". After about a second, X freezes. You can still move the mouse pointer, but nothing else works. I've tried Ctrl-Alt-F1, Ctrl-Alt-Backspace, Ctrl-Alt-Del, Alt-SysRq-{s,u,b} - none of them worked. If I ssh into the machine and run "killall -9 strace", it unfreezes X. But without sshd, I couldn't find any solution but to do a hard reboot.

I'm using an Intel integrated graphics card. From lspci output:
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)

$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

[Chris Crisafulli (itnet7)]

Adding the xserver pacakge.

[Dima Ryazanov (dima-gmail)]

/var/log/Xorg.0.log has lots of messages like this at the end, not sure if that's related:

tossed event which came in late
mieqEnequeue: out-of-order valuator event; dropping.
tossed event which came in late
mieqEnequeue: out-of-order valuator event; dropping.
tossed event which came in late

Btw, this makes debugging OpenGL applications close to impossible.

[Bryce Harrington (bryce)]

Hi dimster-gmail,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

[Dima Ryazanov (dima-gmail)]

This also happens in 8.10.

[Michele Mordenti (micmord)]

I have the same problem with my hardware.
Enabling the UXA acceleration the problem disappear, but I got in trouble with bug 330236

lspci -vvnn
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:2572]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at fe780000 (32-bit, non-prefetchable) [size=512K]
        Region 2: I/O ports at eff0 [size=8]
        Capabilities: <access denied>
        Kernel modules: intelfb

uname -a
Linux i59508 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:43:21 UTC 2009 i686 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

Driver
ii xserver-xorg-video-intel 2:2.6.1-1ubuntu2 X.Org X server -- Intel i8xx, i9xx display d

[Andres Mujica (andres.mujica)]

similar to http://bugs.freedesktop.org/show_bug.cgi?id=20560 but a different chipset.

[Bryce Harrington (bryce)]

We have a PPA with some new tools for debugging X freezes:

  https://launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test

I know how irritating X freezes can be. They're also typically
quite hard to debug, but the information provided by these new
tools should help upstream figure them out.

You can help by doing the following:

 A. Install the PPA packages on Jaunty and boot kernel 2.6.30-rc2
 B. Reproduce your freeze
 C. ssh into the machine and run the steps to collect the info
 D. Attach the tarball of the results to this bug report

With this information, we'll be able to forward your bug upstream.

(For more information on triaging X freeze bugs, see
 https://wiki.ubuntu.com/X/Troubleshooting/Freeze )

[Bryce Harrington (bryce)]

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.