Bug 586235

Summary: [KMS] Out of Scan Range
Product: [Fedora] Fedora Reporter: Marko Myllynen <myllynen>
Component: kernelAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ajax, anton, dougsland, gansalmon, itamar, jonathan, kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.33.3-85.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-18 08:09:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output, screen normal
none
dmesg output, screen blank
none
diff of good vs. bad drm messages none

Description Marko Myllynen 2010-04-27 06:33:03 UTC 
Description of problem:
After installing Fedora 13 Beta on a system with Intel display adapter and an old Sun monitor everything worked ok. However, after upgrading to kernel 2.6.33.2-57.fc13.i686.PAE and booting, then while KMS is being enabled the screen goes blank and the monitor displays information "Out of Scan Range".

I'll attach dmesg outputs with both kernels using drm.debug=0x06.

Version-Release number of selected component (if applicable):
2.6.33.2-57.fc13.i686.PAE

How reproducible:
Always
Comment 1 Marko Myllynen 2010-04-27 06:34:19 UTC 
Created attachment 409365 [details]
dmesg output, screen normal
Comment 2 Marko Myllynen 2010-04-27 06:34:45 UTC 
Created attachment 409366 [details]
dmesg output, screen blank
Comment 3 Chuck Ebbert 2010-04-28 13:41:47 UTC 
Created attachment 409833 [details]
diff of good vs. bad drm messages