<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66521">66521</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>wsun07@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=81912" name="attach_81912" title="dmesg with drm.debug=0xe in kernel command line">attachment 81912</a> <a href="attachment.cgi?id=81912&action=edit" title="dmesg with drm.debug=0xe in kernel command line">[details]</a></span>
dmesg with drm.debug=0xe in kernel command line
I have a DELL XPS13 laptop and an external monitor. They used to work well on
linux kernel 3.8. Recently, I upgraded to kernel 3.9 and found the resolution
of the external monitor could not be configured correctly. I checked kern.log
file and found a lot of error messages look this:
Jul 2 15:27:40 debian kernel: [ 39.181113] [drm:intel_dp_i2c_aux_ch] *ERROR*
too many retries, giving up
I downloaded the latest kernel from drm-intel-nightly
(drm-intel-a59485486882b9867bdcb1fe41cfdcba291c6585,July2nd,2013). However, the
issue is still there. The dmesg information with drm.debug=0xe is attached.
Since this issue was also reported by others and it was there for more than
three months, hope it can be set as a high priority investigation from the
development team.
Please let me know if you want me to try more patches.
Thanks,
Wei</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>