Bug 13940 - X with ati/radeon driver gets stuck in loop with PreferredMode set
Summary: X with ati/radeon driver gets stuck in loop with PreferredMode set
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-05 09:07 UTC by Paul van Tilburg
Modified: 2008-01-05 13:59 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Xorg configuration (1.07 KB, text/plain)
2008-01-05 09:07 UTC, Paul van Tilburg 		no flags Details
Xorg log (41.56 KB, text/plain)
2008-01-05 09:07 UTC, Paul van Tilburg 		no flags Details
View All

Description Paul van Tilburg 2008-01-05 09:07:08 UTC 
When a PreferredMode is set in a Monitor section, X starts but immediately gets stuck in a loop (100% CPU usage) without making it to actually displaying anything.  X will not respond to any signals except for KILL.
I have seen this happen with all ati driver versions from the past 3, 4 months (up until and including 6.7.198~git20080102.30cab1db) on both an ATI Radeon 9200 Pro and ATI X800 XL.

N.B. The options in the Device section have no effect on the problem.
Comment 1 Paul van Tilburg 2008-01-05 09:07:35 UTC 
Created attachment 13542 [details]
Xorg configuration
Comment 2 Paul van Tilburg 2008-01-05 09:07:55 UTC 
Created attachment 13543 [details]
Xorg log
Comment 3 Julien Cristau 2008-01-05 09:24:13 UTC 
(In reply to comment #0)
> When a PreferredMode is set in a Monitor section, X starts but immediately gets
> stuck in a loop (100% CPU usage) without making it to actually displaying
> anything.  

this is a server bug, already fixed.  please upgrade to the latest xserver-xorg-core package in sid.
Comment 4 Paul van Tilburg 2008-01-05 13:40:46 UTC 
I hadn't expected that, seemed ati specific. Confirmed 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.