Comment 1 for bug 1165232

Created attachment 65356
Xorg log

Upgrading from 0.2.906 to 0.3.0 causes the system to become unresponsive (including SSH sessions). Reverting back to 0.2.906 works as expected.

Watching Xorg.0.log and dmesg during "startx" on remote via SSH with tail did not create any output but I will provide what I can.

$ lspci | grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)

$ dmesg | grep -e agp -e drm
[ 5.702201] Linux agpgart interface v0.103
[ 5.708516] agpgart: Detected VIA P4M900 chipset
[ 5.717737] agpgart-via 0000:00:00.0: AGP aperture is 128M @ 0xc0000000
[ 876.025413] [drm] Initialized drm 1.1.0 20060810

$ grep openchrome /var/log/Xorg.0.log
[ 875.678] (II) LoadModule: "openchrome"
[ 875.703] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
[ 875.703] (II) Module openchrome: vendor="http://openchrome.org/"
[ 875.707] (!!) For support, please refer to http://www.openchrome.org/.
[ 875.707] (!!) (openchrome 0.2.906 release)
$ grep rendering /var/log/Xorg.0.log
[ 876.225] (II) CHROME(0): direct rendering disabled

$ grep "^(EE)" /var/log/Xorg.0.log

$ grep "^(WW)" /var/log/Xorg.0.log

$ uname -a
Linux sasquatch 3.4.7-1-ARCH #1 SMP PREEMPT Sun Jul 29 20:05:01 UTC 2012 i686 GNU/Linux

Attached is the complete Xorg.0.log. Although it mentions 0.2.906 I was using 0.3.0 at the time of the log creation (unless somehow the log is still from 0.2.906).

Please let me know if I am missing anything obvious and I will provide it. I have no .xsession-errors file.

Originally reported to Arch Linux:
https://bugs.archlinux.org/task/30868