Bug 4728 - Timer code in WaitFor.c needs better overflow handling
Summary: Timer code in WaitFor.c needs better overflow handling
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: All All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-09 16:52 UTC by Alan Coopersmith
Modified: 2018-12-13 22:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Alan Coopersmith 2005-10-09 16:52:37 UTC
Bug #3254 noted that if you set values so large for the DPMS timers that they
overflow, the server goes into a tight loop constantly convinced the timers have
been hit every time through WaitForSomething, checking them all, and then waiting
for 0 milliseconds before doing it all again.

The immediate cause of that bug was fixed by simply preventing overflow when
reading the timeout values from the config file, but the timer code also needs
some long term thought to figure out if more work should be done to prevent 
overflows there. (Perhaps the timer values should be extended from 32-bit to 
64-bit on platforms that can efficiently handle 64-bit arithmetic?)
Comment 1 Daniel Stone 2007-02-27 01:28:26 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 chemtech 2013-03-15 14:41:48 UTC
Alan Coopersmith 
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Comment 3 GitLab Migration User 2018-12-13 22:15:45 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/334.


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.