Bug 88053

Summary:	after executing ddcxinfo the computer slows the clock by a factor of 5
Product:	[Retired] Red Hat Linux	Reporter:	Joakim Nordberg <joakim>
Component:	kudzu	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DEFERRED	QA Contact:	David Lawrence <dkl>
Severity:	high	Docs Contact:
Priority:	medium
Version:	8.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-29 20:56:59 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:

Description Joakim Nordberg 2003-04-04 22:13:05 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226
Debian/1.2.1-9

Description of problem:
I'm using a old machines IBM PC-300XL and HP Vectra with 233Mhz cpu and +192Mb ram.

When i run ddcxinfo to get the Modelines the computer still runs as it should
but I get som strange problems... The Clock goes slower, each computer second
takes 5-6 seconds i real...

root# time sleep 5
reports approx seconds but it takes 27 seconds in real to execute...

The computer has either Trio 64V2/DX card or ATI Rage 128

strange strange

Version-Release number of selected component (if applicable):
kudzu-vesa 0.99.66

How reproducible:
Always

Steps to Reproduce:
1. Reboot computer
2.# sleep 5 (takes 5 seconds until prompt comes back)
3.# ddcxinfo (or svgamodes)
4.# sleep 5 (takes 27-28 seconds until prompt comes back)

Actual Results:  I get network timeouts, the computer drifts 5 minutes slower
every minute...

Expected Results:  None of above.
The svgamodes and ddcxinfo gives correct info tough.

Additional info:

Comment 1 Bill Nottingham 2005-03-29 20:56:59 UTC

Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

This is a odd interaction between the real-mode DDC calls and your BIOS. It is
unlikely that it will be fixed at this time.