[Hardy] X freezes after OpenGL use with corrupt screen (i945)

[vidak]

When using the video card's 3D capabilities, eg. using beryl window manager or something similar, the computer freezes at random times, and only a hard reset helps. The screen gets messed up with some horizontal stripes, and there is no response whatever I try to do. Without 3D I've experienced no such problems. I tried using the i810 and intel drivers for the video card (the type is Intel Corporation 82945G/GZ Integrated Graphics Controller according to lspci), but the case remained the same.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add your '/etc/X11/xorg.conf' file and your '/var/log/Xorg.0.log' file as attachments to your bug report? Thanks in advance.

[vidak (vidakris)]

xorg.conf attached

[vidak (vidakris)]

/var/log/Xorg.0.log attached

[vidak (vidakris)]

Could this be a hardware error, or is there a bug with the drivers/settings?

[Alessandro Urpi (alexurpi)]

The same happens to me. I'm running Feisty on a Dell Latitude D630, with a graphic card Intel with chipset X3100 (965gm driver on X). As soon as I start beryl, the video freezes (the mouse is still moving, but nothing more works!), and I have to hard reset the computer.
I'm attaching my xorg.conf.

[ifinishwhatistar (mjwagner)]

Ditto for me. Using Compiz fusion produces the same behavior (albeit occurring a bit later). I've tried the feisty current xorg intel video driver, apt pinning the new gutsy intel driver along with the new xserver, and the newly backported gutsy drivers (http://ubuntuforums.org/showthread.php?t=500668). Here's my xorg.conf

[Alessandro Urpi (alexurpi)]

I switched to gutsy, and everything is now working..

[Timo Aaltonen (tjaalton)]

vidak: please try a gutsy live-cd, since Alessandro reports that the issue should be fixed.

[vidak (vidakris)]

Bad luck: the bug is still there. Tried the latest daily kubuntu-cd and armagetron at full detail - it did the job for eg. three minutes then froze the same way... :(

[vidak (vidakris)]

Now I tried the installed gutsy, the problem is the same. I attached the end of Xorg.0.log

[Cris Amon (crisamon)]

The same happens to me with Gutsy installed. I'm running on a MSI M660 with a graphic card Intel, chipset 945GM Mobile 945GM/GMS/940GML Express Integrated Graphics Controller. System freezes with 3D Screensavers and at randon times with Compiz enabled.

[Cris Amon (crisamon)]

I've found at another bug comments about a similar trouble with ATI X300 Card.

"I have the suspicion that it is the "Animations" plugin that causes the freeze when one of the effects are activated (perhaps some pointer goes spoink). If this is the case, then further investigation would be to identify which animation is to blame.

So far I have deactivated the animations plugin and it seems to go ok :-)"

I've not tried yet ..

[vidak (vidakris)]

