| Summary: | [GM45] X freezes immediately on Lenovo X200 with Fedora rawhide (GEM kernel) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Bryan O'Sullivan <bos> | ||||||||||
| Component: | Driver/intel | Assignee: | Wang Zhenyu <zhenyu.z.wang> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
| Severity: | blocker | ||||||||||||
| Priority: | medium | CC: | colin, jeremy, sa | ||||||||||
| Version: | git | Keywords: | NEEDINFO | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 19076 [details]
Xorg.0.log from running Xorg -probeonly
Created attachment 19079 [details]
Xorg.0.log from frozen startup
So your kernel has gem support right? Could you first try an older or vanilla kernel? Or first try "NoAccel" option. Created attachment 19104 [details]
Xorg.0.log with NoAccel
The X server starts successfully with the intel driver using NoAccel, but it incorrectly uses a display resolution of 1024x768. The vesa driver uses the correct resolution, of 1280x800.
I don't know how to tell whether I have a GEM-enabled kernel. I don't follow Xorg development, so I didn't even know about GEM until you asked about it. But I'm running Fedora rawhide's 2.6.27-rc6 kernel, FWIW.
Let me know if you need more information.
So I suggest to try a vanilla kernel instead, as rawhide has cutting-edge gem support which might cause the problem you've seen, and we're not handling rawhide kernel issue... The default 1024x768 mode select is xserver 1.5's problem in its method to select initial mode. You should be able to use xrandr later to check to preferred mode, or write it into xorg.conf. We also met similar problem on GM45: bug#17416. But the error message seems different. I'm decreasing priority since this happens on Fedora rawhide kernel (with GEM) instead the upstream code. Do you connect any external monitors, Bryan? I see this problem with no external monitor attached. *** Bug 17851 has been marked as a duplicate of this bug. *** This needs to be retested against current drm-intel-next kernel and master xf86-video-intel. It seems to work just fine for me. All of the problems I described in bug 17851 are gone. I'm using master xf86-video-intel/libdrm and kernel 2.6.27 with your changes to intel-agp. Nice! Sven, do you also use a X200? (In reply to comment #12) > Nice! Sven, do you also use a X200? Sven is reporter of bug#17851 (marked as dup with here). He uses G45 (Asus P5Q-EM). (In reply to comment #13) > (In reply to comment #12) > > Nice! Sven, do you also use a X200? > > Sven is reporter of bug#17851 (marked as dup with here). He uses G45 (Asus > P5Q-EM). > ping Bryan.... With reference to comment #11, it states "with your changes to intel-agp." As I'm seeing the "fence" problem when resuming from suspend I'd like to try these changes too. (In reply to comment #16) > With reference to comment #11, it states "with your changes to intel-agp." As > I'm seeing the "fence" problem when resuming from suspend I'd like to try these > changes too. Erm, that wasn't clear... what I'm asking is, *what* are the changes to intel-agp? :) (In reply to comment #17) > Erm, that wasn't clear... what I'm asking is, *what* are the changes to > intel-agp? :) > Specifically, this patch: http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=2052746fc8397130c120f0194a89938b0b62b6cb time out for response from bug reporter. this bug should be fixed.. |
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.
Created attachment 19075 [details] lspci output If I try to start X on a new Lenovo X200 laptop, the display is frozen black and I cannot kill the X server or switch to a different virtual console. I'm running Fedora rawhide x86_64, with a 2.6.27 prepatch kernel. Both the 2.4.2 and current git intel xorg drivers show the same symptoms.