Intrepid Compiz hangs on login for i945GM video cards

Hm, on second look this is not as trivial as it seems. The 945 is very popular, blacklisting it will disable compiz on many machines where it is running fine. I just happen to have the very same one:

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

The first one is 8086:27a2, the second one 8086:27a6. compiz has worked fine here for months..

Unsubscribing ubuntu-sru for now, since this seems to be a much harder bug which doesn't have a readily available patch for intrepid.

Martin Pitt wrote:
> The first one is 8086:27a2, the second one 8086:27a6. compiz has worked
> fine here for months..

My chips have the same IDs. Any idea why your system would work fine
and mine would hang?

Thomas

i'm also on the i945gm and compiz works fine here:

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)

If I use gnome without compiz and then run /usr/bin/compiz from a
terminal the screen flashes and appears again sans any window borders.
Immediately after this, the screen goes to black with thin purple lines
before gdm catches the crash and restarts, dropping me at the login prompt.

Any tips on debugging this since it seems to work for others?

Everything worked just fine in Hardy.

This also happens on my Vaio TZ190N with me running 8.10.

Attaching output of lspci -vvnn

With graphics cards, there are two pci id's. From steve's lcpid -vvnn output:

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Sony Corporation Device [104d:900e]

27a2 corresponds to a class of 945 chips that Intel puts out (8086 == Intel). 900e corresponds to a Sony (104d==Sony) integration of this chip onto a particular motherboard.

This is why we always ask for 'lspci -vvnn' output, rather than just lspci. :-)

As to the root problem of the hang - currently there is not sufficient information in this bug report to troubleshoot the problem on the X side. Hangs can be very hard to debug. If the other reporters having this problem are also seeing it on 8086:27a2/104d:900e then it may make sense to blacklist them, but otherwise it would be better to get a real fix in the -intel driver. To do that, please file a new bug via `ubuntu-bug -p xserver-xorg-video-intel`. We would need a more detailed description of the problem, how to reproduce it, whether it occurs during boot or after using particular software, whether disabling compiz makes it go away or just reduces the frequency, and any other information that could help pinpoint the issue.

Mine is packaged by Fujitsu-Siemens:

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Fujitsu Limited. Device [10cf:137a]
 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 f0200000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at 1800 [size=8]
 Region 2: Memory at e0000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at f0300000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: <access denied>
 Kernel modules: intelfb

This also occurs on my Vaio VGN-C240E.

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
 Subsystem: Sony Corporation Device [104d:820f]
 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 d0100000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at 1800 [size=8]
 Region 2: Memory at b0000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at d0200000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: <access denied>
 Kernel modules: intelfb

I haven't seen this noted in any of the other threads, but on my computer, it seems that compiz works fine if I boot in recovery mode and choose the normal boot option, so I don't have to remove compiz. The hang occurs if I do not choose to boot into recovery mode.

Bryce,

Steve Alexander has been having the same issue and has uploaded the necessary diagnostic files (as you requested) to a new bug via apport/ubuntu-bug.

https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/315422

I also just upgraded this laptop to the in-development version of 9.04. I see exactly the same issue. So, it's still a problem with 9.04.

bug 315422 is a dupe of 146859. Perhaps this bug is as well.

Thomas, please attach your /var/log/Xorg.0.log, /var/log/Xorg.0.log, /etc/X11/xorg.conf, and the output of 'lspci -vvnn'. Those are always required when reporting X bugs. Also attach the output of 'xrandr --verbose'.

If in your Xorg.0.log you have an error "Cannot support DRI with frame buffer width > 2048." it means you just have a dupe of 146859 too.

I removed the "virtual" section from my xorg.conf, and restarted X, and now I can use desktop effects.

Awesome.

I have no idea how the "virtual" section with the large screen size got in there. Maybe the "use a projector as well as your laptop screen" applet?

Steve Alexander [2009-02-10 20:06 -0000]:
> I have no idea how the "virtual" section with the large screen size got
> in there. Maybe the "use a projector as well as your laptop screen"
> applet?

It's added by the screen resolution configuration if you want to use
screens side-by-side, not mirroring.