That would be great, I could at least use compiz (even without animations), however, my experince is that the problem is not limited to the use of composite window managers :(
(however, this is truly the largest of them :'( )

[Cris Amon (crisamon)]

I have deactivated animations plugin and the problem still happens. I think that it's a problem with intel driver. Maybe a conflict with power management system because most of troubles happens after a period of time without user interaction.

[vidak (vidakris)]

At my place the pc freezes even if it's just in use. I'm quite sure it should be a driver problem - however, if I remember well, I've tried both the i810 and intel drivers, too. I don't know how much difference could be between those two versions...

[Peter Clifton (pcjc2)]

Just to rule out possible problems, could the people seeing these lockups run the memtest option from their boot menu, and verify that there isn't any underlying hardware issue?

Can anyone someone reproduce this issue again please, and right after a reboot, attach the contents of /var/log/Xorg.0.log.old which will contain any information relating to the crash (if any).

[Cris Amon (crisamon)]

I've run the memtest and my memory is perfect, no errors. Microsoft Windows XP runs with no troubles in my laptop, so is not a bad memory problem.

Vidak, Can you try "noapic nolapic" options at boot (you can add at the end of boot options in menu.lst"). I've added and no troubles happens anymore, for one hour ... :-). Please, let me know your results.

[vidak (vidakris)]

Cris,
I've tried those kernel options, but I had no luck with them, either. I started compiz and the system waz frozen in about 3-5minutes. (first with rain effect and Cube, second time the Cube was enough). You could try to enable all the GPU-eating effects, and check the result...

We have two computers of the exact configuration at our place (main board, memory, cpu, graphic card, etc) producing the same problem, so I don't think it could be memory problem, however, if I'll have plenty of time I'll run a long memtest-run

Xorg.log is attached as requested.

[Cris Amon (crisamon)]

Vidak,

After a libpng update and "noapic nolapic" option my system seems to go perfect. No freezes with 3D screensavers and heavy compiz effects (including animations plugins). You could try just "noapic' option.

[vidak (vidakris)]

Cris,
could you please write the actual version of your libpng? (I think however I should have the latest version, since aptitude upgrade runs automatically each day...)

[Cris Amon (crisamon)]

libpng version 1.2.15~beta5-2ubuntu0.1.

Last weekend my system comes back freezing. I saw menu.lst and "noapic nolapic" option had been removed (i don't know why). So I have put options again and system seems to go ok again. At my place the problem really was solved with these options.

[vidak (vidakris)]

Still no luck. I managed to get a webcam, so I made some screenshots about the actual state of the system. (since I've never seen linux freeze this way :$ )

[FlagMan (flagman)]

Vidak, do you still see this issue?
(There has been an intel related gutsy update recently)

I am experiencing occasional freezes too, but only with AIGLX enabled.
I think my problem was discussed on dri-devel for 2.6.20 in the following thread:

http://<email address hidden>/msg29741.html

You could try to scan kern.log for drm errors, for example like this:

grep -i drm /var/log/kern.log

Hopefully we could get some more clues...

[vidak (vidakris)]

The problem is still present. :( The bug differs from the one you posted, since in my case there are no 'life signals' at all (like mouse movement, eg.)
output of grep -i drm /var/log/kern.log:
Feb 20 23:07:33 localhost kernel: [ 68.787951] [drm] Initialized drm 1.1.0 20060810
Feb 20 23:07:33 localhost kernel: [ 68.793010] [drm] Initialized i915 1.6.0 20060119 on minor 0
Feb 20 23:10:27 localhost kernel: [ 66.550799] [drm] Initialized drm 1.1.0 20060810
Feb 20 23:10:27 localhost kernel: [ 66.554187] [drm] Initialized i915 1.6.0 20060119 on minor 0
Feb 20 23:29:36 localhost kernel: [ 69.329366] [drm] Initialized drm 1.1.0 20060810
Feb 20 23:29:36 localhost kernel: [ 69.338982] [drm] Initialized i915 1.6.0 20060119 on minor 0
Feb 20 23:34:24 localhost kernel: [ 66.678254] [drm] Initialized drm 1.1.0 20060810
Feb 20 23:34:24 localhost kernel: [ 66.681272] [drm] Initialized i915 1.6.0 20060119 on minor 0
Feb 20 23:43:35 localhost kernel: [ 65.023293] [drm] Initialized drm 1.1.0 20060810
Feb 20 23:43:35 localhost kernel: [ 65.033296] [drm] Initialized i915 1.6.0 20060119 on minor 0
Feb 21 00:05:30 localhost kernel: [ 70.585726] [drm] Initialized drm 1.1.0 20060810
Feb 21 00:05:30 localhost kernel: [ 70.588627] [drm] Initialized i915 1.6.0 20060119 on minor 0

[unggnu (unggnu)]

Hardy Heron Alpha5 was recently released. It contains an updated version of the Intel driver. You can download and try the new Hardy Heron Alpha5 Live CD from http://cdimage.ubuntu.com/releases/hardy/alpha-5/ . If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha5 .

[vidak (vidakris)]

I've downloaded and booted the Live CD, updated to the new version of the intel driver, edited xorg.conf to load the 'intel' driver, restarted X, and started armagetron as test. After a few seconds the computer froze the same way as it used to, so the bug is still present :(

[unggnu (unggnu)]

Does it work without this problems under Windows or does Memtest runs fine? Maybe it is a hardware issue since everyone here seems to have a different video card.
If both are true I would report it upstream (http://intellinuxgraphics.org/how_to_report_bug.html) and post the link here.
Thanks

[vidak (vidakris)]

The same problem occured on two different computers of the same architecture. (see comment on 2007-10-26)

I've run memtest86+ for a night, which seemed to be frozen. In case of memory errors memtest should report it... Could this indicate hardware problems of the video card? I don't have the slightest idea what could this be... :S

ps.: I'll run memtest this weekend again, I'll post it's result, too.

[David Burke (bufke)]

I have the same problem on a Intel Extreme Graphics 855 GM card. The laptop worked fine in Gutsy even with compiz. With Hardy beta and compiz is off, it works fine. The Screens and Graphics says "none" for graphics driver. If I change it to i810 it won't work. If I change it to Intel - Experimental modesetting driver It seems to work, but after a reset it's back to "none". I used the modesetting driver on Gutsy. If this was a hardware problem then it shouldn't work on Gutsy.

[David Burke (bufke)]

I fixed it on my machine. This is how, first the screens and graphics wasn't letting me pick intel - exp... but after selecting another driver, then selecting intel-exp it worked. Reset computer, but now everything was slow. Compiz worked but it was slow and scrolling was very slow. Looking through some post about hardy being slow, I found this http://ubuntuforums.org/showthread.php?t=708928 the part that suggest adding Option "AccelMethod" "xaa"
to xorg.conf. I did so, restarted, and now it works fine. Compiz is working and now slowdown when scrolling. No random crashes(so far anyway). Here is my xorg if anyone is interested.

[srllorente (srllorente)]

Check this out: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/177492
It seems to be another way to solve the issue without going to XAA

hope it helps.

[unggnu (unggnu)]

Does still anyone has exactly this problem with final Hardy?

@vidak
Does Memtest works fine now for a long period?

[aslan (guepidon)]

i've got the same problem with my video card Intel Corporation 82945G/GZ Integrated Graphics.
With or without compiz, there are no differences, and running compiz does not cause any bugs.
But when i run an other 3d application using openGL (like supertuxkart or the solarwind screensaver, after 3 minutes the screen shows ugly colors and i can only type alt+sys+O because nothing else response.
can somebody help me ?

[vidak (vidakris)]

Sorry for the late answer...
The problem is still there, testing with armagetron caused the system freeze in 2seconds :(

[unggnu (unggnu)]

You can test a nearly current Intel driver from Debian sid. You have to remove the old i810 driver because the new one doesn't work parallel.
sudo apt-get remove xserver-xorg-video-i810 xserver-xorg-video-all
Download the current driver from http://mirrors.kernel.org/debian/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.3.1-1_i386.deb and install it.
After that restart X and check if your problem is gone. If you have made changes to your xorg.conf generate a new one please (sudo dpkg-reconfigure xserver-xorg) or just remove it to be sure.

If you want to reset everything do the follow commands.
sudo apt-get remove xserver-xorg-video-intel
sudo apt-get install xserver-xorg-video-all

Afterwards you will have the standard hardy driver again.

[vidak (vidakris)]

Tried the intel driver from debian, after two tests and reboots it seems that I still got the problem, however the prevoiusly mentioned corrupt screen changed to a frozen static one (I don't know whether this happened just by chance...)

[unggnu (unggnu)]

I guess it is the best to report it upstream. But there is one point. Could you please try to recreate the xorg.conf and test it again? Run "sudo dpkg-reconfigure xserver-xorg" and confirm all answers. You only have to check that the correct keyboard layout is chosen. Does it still happen with the new xorg.conf?
If so please use the Debian Sid driver and attach up-to-date files of /etc/X11/xorg.conf, /var/log/Xorg.0.log.old (past first reboot after the system has frozen) and the output of dmesg.

[unggnu (unggnu)]

Vidak, are you still interested in this bug report?

[Bryce Harrington (bryce)]

Closing as expired since it's over a month with no response. Feel free to reopen with the requested information if the issue still occurs.