Bug 438984 - intel driver logs recurring error message in Xorg.0.log
Summary: intel driver logs recurring error message in Xorg.0.log
Status: RESOLVED DUPLICATE of bug 427645
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Lubos Lunak
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-25 14:04 UTC by Stefan Brüns
Modified: 2008-10-27 08:31 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Brüns 2008-10-25 14:04:40 UTC 
The intel driver logs the same message (probing for displays?) into Xorg.0.log over and over again:
--------
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): I2C bus "CRTDDC_D" initialized.
(II) intel(0): I2C device "CRTDDC_D:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_D:ddc2" removed.
(II) intel(0): I2C bus "CRTDDC_D" removed.
(II) intel(0): I2C bus "CRTDDC_E" initialized.
(II) intel(0): I2C device "CRTDDC_E:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_E:ddc2" removed.
(II) intel(0): I2C bus "CRTDDC_E" removed.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(WW) EDID preferred timing clock 162.00MHz exceeds claimed max 160MHz, fixing
(II) intel(0): EDID vendor "DEL", prod id 40968
-------

Hardware: Intel DG965WH, G965 graphics, Dell flatpanel via ADD2 DVI card

Repetiotion of the message contains no additional information, and keeps the harddisk spinning.
Comment 1 Stefan Dirsch 2008-10-25 14:15:48 UTC 
Known issue of KDE4 probing for outputs all the time.
Comment 2 Lubos Lunak 2008-10-27 08:31:50 UTC 

*** This bug has been marked as a duplicate of bug 427645 ***