Bug 24237

Summary: [855GM] xorg-server hard freeze when kms is disabled
Product: xorg Reporter: Miklos Vajna <vmiklos>
Component: Driver/intelAssignee: Gordon Jin <gordon.jin>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
dmesg (Xorg.0.log is not present, X freezes before creating any log) none

Description Miklos Vajna 2009-09-30 17:08:04 UTC
Hello,

My card works fine with: xorg-server 1.6.1, kernel 2.6.31.1 and xf86-video-intel 2.7.1. I did a major test upgrade on a test partition and now my box hard freezes when X starts up and KMS is disabled. If I modprobe the i915 kernel module with modeset=1, then everything is fine.

Chipset:

$ /usr/sbin/lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

System architecture:

$ uname -m
i686

xf86-video-intel/xserver/mesa/libdrm version:

xf86-video-intel 2.9.0
xorg-server 1.6.99.903 (hal support disabled)
mesa 7.6
libdrm 2.4.14

kernel version:

$ uname -r
2.6.32-rc2-dirty (in fact this is an unmodified 2.6.32-rc1 kernel, because the guys on #intel-gfx@freenode advised that I should try upgrading my kernel before I report a bug)

Linux distribution:

Frugalware Linux -current

Machine model:

Clevo M450C

Steps to reprouce:

Upgrade to xorg-server 1.7rc and xf86-video-intel 2.9, disable KMS and start X. It results in a hard freeze all the time.
Comment 1 Miklos Vajna 2009-09-30 17:08:45 UTC
Created attachment 29963 [details]
xorg.conf
Comment 2 Miklos Vajna 2009-09-30 17:10:22 UTC
Created attachment 29964 [details]
dmesg (Xorg.0.log is not present, X freezes before creating any log)
Comment 3 Gordon Jin 2009-09-30 18:29:43 UTC

*** This bug has been marked as a duplicate of bug 23568 ***

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.