Hi, I use git 20070901 version and when CTRL+ALT+F1 switching to console or ALT+F& back to xorg, usually with this version I experience computer freeze. This can be tested very easy. 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) kernel vanilla 2.6.22.5, distro Debian testing I have never seen this error with old version (i810)
with git 20070917 it works better, but still experiencing this crash in second or third switch X,console,X, console and so on...
Hi Eric, any news about this problem?? It is really annoying! :( Thanks a lot for reply
If I thought your bug was fixed, I would have closed it. If you wonder if it's been fixed without someone noticing it to close it, keep testing master.
There were some fixes for VT switch crashes for 8xx chips that went into master not long ago. Can you test again and see if your problem still exists?
Hi, My version is pretty new: drwxr-sr-x 6 root src 4096 2007-10-26 18:45 xf86-video-intel
Hi, my version is pretty new: cijoml@notas:~/work/lingea$ ls -la /usr/src| grep xf86-video-intel drwxr-sr-x 6 root src 4096 2007-10-26 18:45 xf86-video-intel
Created attachment 12305 [details] [review] Fix / workaround which helped many Ubuntu users seeing this bug This might not be the "right" thing to do, but it seems that people hitting the bug on VT-switching were seeing the crash when programming the PIPE[AB]CONF registers. It looked like the registers might be keyed to some hardware state-machine dependant on the DPLL clock to sync, and locks the chip up if this isn't running. More specifically, it seems to lock it up if you try to enable the PIPE whilst the corresponding DPLL is in VGA mode. Perhaps the tests might be special cased to only stop this reg programming on the 855 chips?
I pushed Peter's fix upstream. Please test and reopen if it doesn't work. Thanks, Jesse
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.