Bug 3980

Summary: machine completely unusable during Xorg startup
Product: xorg Reporter: Wilco <wbeekhui>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: libv
Version: 6.8.2   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg 6.8.2 log with VIA driver
none
My Xorg log file none

Description Wilco 2005-08-04 23:45:18 UTC
When starting X on my laptop it takes about 20 seconds and during 15 seconds of  
that 20 when X probes for modes the machine isn't responding to anything or  
handling interrupts.  
After starting X a few times my system clock lags about a minute behind and all  
services running can't handle requests during that horrible 15 seconds.  
When starting X remotely I can see the delay when the driver is searching for   
matching VESA modes.   
I have a unichrome Pro chipset (PN800).   
It happens both with the VESA driver and with the VIA driver.   
I noticed a faster startup time when using the option "NoInt10" but with that  
option my display became unusable and required a reboot.
Comment 1 Wilco 2005-08-04 23:49:24 UTC
Created attachment 3258 [details]
xorg -configure
Comment 2 Donnie Berkholz 2005-09-05 22:49:41 UTC
Please reattach your log; it was lost.
Comment 3 Wilco 2005-09-07 01:25:56 UTC
Created attachment 3189 [details]
Xorg 6.8.2 log with VIA driver
Comment 4 Wilco 2005-09-22 01:36:16 UTC
VBEGetModePool seems to cause this problem. Can't find out why exactly.
Comment 5 Eric Vachon 2005-10-28 01:07:49 UTC
Created attachment 3650 [details]
My Xorg log file

I have the very same problem on my Dell inspiron 2200 laptop and this video
card :
Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics
Controller (rev 03)

It freezes completely the computer for 20 seconds when I start xorg. My driver
is working correcly when xorg is started, and I experience no problem at all
once in xorg. 

xorg version : 6.8.99.15-r4 (Gentoo)
kernel : 2.6.13-gentoo-r4 

My xorg log file is attached
Comment 6 Wilco 2005-10-28 07:02:23 UTC
Could you test it with the option "NoInt10" to see if it starts up faster? For
me it starts fast but the display becomes unusable (you may require a reboot).
I think the problem has to do with the display not reporting its capabilities
but I can't figure out how it works.
Does your clock also lags behind after starting X a few times?
Comment 7 Eric Vachon 2005-10-28 10:55:30 UTC
I just tried the Option "NoInt10" "Yes", and it gave me an error :

No usable screen found

I tried to count the time to see if there's a clock lag, but I can't seem to be
exact in my timing. But I can say it was 4 minutes behind this morning, so I
guess  it does lag behind. I can't do absolutely nothing while it loads. I don't
have access to my desktop, so all my attempts to see where it froze were in vain. 

Any other ideas?

PS. It was working fine with xorg 6.8.1, but now it's not in Gentoo anymore...
Comment 8 Wilco 2005-10-28 11:09:05 UTC
Well I started X from a remote terminal and noticed I couldn't do anything while
it loaded. But I'm gonna try 6.8.1 to see if that helps!
I haven't heard anything from the xorg team so I'm not sure what causes this,
probably some interrupt disabling routine.
Comment 9 Wilco 2005-10-31 11:48:26 UTC
Compiled and installed 6.8.1 and 6.8.0 but still the same problems.
Comment 10 Wilco 2006-03-13 20:12:44 UTC
Fixed this by using the openchrome drivers and removing a check which used the
VIA bios. It seems accessing the video bios is way to slow.
Comment 11 Daniel Stone 2007-02-27 01:27:34 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 12 Adam Jackson 2009-06-03 10:55:42 UTC
Yes, int10 is nasty.

The switch to x86emu everywhere should actually improve this a bit, but in general this isn't really fixable.

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.