<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 --- - linux-3.9: [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64133">64133</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>linux-3.9: [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mmokrejs@fold.natur.cuni.cz
</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=78736" name="attach_78736" title="dmesg 3.9 attempt1 with both "*ERROR* dp aux" and "Wrong MCH_SSKPD"">attachment 78736</a> <a href="attachment.cgi?id=78736&action=edit" title="dmesg 3.9 attempt1 with both "*ERROR* dp aux" and "Wrong MCH_SSKPD"">[details]</a></span>
dmesg 3.9 attempt1 with both "*ERROR* dp aux" and "Wrong MCH_SSKPD"
This bug is present in 3.9 and linux-next-20130501. We communicated about it in
private emails with some developers, so I am pasting in here the whole
communication.
On Wed, May 1, 2013 at 12:39 AM, Sedat Dilek <<a href="mailto:sedat.dilek@gmail.com">sedat.dilek@gmail.com</a>> wrote:
<span class="quote">> On Wed, May 1, 2013 at 12:30 AM, Martin Mokrejs
> <<a href="mailto:mmokrejs@fold.natur.cuni.cz">mmokrejs@fold.natur.cuni.cz</a>> wrote:
>> Hi Sedat, [+Imre and +Daniel who were in the original thread]
>>
>> Sedat Dilek wrote:
>>> On Tue, Apr 30, 2013 at 11:56 PM, Martin Mokrejs
>>> <<a href="mailto:mmokrejs@fold.natur.cuni.cz">mmokrejs@fold.natur.cuni.cz</a>> wrote:
>>>> Hi,
>>>> I found the above error in my dmesg and found a thread
>>>> <a href="https://lkml.org/lkml/2013/2/27/275">https://lkml.org/lkml/2013/2/27/275</a> . However, I am not sure this
>>>> is really my hardware BIOS bug or a kernel bug. Would you please
>>>> ensure me I should blame Dell for this Dell Vostro 3550 laptop?
>>>> This is a Sandy Bridge-based laptop with no extra graphics chip,
>>>> has only the intel VGA bundled into my core i7 CPU.
>>>> I am attaching a full dmesg from my system.
>>>> Regarding symptoms ... I think at the time I got this error
>>>> message in dmesg I had my external HDMI1 screen working ... but I
>>>> admit I have in general "random" issues that my external HDMI1 display
>>>> is not detected during bootup and stays blank. xrandr says HDMI1 is
>>>> disconnected I cannot make it to enable HDMI1 for me. Turning on/off
>>>> the LCD itself does not work, also not manually setting its input to
>>>> HDMI (it has also VGA D-SUB input socket). But these issue exist in
>>>> 3.7/3.8 series as well. So maybe this ERROR message which landed in
>>>> 3.9-rc1 is good for me. To date, have the latest BIOS, A11 for this
>>>> model.
>>>>
>>>
>>> IIRC that was fixed with [1] and is included in Linux-v3.9?
>>
>> Seems not. This is vanilla 3.9.
>></span >
>
<span class="quote">> I am on Linux-Next, try that or drm-intel-next?</span >
Hm, random HDMI failures combined with the dp aux stuff being stuck
makes some sense. If drm-intel-nightly or linux-next don't cut it for
you, please file a bug report on bugs.freedesktop.org against DRI ->
DRM(Intel)
<span class="quote">>>>
>>> Might be good to CC intel-gfx ML.
>>
>> Yeah, I wanted to ask first ... and due to the size of dmesg it would not
>> likely pass filters anyway ... Please Cc: the list for the sake of internet
>> archives if you find this *relevant*. I just do not know whether this is
>> a false alarm or not. Sorry for me being so suspicious. ;-)
>>
>>>
>>> AFAICS I have seen some /similiar/same) drm/kms/i915 warnings/errors
>>> with v3.9-rc7+ Ubuntu/raring mainline kernels [1].
>>> But I might be wrong...
>>
>> OK, I did another cold boot and this time the ERROR message is gone, but the
>> line with Wrong MCH_SSKPD stays. Below are both snippets of two plain 3.9
>> bootups.
>></span >
>
<span class="quote">> That one I reported, too.
> Daniel was reflecting on it, can't say if he made a decision.
> AFAICS harmless.</span >
Worst case it can cause underruns, which especially on DP can cause
loss of sync and black screen.
-Daniel</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>