This freeze was a one off event (so far). I do not have repro steps. I was basically just using firefox to browse the web (not even a video webpage or anything, just boring old linkedin.com). Just after freeze I find this in dmesg: [21456.983406] render error detected, EIR: 0x00000010 [21456.983410] IPEIR: 0x00000000 [21456.983412] IPEHR: 0x02000000 [21456.983414] INSTDONE: 0x808fffff [21456.983415] INSTPS: 0x8001e025 [21456.983417] INSTDONE1: 0x999fffae [21456.983419] ACTHD: 0x0c96b1b4 [21456.983420] page table error [21456.983422] PGTBL_ER: 0x01000000 [21456.983425] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking During the last hour leading up to the freeze, I had the solarwinds screensaver SEGV about 10 times due to bug this bug (which is fixed upstream but the fix is not in Ubuntu yet): https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bug/346072 A crashing userspace screensaver should, in theory, not affect system stability but I thought I'd mention it anyway. I'm using a snapshot of Ubuntu karmic which means I'm current on: Linux kingfish 2.6.31-8-generic #28-Ubuntu SMP Thu Aug 27 14:42:57 UTC 2009 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu karmic (development branch) Release: 9.10 Codename: karmic xserver-xorg-core 2:1.6.3-1ubuntu4 xserver-xorg-core-dbg 2:1.6.3-1ubuntu4 libdrm-intel1 2.4.12+git20090801.45078630-0ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu1 xserver-xorg-video-intel-dbg 2:2.8.1-1ubuntu1 libgl1-mesa-dri 7.6.0~git20090817.7c422387-0ubuntu3 libgl1-mesa-dri-dbg 7.6.0~git20090817.7c422387-0ubuntu3 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3 libgl1-mesa-glx-dbg 7.6.0~git20090817.7c422387-0ubuntu3 libglu1-mesa 7.6.0~git20090817.7c422387-0ubuntu3 mesa-utils 7.6.0~git20090817.7c422387-0ubuntu3 libdrm-intel1 2.4.12+git20090801.45078630-0ubuntu1 libdrm-radeon1 2.4.12+git20090801.45078630-0ubuntu1 libdrm2 2.4.12+git20090801.45078630-0ubuntu1 compiz 1:0.8.2-0ubuntu16 compiz-core 1:0.8.2-0ubuntu16 compiz-fusion-plugins-extra 0.8.2-0ubuntu4 compiz-fusion-plugins-main 0.8.2-0ubuntu5 compiz-gnome 1:0.8.2-0ubuntu16 compiz-plugins 1:0.8.2-0ubuntu16 compiz-wrapper 1:0.8.2-0ubuntu16 compizconfig-backend-gconf 0.8.2-0ubuntu2 compizconfig-settings-manager 0.8.2-0ubuntu1 libcompizconfig0 0.8.2-0ubuntu2 python-compizconfig 0.8.2-0ubuntu1
Created attachment 29003 [details] dmesg Note that everything starting at: [21600.568024] INFO: task i915/2:869 blocked for more than 120 seconds. ...and beyond is just me trying to do "cat /proc/dri/0/SOMETHING > something.txt" so it's post crash stuff caused by debugging efforts. This includes those stacks like: [21600.568056] [<ffffffff8151f2a7>] __mutex_lock_slowpath+0xd7/0x160 [21600.568060] [<ffffffff8151f1a6>] mutex_lock+0x26/0x50 [21600.568077] [<ffffffffa0060768>] i915_gem_retire_work_handler+0x38/0x90 [i915]
Created attachment 29004 [details] xorg.log (captured using ssh while hung)
Created attachment 29005 [details] intel_gpu_dump (gzipped because bugzilla didnt accept >1MB)
Created attachment 29006 [details] gdm.log
Created attachment 29007 [details] i915_batchbuffers
Created attachment 29008 [details] i915_error_state
Created attachment 29009 [details] i915_gem_active
Created attachment 29010 [details] i915_gem_fence_regs
Created attachment 29011 [details] i915_gem_flushing
Created attachment 29012 [details] i915_gem_hws
Created attachment 29013 [details] i915_gem_inactive
Created attachment 29014 [details] i915_gem_interrupt
Created attachment 29015 [details] i915_gem_request
Created attachment 29016 [details] i915_gem_seqno
Created attachment 29017 [details] i915_ringbuffer_data
Created attachment 29018 [details] i915_ringbuffer_info
Created attachment 29019 [details] froze again a few minutes after reboot, here is another full set of logs
looks similar to bug#22336
Thank you for the bug report, I am having to close this as there is not enough information to work out what the failure was - except to note that the current command stream is radically different to that which was captured here and probably fails in completely different ways.
Not the right information to know whether I've fixed this already.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.