Created attachment 65356 [details] 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
This log really is from 0.2.906. Can you please provide the 0.3.0 log ?
From reading the bug report from Arch linux I get the impression you attempting to run with the new drm KMS driver. Is this true? Can you attach your dmesg log.
Created attachment 66429 [details] dmesg
Apparently no Xorg log is actually created with 0.3.0 upon "startx" and then subsequent system freeze. Attached dmesg, but I'm not sure how useful it will be since I can't "startx" and there is no mention of drm.
Please build the latest openchrome from git master and try to reproduce this problem.
Please also follow following instruction: http://www.x.org/wiki/Development/Documentation/ServerDebugging#The_basics 1. Run X.org 2. Go over to your second machine and ssh into the first one. su root 3. gdb /usr/bin/Xorg $(pidof X) 4. try to run "bt"
I can duplicate the issue with current git-master (803c882) using libdrm 2.4.39 and libxvmc 1.0.7. As soon as startx is issued the machine becomes unresponsive including the ssh server and any existing sessions.
Try to disable hotplugging, by following instruction: https://wiki.archlinux.org/index.php/Xorg_input_hotplugging#Disabling_input_hot-plugging
Does this problem still exist?
Created attachment 70833 [details] [review] line compare fix This bugs very familiar to the one we saw in the DRM KMS driver. Can you try the attached patch to see if it works.
The problem still exists. I tried disable hotplugging and the attached patch, but I won't rule out user error/ignorance. However, this laptop has encountered another video related issue beginning with kernel 3.5.4 (and still present as of 3.6.8). The laptop screen becomes garbled during boot but using external monitor still works. This was one of the least Linux friendly machines I've used, and at this point I'm ready to send it away. Would it be useful as a development machine? I can mail it to an interested developer.
I hate to see you lose your hardware. How about you email me privately and we can discuss me getting access to your device and fixing it.
did you resolve problem? may be I have same bug bug: 58409
Not yet. I'm attempting to get my hands on some of this hardware to reproduce the problem.
Hardware is expected around Janurary 14th. Once I get it I will work on the problem.
*** Bug 58409 has been marked as a duplicate of this bug. ***
This should be fixed in git master, can you please give it a try and report back ?
Sorry for such long answer I have not this hardware anymore. When I will get it again, I will test bug
I can confirm this bug is fixed in git-mainline-master. I was affected by this bug since 0.3.x came out. Now I built it from git and it works again. Thanks.
Which git commit fixed this? It would be useful for downstream.
(In reply to comment #20) > Which git commit fixed this? It would be useful for downstream. http://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=76515c8a369346d76864e55610a6a747d9b152d8
Since it works we can close this ticket.
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.