Bug 10670

Summary: inter driver turns off VGA output after a Xorg server reset
Product: xorg Reporter: Barry Scott <barry.scott>
Component: Driver/intelAssignee: Eric Anholt <eric>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: major    
Priority: medium    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log file
none
Xorg config file none

Description Barry Scott 2007-04-18 02:57:24 UTC 
I'm testing on HP 7600U (945) and HP 7700U (965)
running FC4 with 2.6.20 kernel and Xorg 7.2 + 
tar balls depends to support git intel driver
built from source.

1. start Xorg
2. xmessage Hello
3. ^C xmessage
4. xmessage Hello

At 1 the screen goes black showing Xorg is running and the screen is happy.
At 2 Hello appears on the screen
At 3 the Xorg server resets and the screen is still happy.
At 4 the screen sees the VGA signal go away.

Since xmessage is the one and only client when it quits the Xorg server will reset itself. The interesting message in the logs is:

(WW) intel(0):   Hardware claims plane A is off while software believes it is on
Comment 1 Barry Scott 2007-04-18 03:15:40 UTC 
It's simpler then I thought. Only three steps (I did not wait log enough to
see the screen notice the VGA signal had gone).

1. start Xorg
2. xmessage Hello
3. ^C xmessage

At 1 the screen goes black showing Xorg is running and the screen is happy.
At 2 Hello appears on the screen
At 3 the Xorg server resets and the screen sees the VGA signal go away.
Comment 2 Barry Scott 2007-04-18 03:20:07 UTC 
Created attachment 9650 [details]
Xorg log file

Notice this warning:

(WW) intel(0):   Hardware claims plane A is off while software believes it is on
Comment 3 Barry Scott 2007-04-18 03:20:48 UTC 
Created attachment 9651 [details]
Xorg config file
Comment 4 Eric Anholt 2007-04-18 09:25:00 UTC 
Already fixed in server RC4.

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.