<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:rockowitz@minsoft.com" title="Sanford Rockowitz <rockowitz@minsoft.com>"> <span class="fn">Sanford Rockowitz</span></a>
</span> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915 I2C failures with recent chips and docking stations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100954">bug 100954</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>REOPENED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915 I2C failures with recent chips and docking stations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100954#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915 I2C failures with recent chips and docking stations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100954">bug 100954</a>
from <span class="vcard"><a class="email" href="mailto:rockowitz@minsoft.com" title="Sanford Rockowitz <rockowitz@minsoft.com>"> <span class="fn">Sanford Rockowitz</span></a>
</span></b>
<pre>Ricardo,
Unfortunately, I don't see the problem on any of my own laptops, which are
older. So for me to install the latest intel drm and produce a driver
diagnostic log is pointless. However, I've received enough bug reports from
people who have tried to use ddcutil through a docking station that I'm pretty
sure there's a problem.
>From the original post on the intel-gfx list:
<span class="quote">> I'm not sure how best to go about reporting these issues. The usual bug
> reporting mechanism asks for detailed information about a specific
> system, which I don't have. What I do have is the ability to see a
> pattern.</span >
<span class="quote">> Because I2C communication is so fragile (dependencies on hardware
> quirks, drivers, etc), ddcutil (which is written in C) has an extensive
> subsystem devoted to remotely diagnosing user configurations. It
> already reports DDC (i.e. I2C) communication errors, and has interfaces
> to udev, libdrm, and x11 libraries. If there is some i915 specific code
> I could add to refine the diagnosis, I would be happy to add that.
> (Note: ddcutil is entirely a user space program, using the i2c-dev
> interface.)</span >
<span class="quote">> Suggestions on how to proceed appreciated.</span >
That list thread led to the suggestion that I post a bug report despite the
unavailability of detail. Hopefully I've categorized the bug properly, and
this report will at least serve as a marker that there's a problem.
Sanford</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 on the CC list for the bug.</li>
</ul>
</body>
</html>