[i945g] karmic: INFO: task i915/* blocked for more than 120 seconds.

This sounds a lot like a lot like a GPU freeze. Could you check https://wiki.ubuntu.com/X/Troubleshooting/Freeze and if you agree, please provide a batchbuffer dump as described there.

Here is batchbuffer dump.

Same bug here after 9.04 > 9.10 upgrade.

No freeze without compiz.

Oops, disregard my previous attachement, I forgot to trigger the freeze before dumping.
So here's the freezed dump, sorry if anyone tried to figure out what was wrong in this one :)

Same bug here after 9.04 > 9.10 upgrade.

I'm seeing what looks like exactly the same thing on i830 (thinkpad X30), running 9.10 netbook remix updated today. Freezes the display hard when rendering the task chooser thingy (which I think uses 3d), can still login using ssh etc.

Here's the dri debug stuff from my X30. You know, this poor laptop hasn't had X working properly since hardy....

I can confirm this bug on an with an Intel D945GCLF, X never frozen here but the attached monitor is only recognized as 800x600 which is not true at all.

[ 44.456967] i2c-adapter i2c-0: unable to read EDID block.
[ 44.456976] i915 0000:00:02.0: VGA-1: no EDID data
[ 44.566577] [drm:edid_is_valid] *ERROR* Raw EDID:
[ 44.566590] <3>1f ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566596] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566602] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566608] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566614] <3>ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00 ................
[ 44.566620] <3>00 00 00 07 ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566626] <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
[ 44.566632] <3>ff ff ff ff ff ff ff ff ff f0 00 00 00 00 00 00 ................
[ 44.566636]
[ 44.566643] i915 0000:00:02.0: VGA-1: EDID invalid.
[ 44.841705] [drm:i915_wait_request] *ERROR* something (likely vbetool) disabled interrupts, re-enabling
[ 360.692039] INFO: task i915/1:292 blocked for more than 120 seconds.
[ 360.692048] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 36...

I have similar problems too. The computer is Dell Optiplex GX 260. I have disabled compiz, power saving options and updated BIOS to latest version A09.

Intel graphics is :
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
 Subsystem: Dell Device 0126
 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 e8000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at ff680000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: [d0] Power Management version 1
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: i915
 Kernel modules: i915

Kernel panic section is :
[248401.076087] i915/0 D c08145c0 0 253 2 0x00000000
[248401.076097] f6a2df04 00000046 eaa56000 c08145c0 f6ac4df8 c08145c0 3a030219 0000e1c7
[248401.076110] c08145c0 c08145c0 f6ac4df8 c08145c0 00000000 0000e1c7 c08145c0 f68b4e00
[248401.076122] f6ac4b60 f68cac14 f68cac18 ffffffff f6a2df30 c056f776 c0748e80 f68cac1c
[248401.076133] Call Trace:
[248401.076157] [<c056f776>] __mutex_lock_slowpath+0xc6/0x130
[248401.076163] [<c056f690>] mutex_lock+0x20/0x40
[248401.076215] [<f8257c0a>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
[248401.076228] [<c0157a7e>] run_workqueue+0x6e/0x140
[248401.076244] [<f8257be0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
[248401.076251] [<c0157bd8>] worker_thread+0x88/0xe0
[248401.076258] [<c015c280>] ? autoremove_wake_function+0x0/0x40
[248401.076264] [<c0157b50>] ? worker_thread+0x0/0xe0
[248401.076270] [<c015bf8c>] kthread+0x7c/0x90
[248401.076275] [<c015bf10>] ? kthread+0x0/0x90
[248401.076283] [<c0104007>] kernel_thread_helper+0x7/0x10

I have modified xorg.conf file - added AccelMethod "uxa", put only one resultion in screen section, disabled all the modules in section Modules.

Section "Device"
        Identifier "Configured Video Device"
        Boardname "Intel 845"
        Busid "PCI:0:2:0"
        Driver "intel"
        Screen 0
        Vendorname "Intel"
        Option "AccelMethod" "uxa"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
        Vendorname "Samsung"
        Modelname "Samsung SyncMaster 171S/175S/170S/CX175S-AZ/LX175S"
        Horizsync 30-81
        Vertrefresh 56-85
  modeline "1280x1024@75" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
        Gamma 1.0
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "Configured Video Device"
        Monitor "Configured Monitor"
        Defaultdepth 24
        SubSection "Display"
                Depth 24
                Virtual 1280 1024
                Modes "1280x1024@75"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
  screen 0 "Default Screen" 0 0
E...

Here is my attachment of Batchbuffer Dump.

I have switch to vesa driver instead of intel driver and this is enough for me. The intel graphics card on Dell GX260 in not very good at 3D acceleration anyway. I have noticed that lsipci shows that my graphics card has 128 MB of RAM which is not true - It has only 8 MB RAM (Region 0).

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
 Subsystem: Dell Device 0126
 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 e8000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at ff680000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: [d0] Power Management version 1
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: i915
 Kernel modules: i915

I have changed the option Driver in Section Device from intel to vesa, added VideoRam 7680 and disabled all the modules in Section Module . The formula for determing VideoRam is (Video Memory)*1024 - (Region 1 size from lspci).

My xorg.conf looks like this :

Section "Device"
        Identifier "Configured Video Device"
        Boardname "Intel 845"
        Busid "PCI:0:2:0"
        Driver "vesa"
        Screen 0
        Vendorname "Intel"
# Option "AccelMethod" "uxa"
        VideoRam 7680
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
        Vendorname "Samsung"
        Modelname "Samsung SyncMaster 171S/175S/170S/CX175S-AZ/LX175S"
        Horizsync 30-81
        Vertrefresh 56-85
  modeline "1280x1024@75" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
        Gamma 1.0
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "Configured Video Device"
        Monitor "Configured Monitor"
        Defaultdepth 24
        SubSection "Display"
                Depth 24
                Virtual 1280 1024
                Modes "1280x1024@75"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
  screen 0 "Default Screen" 0 0
EndSection
Section "Module"
# Load "glx"
# Load "GLcore"
# Load "dri"
# Load "v4l"
EndSection
Section "ServerFlags"
EndSection

Ugh - happened to me too - after the latest kernel upgrade (don't know if it's related).
I'm running:
adrianp@frost:~$ uname -a
Linux frost 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux
adrianp@frost:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)

The thing is - it seems to be crashing only when xscreensaver is running (I have some GL screensavers) - but it's not always reproductible. I have turned off dpms, but it doesn't help. I can login to the computer via ssh, but commands like xset can't run (start, but remain "hanged").

Here is some output from dmesg:
[176880.528048] INFO: task i915/0:315 blocked for more than 120 seconds.
[176880.528054] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[176880.528058] i915/0 D c08145c0 0 315 2 0x00000000
[176880.528066] f6991f04 00000046 f64e4b8c c08145c0 f64e4df8 c08145c0 dd47cd37 00009fbf
[176880.528079] c08145c0 c08145c0 f64e4df8 c08145c0 dd47bfb4 00009fbf c08145c0 eed81500
[176880.528090] f64e4b60 f697c414 f697c418 ffffffff f6991f30 c056fdd6 f6901920 f697c41c
[176880.528101] Call Trace:
[176880.528114] [<c056fdd6>] __mutex_lock_slowpath+0xc6/0x130
[176880.528120] [<c056fcf0>] mutex_lock+0x20/0x40
[176880.528150] [<f840ac0a>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
[176880.528158] [<c0157a7e>] run_workqueue+0x6e/0x140
[176880.528181] [<f840abe0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
[176880.528188] [<c0157bd8>] worker_thread+0x88/0xe0
[176880.528194] [<c015c280>] ? autoremove_wake_function+0x0/0x40
[176880.528200] [<c0157b50>] ? worker_thread+0x0/0xe0
[176880.528205] [<c015bf8c>] kthread+0x7c/0x90
[176880.528210] [<c015bf10>] ? kthread+0x0/0x90
[176880.528216] [<c0104007>] kernel_thread_helper+0x7/0x10

...and from messages:
Dec 17 14:23:54 localhost kernel: [176880.528058] i915/0 D c08145c0 0 315 2 0x00000000
Dec 17 14:23:54 localhost kernel: [176880.528066] f6991f04 00000046 f64e4b8c c08145c0 f64e4df8 c08145c0 dd47cd37 00009fbf
Dec 17 14:23:54 localhost kernel: [176880.528079] c08145c0 c08145c0 f64e4df8 c08145c0 dd47bfb4 00009fbf c08145c0 eed81500
Dec 17 14:23:54 localhost kernel: [176880.528090] f64e4b60 f697c414 f697c418 ffffffff f6991f30 c056fdd6 f6901920 f697c41c
Dec 17 14:23:54 localhost kernel: [176880.528101] Call Trace:
Dec 17 14:23:54 localhost kernel: [176880.528114] [<c056fdd6>] __mutex_lock_slowpath+0xc6/0x130
Dec 17 14:23:54 localhost kernel: [176880.528120] [<c056fcf0>] mutex_lock+0x20/0x40
Dec 17 14:23:54 localhost kernel: [176880.528150] [<f840ac0a>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
Dec 17 14:23:54 localhost kernel: [176880.528158] [<c0157a7e>] run_workqueue+0x6e/0x140
Dec 17 14:23:54 localhost kernel: [176880.528181] [<f840abe0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
Dec 17 14:23:54 localhost kernel: [176880.528188] [<c0157bd8>] worker_thread+0x88/0xe0
Dec 17 14:23:54 localhost kernel: [176880.528194] [<c015c280>] ? autoremove_wake_function+0x0/0x40
Dec 17 14:23:54 localhost kernel: [176880.528200] [<c0157b50>] ? worker_thread+0x0/0xe0
Dec 17 14:23:...

Update:
My system is now stable after uninstalling xscreensaver and using xlock instead (no more 3d graphics). I will leave it on like this for a while and afterwards I will enable compositing in my window manager (Xfce) and see if it becomes unstable again. Will keep you posted.

This also just happened to me. The display is blank (the power led is blinking to signify that DPMS is off), the mouse and keyboard do not respond (the num lock led is stuck). Syslog has:

Dec 21 15:31:32 dov kernel: [81840.640063] INFO: task i915/0:360 blocked for more than 120 seconds.
Dec 21 15:31:32 dov kernel: [81840.640067] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 21 15:31:32 dov kernel: [81840.640070] i915/0 D 0000000000000000 0 360 2 0x00000000
Dec 21 15:31:32 dov kernel: [81840.640075] ffff880122dedd70 0000000000000046 0000000000000000 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640079] ffff8801234e47c0 0000000000015880 0000000000015880 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640083] 0000000000015880 ffff8801234e47c0 0000000000015880 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640087] Call Trace:
Dec 21 15:31:32 dov kernel: [81840.640096] [<ffffffff81528847>] __mutex_lock_slowpath+0xd7/0x160
Dec 21 15:31:32 dov kernel: [81840.640100] [<ffffffff81528746>] mutex_lock+0x26/0x50
Dec 21 15:31:32 dov kernel: [81840.640120] [<ffffffffa00858d8>] i915_gem_retire_work_handler+0x38/0x90 [i915]
Dec 21 15:31:32 dov kernel: [81840.640130] [<ffffffffa00858a0>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
Dec 21 15:31:32 dov kernel: [81840.640135] [<ffffffff810737f5>] run_workqueue+0x95/0x170
Dec 21 15:31:32 dov kernel: [81840.640139] [<ffffffff81073974>] worker_thread+0xa4/0x120
Dec 21 15:31:32 dov kernel: [81840.640142] [<ffffffff81078b20>] ? autoremove_wake_function+0x0/0x40
Dec 21 15:31:32 dov kernel: [81840.640146] [<ffffffff810738d0>] ? worker_thread+0x0/0x120
Dec 21 15:31:32 dov kernel: [81840.640149] [<ffffffff81078736>] kthread+0xa6/0xb0
Dec 21 15:31:32 dov kernel: [81840.640153] [<ffffffff810130ea>] child_rip+0xa/0x20
Dec 21 15:31:32 dov kernel: [81840.640156] [<ffffffff81078690>] ? kthread+0x0/0xb0
Dec 21 15:31:32 dov kernel: [81840.640159] [<ffffffff810130e0>] ? child_rip+0x0/0x20
Dec 21 15:31:32 dov kernel: [81840.640171] INFO: task Xorg:1299 blocked for more than 120 seconds.
Dec 21 15:31:32 dov kernel: [81840.640173] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec 21 15:31:32 dov kernel: [81840.640175] Xorg D 0000000000000000 0 1299 1253 0x00400000
Dec 21 15:31:32 dov kernel: [81840.640179] ffff8800ce5ebcb8 0000000000000086 ffff8800ce5ebc58 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640183] ffff8800ce5383b0 0000000000015880 0000000000015880 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640187] 0000000000015880 ffff8800ce5383b0 0000000000015880 0000000000015880
Dec 21 15:31:32 dov kernel: [81840.640196] Call Trace:
Dec 21 15:31:32 dov kernel: [81840.640199] [<ffffffff81528847>] __mutex_lock_slowpath+0xd7/0x160
Dec 21 15:31:32 dov kernel: [81840.640201] [<ffffffff81528739>] ? mutex_lock+0x19/0x50
Dec 21 15:31:32 dov kernel: [81840.640204] [<ffffffff81528739>] ? mutex_lock+0x19/0x50
Dec 21 15:31:32 dov kernel: [81840.640206] [<ffffffff81528746>] mutex_lock+0x26/0x50
Dec 21 15:31:32 dov kernel: [81840.640214] [<ffffffffa0085bc6>] i915_gem_throttle_ioctl+0x36/0x90 [i915]
De...

Also seem to have same issue - Intel Atom 330 dual core with 945 chipset. identical messages in syslog

uname -a is
Linux Mythbox-1 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux

syslog has
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203871] Call Trace:
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203891] [<ffffffff815286a7>] __mutex_lock_slowpath+0xd7/0x160
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203901] [<ffffffff815285a6>] mutex_lock+0x26/0x50
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203955] [<ffffffffa00618d8>] i915_gem_retire_work_handler+0x38/0x90 [i915]
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203984] [<ffffffffa00618a0>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.203996] [<ffffffff810737a5>] run_workqueue+0x95/0x170
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204006] [<ffffffff81073924>] worker_thread+0xa4/0x120
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204015] [<ffffffff81078b30>] ? autoremove_wake_function+0x0/0x40
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204024] [<ffffffff81073880>] ? worker_thread+0x0/0x120
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204033] [<ffffffff81078746>] kthread+0xa6/0xb0
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204042] [<ffffffff810130ea>] child_rip+0xa/0x20
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204051] [<ffffffff810786a0>] ? kthread+0x0/0xb0
Dec 26 21:13:06 Mythbox-1 kernel: [ 6001.204058] [<ffffffff810130e0>] ? child_rip+0x0/0x20
Dec 26 21:15:06 Mythbox-1 kernel: [ 6121.202005] INFO: task i915/0:267 blocked for more than 120 seconds.

repeated.

Interestingly this machine sometimes hangs on startup at the point where it would switch into the X server, I was assume it had all hung but looking in syslog it seems to be just the screen as other startup processes are still running (at least until I pull the plug to restart it!)

David

This comment goes to bug 400934, bug 451518, bug 475429, bug 500686,
bug 501875, bug 342675, bug 4611163 and 493111.

We have had several reports of freezes (GPU hangs) on i945 chipsets
(945G, 945GM and 945GME, all of which uses the GMA950 graphics core)
in Karmic. I would like to get some testing going so that we may
identify the cause and give upstream all the information they need
(and possibly some they do not need) so that they can fix this before
Lucid is out. I have set up a wiki page to coordinate the effort:
https://wiki.ubuntu.com/X/Lucidi945Freezes . There is a list of test
that I think will be useful in order to isolate where the problem is
and a table where you can fill in your test results. If we're lucky
there is only one underlying problem, and we will probably get
consistent test results. Otherwise, different test results may group
the problems in different categories.

I realize that doing all the tests can be quite time consuming (it
calls for tests on both Karmic and Lucid), and if you are only able to
do some of the tests it would be nice if you could fill in those cells
in the test result table.

My initial guess is that the bug is in mesa, since it seems to be
related to 3D operations. It would be nice if we could also get some
testing of different mesa versions, but I'm not aware of any that are
pre-built yet.

My i915 laptop is out of commission, but I do get freezes with an 82Q35 Express IGC, and annoying blanking with GM965 IGC. Are any of these relevant to this?

Update - I have tried with kernel 2.6.31-16 and parameter acpi=off and I was unable to reproduce the bug for 3 days. I would say acpi fixes the issue.
Now, I have switched to kernel 2.6.31-17 and I will test again without acpi=off (the default way) and I will let you know if I have more instabilities...

I've been running kernel 2.6.31-17 for about 5 days now, and no more freeze (with acpi=on). Did the problem get fixed, or is it a coincidence?

I have uploaded an older version of mesa to my "old" PPA: https://launchpad.net/~gomyhr/+archive/old/+packages . By testing this, we can find out if this is caused by a bug in mesa which is introduced after version 7.5.

Unfortunately, installing it is probably not as easy as just adding the PPA to /etc/apt/sources and do `sudo apt-get update; sudo apt-get upgrade`, since the version in the PPA is older than then one in karmic and I didn't do any PPA magic to make it want to upgrade anyway. The easiest way I can think about is probably to download all the deb-files for your architecture (*i386.deb) to an empty folder and do a `dpkg -i -O *.deb` in that folder. That will install only the packages that already have an installed version on your system.

If Karmic freezes with this version, I can try to go all the way back to the Jaunty version.

PS: I don't have a Karmic installation (I only have Jaunty and Lucid) so I haven't had a chance to test that the packages even work.

PPS: If anyone can confirm Adrian's finding that 2.6.31-17 fixes the issue, that would be great!

I still have problems with 2.6.31-17. So I can't confirm Adrian's finding.

Jan 8 19:22:53 sat-ubuntu kernel: [ 0.000000] Linux version 2.6.31-17-generic (buildd@palmer) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 (Ubuntu 2.6.31-17.54-generic)
Jan 8 19:22:53 sat-ubuntu kernel: [ 0.000000] Kernel command line: root=UUID=32f0f14c-3fe3-47b2-baf7-6a7af816884d ro quiet splash
Jan 8 20:44:32 sat-ubuntu kernel: [ 4920.860054] INFO: task i915/0:274 blocked for more than 120 seconds.
Jan 8 20:46:32 sat-ubuntu kernel: [ 5040.860057] INFO: task i915/0:274 blocked for more than 120 seconds.

Maybe my own video card model is no longer affected by this bug:
adrianp@frost:~$ grep "blocked for more" /var/log/kern.log
adrianp@frost:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
adrianp@frost:~$ uname -a
Linux frost 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux
adrianp@frost:~$

Adrian, we treat bugs on different chipsets as different bugs unless proven otherwise. If I remember correctly, the Q35 is similar to the 965G, but it is quite different from 945G and in the vast majority of the cases bugs on one chipset does not translate to another (even though they may have the exact same symptoms). I missed the fact that you had another chipset when I wrote the comment above.

On other bug reports (bug 450853 and bug 445056), people have reported that downgrading mesa to the version in my PPA stops the freezes. It would be nice if you (Steen) could test this as well.

I have downgraded mesa, but this still freeze.

sat@sat-ubuntu:~$ dpkg -l | grep mesa
ii libgl1-mesa-dri 7.5-1ubuntu1 A free implementation of the OpenGL API -- D
ii libgl1-mesa-glx 7.5-1ubuntu1 A free implementation of the OpenGL API -- G
ii libglu1-mesa 7.5-1ubuntu1 The OpenGL utility library (GLU)
ii mesa-utils 7.5-1ubuntu1 Miscellaneous Mesa GL utilities

I too am affected by this bug. When I searched previously I couldn't find related bugs so I opened a new one. All of my logs are attached to bug Bug #509410 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/509410?comments=all
I'll try the downgrade of mesa as well. Presently I am running : dpkg -l | grep mesa
ii libgl1-mesa-dri 7.6.0-1ubuntu4 A free implementation of the OpenGL API -- D
ii libgl1-mesa-glx 7.6.0-1ubuntu4 A free implementation of the OpenGL API -- G
ii libglu1-mesa 7.6.0-1ubuntu4 The OpenGL utility library (GLU)
ii mesa-utils 7.6.0-1ubuntu4 Miscellaneous Mesa GL utilities

I performed the downgrade. It didn't work well at all. On my user id it seemed ok, however, on my wife's user id the screen would not refresh in certain areas - like applications windows, switch user, main desktop when applications would launch. Basically it was unusable so I reverted back to the repo versions...

Hi All.

I just came home to find my ECS 945GCD-M(1.0) 945GC ATOM 330 system hung up after approx 7 days uptime.
This is an atom 330 system with Intel 945 video. Was running Xscreensaver too when this likely occurred. Havent seen any Xscreensaver issues in previous 2-3 weeks of use.

System did not respond to any keyboard or mouse; numlock stuck, but i could still log in via ssh.

I'll attach my system info + syslog. Hope this helps.

I am uninstalling xscreensaver to see if it happens again.

We're also seeing this problem on a Dell Inspiron 1100, running Karmic with intel video driver version 2.9.1~git-0ubuntu0tormod from xorg-edgers and a 2.6.31-20 kernel. There are no 3D effects enabled (compiz has been completely removed).

The X server freezes, although the mouse still moves, but the system requires a full reboot.

I am happy to report that issues with Dell Optiplex GX260 and Intel Video Card has gone - all is working OK. I have upgraded to latest kernel version and my xorg.conf is the same as it was on 2009-11-19.

"I have upgraded to latest kernel version and my xorg.conf is the same as it was on 2009-11-19." - sorry that is not true - I am using intel video driver.

I'm seeing this problem too, since I moved from Kubuntu 8.04 to 9.10. HW: Fujitsu Siemens Lifebook E4010D and a intel 955 GPU, all the latest patches for xorg and kde loaded, also from PPA. Kernel 2.6.31-20, but same problems from on -14. KDE 4.4.1, xserver-xorg-video-intel - 2:2.9.01-1. Basically 3 types of graphics errors with different severity and effects:

the little tabs or hints with detailed info from the task bar don't always show up at the right place, and don't always get removed right. A bit annoying, but not too serious. One way to reproduce: left click on the network manager icon after bootup, the info shows up in the top left corner of the screen. Right click on the icon, info directly next to it, left click from from on then on the same. Every other effects alike are random, couldn't find a way to reproduce.

video from a webcam (Logitech C300) on skype or cheese never worked for me on 9.10. No streaming of any video data in anyone of the 2 apps, but mplayer worked fine! I almost gave up on this, but the latest xorg intel driver update around the frame buffer alignment bug made it happen, and everything perfectly works now, thx!

the third bug is about the one mentioned everywhere above, a complete lockup of the screen, randomly, maybe 2 days in a row fine, then 3 times a day. Always in conjunction with some heavier graphics activities, like opening some new windows, selecting a bigger text etc., and only a complete shutdown helps. I'm still not that deep into all the tools, but after such a lockup we still can get onto the laptop with ssh, and I think it was ksysguard showing the "i915_gem_retire_work_handler" status for the i915 driver. This bug is extremely annoying, and I've lost quite some work due to it already..

OK, a few days ago I found just by coincidence the 100% killer for my system, it's Google Earth, the latest downloadable version. Just start, and within a few seconds my laptop graphics is dead. Perfectly works on another system with all the same os and graphics versions as on my laptop, but with a ATI radeon GPU, could verify this today, so it's not like I thought a bug in Google Earth, but apparently in the graphics driver.

this other PC also doesn't experience the lockups, and never did so. But it had this "hints location" problem too, which disappeared since we've changed in the BIOS (!!!) the default settings for the graphics card from PCI to PCIe, which it really is.

sorry if I messed up a little bit here and maybe put too many things into this thread, but I think most or all of the bugs are clearly related and come down just to the intel i915 xorg driver.

could anybody with more linux knowledge than me please verify the Google Earth i915 killer, and publish the appropriate info, or tell me what exactly to do in order to provide the necessary info.

TIA

OK, I've to recall one of the statements I made above, apparently the BIOS change for the ATI radeon GPU from PCI to PCIe didn't fix the issue of the misplaced litte hints / status windows for that PC, only seems they show up less frequently..

I am also affected; I'm running 2.6.31-20 in Ubuntu 9.10.

Just happened to me after 137 days of uptime on my Acer Aspire 5570-2607 laptop, when trying to open Totem to play an audio file (probably the visualization triggered it, compiz was enabled too). Kernel is 2.6.31-15 in Ubuntu 9.10, video is:

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Here as well: ThinkPad Edge, Ubuntu 10.04 LTS, 2.6.32-22-generic. Display freezes, but otherwise the machine is responsive (logs continue, ssh works etc).

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12)

lspci -s 00:02.0 -n
00:02.0 0300: 8086:0046 (rev 12)

kernel: [ 2936.275191] INFO: task i915:779 blocked for more than 120 seconds.
kernel: [ 2936.275198] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: [ 2936.275203] i915 D 00000000ffffffff 0 779 2 0x00000000
kernel: [ 2936.275213] ffff880146de7d40 0000000000000046 0000000000015bc0 0000000000015bc0
kernel: [ 2936.275221] ffff8801486a9ab0 ffff880146de7fd8 0000000000015bc0 ffff8801486a96f0
kernel: [ 2936.275229] 0000000000015bc0 ffff880146de7fd8 0000000000015bc0 ffff8801486a9ab0
kernel: [ 2936.275237] Call Trace:
kernel: [ 2936.275254] [<ffffffff8153f897>] __mutex_lock_slowpath+0xe7/0x170
kernel: [ 2936.275265] [<ffffffff81058620>] ? finish_task_switch+0x50/0xe0
kernel: [ 2936.275272] [<ffffffff8153f78b>] mutex_lock+0x2b/0x50
kernel: [ 2936.275305] [<ffffffffa015437d>] i915_gem_retire_work_handler+0x3d/0xa0 [i915]
kernel: [ 2936.275327] [<ffffffffa0154340>] ? i915_gem_retire_work_handler+0x0/0xa0 [i915]
kernel: [ 2936.275337] [<ffffffff81080777>] run_workqueue+0xc7/0x1a0
kernel: [ 2936.275344] [<ffffffff810808f3>] worker_thread+0xa3/0x110
kernel: [ 2936.275351] [<ffffffff81085320>] ? autoremove_wake_function+0x0/0x40
kernel: [ 2936.275358] [<ffffffff81080850>] ? worker_thread+0x0/0x110
kernel: [ 2936.275364] [<ffffffff81084fa6>] kthread+0x96/0xa0
kernel: [ 2936.275372] [<ffffffff810141ea>] child_rip+0xa/0x20
kernel: [ 2936.275378] [<ffffffff81084f10>] ? kthread+0x0/0xa0
kernel: [ 2936.275383] [<ffffffff810141e0>] ? child_rip+0x0/0x20
kernel: [ 2936.275401] INFO: task Xorg:1148 blocked for more than 120 seconds.
kernel: [ 2936.275404] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: [ 2936.275408] Xorg D 0000000000000000 0 1148 1093 0x00400004
kernel: [ 2936.275416] ffff880144b0dc98 0000000000000086 0000000000015bc0 0000000000015bc0
kernel: [ 2936.275423] ffff8801449a1ab0 ffff880144b0dfd8 0000000000015bc0 ffff8801449a16f0
kernel: [ 2936.275431] 0000000000015bc0 ffff880144b0dfd8 0000000000015bc0 ffff8801449a1ab0
kernel: [ 2936.275438] Call Trace:
kernel: [ 2936.275446] [<ffffffff8153f897>] __mutex_lock_slowpath+0xe7/0x170
kernel: [ 2936.275453] [<ffffffff8153f78b>] mutex_lock+0x2b/0x50
kernel: [ 2936.275473] [<ffffffffa0155be9>] i915_gem_set_domain_ioctl+0xb9/0x160 [i915]
kernel: [ 2936.275496] [<ffffffffa0096e2a>] drm_ioctl+0x27a/0x480 [drm]
kernel: [ 2936.275517] [<ffffffffa0155b30>] ? i915_gem_set_domain_ioctl+0x0/0x160 [i915]
kernel: [ 2936.275525] [<ffffffff81085320>] ? autoremove_wake_function+0x0/0x40
kernel: [ 2936.275534] [<ffffffff81152a92>] vfs_ioctl+0x22/0xa0
kernel: [ 2936.275540] [<ffffffff81152d41>] do_vfs_ioctl+0x81/0x380
kernel: [ 2936.275547] [<ffffffff811431df>] ? vfs_read+0x12f/0x1a0
kernel: [ 2936.275553] [<ffffffff811530c1>] sys_ioctl+0x81/0xa0
kernel: [ 2936.275561] ...

Similar issue to Nicholas above, running Lucid X64.
I have a slightly different graphics card looking at the output from lspci:

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

Freezes up happening intermittently with no apparent pattern, at first I suspect could be down to a higher load as it was happening with the GLxxxx screensavers but has since occurred whilst using FIrefox and even happened last night whilst testing the HDMI out on my friends telly and displaying some photos (I was very impressed how that worked so smoothly - always been a bit weary of ubuntu+multiple screens!)

FWIW: Disabling compiz is a successful workaround for my sister's ThinkPad Edge... not a single freeze since.

System | Preferences | Appearance ... Visual Effects | None

Am seeing this on a Dell Optiplex 980 under karmic:

00:02.0 VGA compatible controller: Intel Corporation Clarkdale Integrated Graphics Controller (rev 02)

[ 838.848500] INFO: task i915/3:428 blocked for more than 120 seconds.
[ 838.848506] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 838.848510] i915/3 D ffffffff815eb720 0 428 2 0x00000000
[ 838.848517] ffff88011046bda0 0000000000000046 0000000000000000 00000000ffffffff
[ 838.848524] ffff88011046bd30 ffffffff8104af6b ffff88010dce2d98 000000010000a007
[ 838.848529] ffff88010dce3110 000000000000f6e8 0000000000015580 ffff88010dce3110
[ 838.848535] Call Trace:
[ 838.848547] [<ffffffff8104af6b>] ? dequeue_entity+0x1b/0x240
[ 838.848555] [<ffffffff815d3fd7>] __mutex_lock_slowpath+0xd7/0x160
[ 838.848560] [<ffffffff815d3ed6>] mutex_lock+0x26/0x50
[ 838.848589] [<ffffffffa00b8398>] i915_gem_retire_work_handler+0x38/0x90 [i915]
[ 838.848608] [<ffffffffa00b8360>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
[ 838.848615] [<ffffffff8106ca55>] worker_thread+0x165/0x290
[ 838.848621] [<ffffffff81071cb0>] ? autoremove_wake_function+0x0/0x40
[ 838.848626] [<ffffffff8106c8f0>] ? worker_thread+0x0/0x290
[ 838.848631] [<ffffffff810718c6>] kthread+0xa6/0xb0
[ 838.848637] [<ffffffff81012f8a>] child_rip+0xa/0x20
[ 838.848642] [<ffffffff81071820>] ? kthread+0x0/0xb0
[ 838.848646] [<ffffffff81012f80>] ? child_rip+0x0/0x20

May be related: saw several nfs timeout errors in the log at around the same time.

me too: ubuntu 10.04 - 2.6.32-23

[433560.791484] i915 D ffff8800b8f93028 0 742 2 0x00000000
[433560.791489] ffff8800b6f11d20 0000000000000046 0000000000015bc0 0000000000015bc0
[433560.791494] ffff8800b942df80 ffff8800b6f11fd8 0000000000015bc0 ffff8800b942dbc0
[433560.791498] 0000000000015bc0 ffff8800b6f11fd8 0000000000015bc0 ffff8800b942df80
[433560.791502] Call Trace:
[433560.791512] [<ffffffff81542077>] __mutex_lock_slowpath+0xe7/0x170
[433560.791516] [<ffffffff81541f6b>] mutex_lock+0x2b/0x50
[433560.791543] [<ffffffffa01b1220>] intel_idle_update+0x60/0x1e0 [i915]
[433560.791555] [<ffffffffa01b11c0>] ? intel_idle_update+0x0/0x1e0 [i915]
[433560.791560] [<ffffffff81080867>] run_workqueue+0xc7/0x1a0
[433560.791564] [<ffffffff810809e3>] worker_thread+0xa3/0x110
[433560.791568] [<ffffffff81085430>] ? autoremove_wake_function+0x0/0x40
[433560.791571] [<ffffffff81080940>] ? worker_thread+0x0/0x110
[433560.791574] [<ffffffff810850b6>] kthread+0x96/0xa0
[433560.791578] [<ffffffff810141ea>] child_rip+0xa/0x20
[433560.791582] [<ffffffff81085020>] ? kthread+0x0/0xa0
[433560.791584] [<ffffffff810141e0>] ? child_rip+0x0/0x20
[433560.791600] INFO: task Xorg:1206 blocked for more than 120 seconds.
[433560.791602] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[433560.791604] Xorg D 00000000ffffc900 0 1206 1144 0x00400004
[433560.791608] ffff8800b8a4fca8 0000000000000086 0000000000015bc0 0000000000015bc0
[433560.791612] ffff8800b80003c0 ffff8800b8a4ffd8 0000000000015bc0 ffff8800b8000000
[433560.791616] 0000000000015bc0 ffff8800b8a4ffd8 0000000000015bc0 ffff8800b80003c0
[433560.791620] Call Trace:
[433560.791624] [<ffffffff81542077>] __mutex_lock_slowpath+0xe7/0x170
[433560.791627] [<ffffffff81541f6b>] mutex_lock+0x2b/0x50
[433560.791638] [<ffffffffa019e88b>] i915_gem_throttle_ioctl+0x3b/0x90 [i915]
[433560.791653] [<ffffffffa0101e5c>] drm_ioctl+0x27c/0x480 [drm]
[433560.791663] [<ffffffffa019e850>] ? i915_gem_throttle_ioctl+0x0/0x90 [i915]
[433560.791668] [<ffffffff810397a9>] ? default_spin_lock_flags+0x9/0x10
[433560.791672] [<ffffffff8154348f>] ? _spin_lock_irqsave+0x2f/0x40
[433560.791677] [<ffffffff81153cd2>] vfs_ioctl+0x22/0xa0
[433560.791682] [<ffffffff81252326>] ? security_file_permission+0x16/0x20
[433560.791685] [<ffffffff81153f81>] do_vfs_ioctl+0x81/0x380
[433560.791688] [<ffffffff81154301>] sys_ioctl+0x81/0xa0
[433560.791692] [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b

00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
 Subsystem: ASRock Incorporation Device 2772
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at fe980000 (32-bit, non-prefetchable) [size=512K]
 I/O ports at cc00 [size=8]
 Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Memory at fe940000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
 Capabilities: [d0] Power Management version 2
 Kernel driver in use: i915
 Kernel modules: i915

It just happened to me, running 2.6.32-24-generic on Lucid. I really don't know how to reproduce it, I wasn't doing anything fancy. As other said, the system was completely unresponsive, but it still replied to pings from another machine.

Upgraded from 9.04 --> 9.10 karmic GPU freezes same as above, with these messages looping in /var/log/messages every two minutes:

May 9 19:57:58 shire kernel: [17640.452040] i915/0 D c081b5c0 0 274 2 0x00000000
May 9 19:57:58 shire kernel: [17640.452047] f6af9f04 00000046 f6b4d81c c081b5c0 f6b4da88 c081b5c0 8513c6a8 00000fd8
May 9 19:57:58 shire kernel: [17640.452055] c081b5c0 c081b5c0 f6b4da88 c081b5c0 8513bf06 00000fd8 c081b5c0 f5e8b500
May 9 19:57:58 shire kernel: [17640.452062] f6b4d7f0 f68fb814 f68fb818 ffffffff f6af9f30 c0574476 c074ee80 f68fb81c
May 9 19:57:58 shire kernel: [17640.452070] Call Trace:
May 9 19:57:58 shire kernel: [17640.452082] [<c0574476>] __mutex_lock_slowpath+0xc6/0x130
May 9 19:57:58 shire kernel: [17640.452087] [<c0574390>] mutex_lock+0x20/0x40
May 9 19:57:58 shire kernel: [17640.452119] [<f814bb3a>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
May 9 19:57:58 shire kernel: [17640.452127] [<c0157a2e>] run_workqueue+0x6e/0x140
May 9 19:57:58 shire kernel: [17640.452146] [<f814bb10>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
May 9 19:57:58 shire kernel: [17640.452152] [<c0157b88>] worker_thread+0x88/0xe0
May 9 19:57:58 shire kernel: [17640.452157] [<c015c1d0>] ? autoremove_wake_function+0x0/0x40
May 9 19:57:58 shire kernel: [17640.452162] [<c0157b00>] ? worker_thread+0x0/0xe0
May 9 19:57:58 shire kernel: [17640.452166] [<c015bedc>] kthread+0x7c/0x90
May 9 19:57:58 shire kernel: [17640.452170] [<c015be60>] ? kthread+0x0/0x90
May 9 19:57:58 shire kernel: [17640.452175] [<c0104047>] kernel_thread_helper+0x7/0x10

The keyboard, mouse, and screen are completely unresponsive; however, I am able to ssh into the box, look at the logs, restart the system &etc.

This only seems to happen with the affects running compiz.real and if the gnome-screensaver is running for a while. I have disabled the screen-saver but left compiz running; will let you know.

thanks

This may be related to DVMT; Intel's Dynamic Video Memory Technology. ... its supposed to work with Microsoft's proprietary driver to dynamically allocate video memory resources (up to 128 M) for 2D - 3D performance and then return the memory resource to the OS when finished. My machine defaults to 8M preallocated, 0M fixed, and 120M DVMT...

I changed the default settings to 8M preallocated 120M fixed and 0M DVMT... and the freeze is gone... even with compiz.real running w/ screensaver. I left the silly thing running all night... no problems.

Perhaps the i915 driver isn't working well with DVMT ; Intel integrated graphics chipset 915 945 ?

regards,
m harris

Missed interrupts long ago fixed.