Bug 78770 – [patch] DDC probe returns invalid vsync,hsync when monitor does not report it and it is not in monitorsDB

Bug 78770 - [patch] DDC probe returns invalid vsync,hsync when monitor does not report it and it is not in monitorsDB

Summary:	[patch] DDC probe returns invalid vsync,hsync when monitor does not report it...

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	kudzu (Show other bugs)
Sub Component:
Version:	phoebe
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-11-29 09:59 EST by Miloslav Trmac
Modified:	2014-03-16 22:32 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-28 10:43:32 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Miloslav Trmac 2002-11-29 09:59:11 EST

Description of Problem:
Bug 70190 contains a patch for kudzu, which fixes a NULL pointer
dereference when monitor does not report hsync/vsync values, and
it is not in MonitorsDB. Because the VESA DDC code maps memory
to first 1M, kudzu does not crash, but reports hsync/vsync
in range about -2e9. This has been worked around in anaconda, but
the underlying cause has not been fixed. Please see 70190
for an example and an patch.

Comment 1 Miloslav Trmac 2003-01-06 14:51:03 EST

Same in phoebe.
I hope this will be fixed before summer betas ;-)

Comment 2 Miloslav Trmac 2003-01-28 10:43:32 EST

I don't know what bug 78284 says, but the patch is in rhlinux.redhat.com
CVS now.

Gee, I can't even mark it as duplicate ;-)

Note You need to log in before you can comment on or make changes to this bug.