Graphics crash

[BSOD]

I took a video about strange crash of my ubuntu 11.04
http://www.youtube.com/watch?v=U9dfz5N2VLQ

I was doing nothing special before that: just surfing in chrome and talking in skype (I don't remember what actually was the last) then my screen has been frozen for a split second, blinked and then began what is shown in the video.
I had runned Chrome, Skype, NetBeans, Gnome-terminal, Tomboy, LO Writer, may be Gimp and Firefox, nothing more.

I had similar bug few days ago but at that time my screen just got frozen (no blinking as on video).

Hardware:
ASUS u30jc
video: nvidia optimus (intel + nv card). nouveau driver is blacklisted, proprietary is not installed

Ubuntu:
10.10 upgraded to 11.04; Unity session.
---
Architecture: i386
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Package: xorg 1:7.6+4ubuntu3
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Tags: natty running-unity ubuntu
Uname: Linux 2.6.38-8-generic-pae i686
UnreportableReason: Please work this issue through technical support channels first.
UpgradeStatus: Upgraded to natty on 2011-04-23 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[IKT (ikt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 778222

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[BSOD (lm-bsod)]

Ok, I did.

I just got "No additional information collected." message, nothing more.

[IKT (ikt)]

wops, try now :)

[BSOD (lm-bsod)]

apport information

[BSOD (lm-bsod)]

ok, now it have sent something :)

[IKT (ikt)]

hmm was expecting a lot more logs to be attached.

Are you able to attach these logs which are in /var/log/:

dmesg
Xorg.0.log
kern.log

thanks :)

[BSOD (lm-bsod)]

ok

[IKT (ikt)]

Going to throw this against compiz because of:

May 6 03:16:42 bsod-U30Jc kernel: [174450.049446] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 6 03:16:42 bsod-U30Jc kernel: [174450.051478] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 12502359 at 12502350, next 12502360)
May 6 03:16:43 bsod-U30Jc kernel: [174451.767204] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 6 03:16:43 bsod-U30Jc kernel: [174451.767293] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 12502369 at 12502350, next 12502459)
May 6 03:16:45 bsod-U30Jc kernel: [174453.780538] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
May 6 03:16:45 bsod-U30Jc kernel: [174453.781050] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
May 6 03:16:45 bsod-U30Jc kernel: [174453.781052] [drm:i915_reset] *ERROR* Failed to reset chip.
May 6 03:16:45 bsod-U30Jc kernel: [174453.782818] compiz[1723]: segfault at 0 ip b6f6b171 sp bfd3fd30 error 6 in libc-2.13.so[b6e53000+15a000]
May 6 03:16:50 bsod-U30Jc kernel: [174458.044330] compiz[10648]: segfault at 0 ip b629c2ce sp bf9a32d0 error 6 in i965_dri.so[b6284000+a4000]
May 6 03:16:53 bsod-U30Jc kernel: [174461.358194] compiz[10653]: segfault at 0 ip b628f2ce sp bff393e0 error 6 in i965_dri.so[b6277000+a4000]
May 6 03:16:56 bsod-U30Jc kernel: [174464.288324] compiz[10657]: segfault at 0 ip b63102ce sp bf86aeb0 error 6 in i965_dri.so[b62f8000+a4000]
May 6 03:16:58 bsod-U30Jc kernel: [174466.952542] compiz[10662]: segfault at 0 ip b62e62ce sp bfd38d90 error 6 in i965_dri.so[b62ce000+a4000]
May 6 03:17:01 bsod-U30Jc kernel: [174469.627815] compiz[10666]: segfault at 0 ip b63802ce sp bfe51f20 error 6 in i965_dri.so[b6368000+a4000]
May 6 03:17:04 bsod-U30Jc kernel: [174472.278055] compiz[10671]: segfault at 0 ip b62602ce sp bfb1e730 error 6 in i965_dri.so[b6248000+a4000]
May 6 03:17:07 bsod-U30Jc kernel: [174475.090137] compiz[10673]: segfault at 0 ip b62ff2ce sp bf9fc2d0 error 6 in i965_dri.so[b62e7000+a4000]
May 6 03:17:09 bsod-U30Jc kernel: [174477.848641] compiz[10678]: segfault at 0 ip b62a52ce sp bfaef480 error 6 in i965_dri.so[b628d000+a4000]
May 6 03:17:12 bsod-U30Jc kernel: [174480.814668] compiz[10680]: segfault at 0 ip b63772ce sp bfc6a6e0 error 6 in i965_dri.so[b635f000+a4000]
May 6 03:17:15 bsod-U30Jc kernel: [174483.778654] compiz[10682]: segfault at 0 ip b633b2ce sp bf8f0c80 error 6 in i965_dri.so[b6323000+a4000]
May 6 03:17:18 bsod-U30Jc kernel: [174486.550470] compiz[10687]: segfault at 0 ip b62e82ce sp bf8a1440 error 6 in i965_dri.so[b62d0000+a4000]
May 6 03:17:21 bsod-U30Jc kernel: [174489.516655] compiz[10689]: segfault at 0 ip b62a02ce sp bf9c6ee0 error 6 in i965_dri.so[b6288000+a4000]
May 6 03:17:24 bsod-U30Jc kernel: [174492.443142] compiz[10691]: segfault at 0 ip b622b2ce sp bf8d1ec0 error 6 in i965_dri.so[b6213000+a4000]
May 6 03:17:27 bsod-U30Jc kernel: [174495.389321] compiz[10693]: segfault at 0 ip b630f2ce sp bfdee330 error 6 in i965_dri.so[b62f7000+a4000]
May 6 03:17:30 bsod-U30Jc kernel: [174498.379059] compiz[10698]: segfault at 0 ip b6336...

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.