X crashes after suspend or hibernate when playing video using intel video overlay i945GM in Hardy

Bug #229128 reported by DenisP
8
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

When my laptop wakes up from hibernate or suspend when I try to play video clip using intel video overlay x freezes with black screen and some weird stuff on screen after couple of seconds, it doesn't happen after each time laptop is suspended sometimes it takes 5 suspends until x crashes sometimes only 1. This happens only if any sort of compositing is activated, it doesn't matter if it is metacity compositing or compiz-fusion, without compositing and desktop effects this crash doesn't happen. After x freezes and crashes there is no other way to make system usable again then to power it down over power button because keyboard is not working. My laptop type is Samsung Q35 Model:NP-Q35.

I hope this bug will be solved soon because it is preventing me of using any sort of compositing, and I like this eye candy very much.

Thank you!

Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach your /var/log/Xorg.0.log and a full backtrace. See http://wiki.ubuntu.com/X/Backtracing for directions.

Changed in xserver-xorg-video-intel:
status: New → Incomplete
Revision history for this message
DenisP (denisp) wrote :

Here is my xorg.0.log after the crash. I hope this will help you further.

Besides this issue also have had some other problems with my graphic. If I connect external monitor and work with it after some 1 Hour + I get a whiteout, the whole screen gets white and I can't see anything to solve this I must restart the xserver with crl+alt+backspace and log in again.
Also I noticed some problem with switching from X11 to consoles with ctrl+alz+F1 etc. sometimes after hibernate or suspend I get white screen if I try to switch to console from X11. I don't know if this bugs are related to this first bug but they are happening also without any compositing switched on.

I hope someone has an Idea how to solve this problems, for me it seems that intel drivers are very unstable or is it my system?!

Revision history for this message
unggnu (unggnu) wrote :

Please also attach the file /var/log/Xorg.0.log.old directly after the crash.

Revision history for this message
DenisP (denisp) wrote :

Here also the requested /var/log/Xorg.0.log.old directly after the crash.

Revision history for this message
unggnu (unggnu) wrote :

You uploaded the Xorg.0.log.old past a reboot after your system had crashed?
Maybe it is a kernel issue but shutdown seems to work according to your first post. Does Ubuntu really shutdown or do you press the power button for more than three seconds?
If you are not able to switch to console after crash with ctrl + alt + f1 it is a kernel issue I guess.

Revision history for this message
DenisP (denisp) wrote :

I am not able to switch to console after the crash and yes I must press the power button for more than three seconds in order to shut down.
I don't know if it is the kernel issue but it only happens in connection with my described actions in first post, everything else works properly, only if I try to play video then whole system crashes with weird black screen with green stripes, because of that I have thought that this must have something to do with intel graphic driver, if I don't use IntelVideoOverlay with compositing on or if I use IntelVideoOverlay without compositing then I don't get any problems.

Revision history for this message
DenisP (denisp) wrote :

I must correct myself there are also the two problems with whiteouts on the external monitor and sometimes if I switch to console I get white screen instead of the console but I can switch back to X11 with the ctrl+shift+F7.

Revision history for this message
DenisP (denisp) wrote :

Is there any possibility to resolve this problems somehow? If it is kernel issue, how to further diagnose it? Any suggestion is welcome!

Revision history for this message
DenisP (denisp) wrote :

I have now tried to suspend and hibernate my machine wit the result that on each resume from hibernate my console is not reachable only thing I see when I try to switch to console with ctrl+alt+f1 etc. is white screen, X11 is working without problems. This error only happens when I resume from hibernation, suspend is working without this error. This error happens regardless of activating the compositing. I don't know if my first problem is somehow connected to this one.

If someone has any Idea how to solve this please write your Idea here, any suggestion is welcome.

Revision history for this message
DenisP (denisp) wrote :

In my report for the Bug #238131 I was suggested to try the unofficial package http://people.ubuntu.com/~bryce/Testing/intel/hardy-i386/xserver-xorg-video-intel_2.3.1-1ubuntu1~bwh3_i386.deb.

This unofficial driver solves this bug for me.

Revision history for this message
unggnu (unggnu) wrote :

Thanks for testing and reporting back. This issue is fixed in Intrepid so marking as such. It is unlikely that the fix could be backported to Hardy since it is most likely in the huge Xv commit but you could try to nail it down if you like.

You can try out the 'rac763634' git driver at this page: http://people.ubuntu.com/~bryce/bisect/
If that version works, please try some of the older ones to see where it switches from working to failing; this will help us in narrowing down at what point it started working.
If only the latest version (rac763634) works the patch is in the huge Xv commit and will most likely not backported.
Btw. since Textured video is the default in the bisect -intel driver you manually have to activate overlay each time with your video player. The easiest way is to install mplayer and start it with "mplayer -vo xv:port=<n> <VideoName>" where <n> is the port number you get from xvinfo for the video overlay adaptor.

Changed in xserver-xorg-video-intel:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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