| Summary: | [G33] 2.2.0 locks up X with error "First SDVO output reported failure to sync" | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Alan W. Irwin <Alan.W.Irwin1234> | ||||||||
| Component: | Driver/intel | Assignee: | Hong Liu <hong.liu> | ||||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | critical | ||||||||||
| Priority: | medium | CC: | hong.liu, jbarnes, keithp, zhenyu.z.wang | ||||||||
| Version: | 7.3 (2007.09) | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||
| OS: | Linux (All) | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Alan W. Irwin
2007-11-26 12:17:23 UTC
So the crash only occurs after the server exits? Does it actually hard hang your system or can you ssh into it from outside? If the latter, I'm thinking it might be a duplicate of 13196... > So the crash only occurs after the server exits? Not completely sure, but I don't think so. The lockup occurs during "X -probeonly" which never seems to exit properly (although perhaps you can tell differently from the log file I have included in the original report). The lockup means no keyboard function and the monitor goes dark into extreme power saving mode. > Does it actually hard hang your system or can you ssh into it from outside? I can ssh into the box from outside, but the only way to return control to the local keyboard which was frozen and get the local monitor out of extreme power saving mode is to reboot the system. Ok, that's a good data point. Can you try the patch in #13196? It may fix this problem for you. >Ok, that's a good data point. Can you try the patch in #13196? It may fix this problem for you. Trying the patch may take a while. I am pretty experienced at building software, but this is my first try with building a component of X that is supposed to work consistently with my debian unstable version of xorg. I will follow the wiki advice at http://www.x.org/wiki/CompileXserverManually. I will first attempt to build the 2.1.1 version of xf86-video-intel. If that gives good results like the Debian binary version 2.1.1 of that driver, that will show my xf86-video-intel build procedure is working. Once I have that confirmation, I will build 2.2.0 with and without the patch to see if the patch makes any difference. < Can you try the patch in #13196? It may fix this problem for you. Good call, Jessie! The X lockup problems for the g33 chipset have been cleared up by applying i830-restore-pipeconf-fix.patch from #13196. I am posting this from my KDE desktop environment using (patched) version 2.2.0 of the xf86-video-intel driver. For reference I will be attaching my xorg.conf and log file. Also, I will be attaching the debuild output on Debian. (Thanks to Brice Goglin for giving me the debian cookbook for the debuild.) Note, there are a lot of compiler warnings for gcc version "gcc (GCC) 4.2.3 20071014 (prerelease) (Debian 4.2.2-3)" which the Intel development team will want to address. What's the next step? Will this patch be going into your next release in its present form or are there further changes planned for this area? If the latter, I will be happy to test.... Created attachment 12828 [details]
successful g33 xorg.conf file
Created attachment 12829 [details]
Successful X log file for g33
Created attachment 12830 [details]
debuild log on Debian testing/unstable showing lots of compile warnings
Excellent, thanks for testing. Yeah, I'm thinking we need a 2.2.1 release to address some of these brown paper bag bugs... Maybe next week after we pull in a few more fixes. As for the warnings, yeah they need to be cleaned up. But all that's left are printf format warnings (unsigned long is 32 bit on x86 and 64 bit on x86_64 and we're not using the right specifier), so there's nothing serious there. *** This bug has been marked as a duplicate of bug 13196 *** |
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.