<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 --- - Changing display mode while opening audio leaves audio unusable"
href="https://bugs.freedesktop.org/show_bug.cgi?id=72212">72212</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Changing display mode while opening audio leaves audio unusable
</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>lauri.myllari@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>unspecified
</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=90072" name="attach_90072" title="kernel log from failed playback attempt">attachment 90072</a> <a href="attachment.cgi?id=90072&action=edit" title="kernel log from failed playback attempt">[details]</a></span>
kernel log from failed playback attempt
I am using xbmc on Haswell to play a video with DTS-HD/MA audio. If resolution
matching is enabled, sometimes audio playback fails with input/output error,
and any further attempt to open the audio device fails.
If I disable resolution matching, I don't encounter this issue and HBR audio
works fine.
I tried reproducing the issue with speaker-test and xrandr, but could not
trigger it. My guess is that it is very timing sensitive, and xbmc happens to
time the mode change and audio init just right.
I built a kernel with verbose sound debugging, and booted with drm.debug=0x0e.
I am attaching a log from a failed playback attempt. My kernel includes some
upstream patches, see linux-992.* in
<a href="https://github.com/laurimyllari/OpenELEC.tv/tree/77faefac8ef51d9434a918ba4bb12deddaa9e416/packages/linux/patches/3.12.1">https://github.com/laurimyllari/OpenELEC.tv/tree/77faefac8ef51d9434a918ba4bb12deddaa9e416/packages/linux/patches/3.12.1</a>
I have also tried using 3.13-rc1.
Is it obvious from the log what's happening? If not, what would be the best way
to provide useful information?
(The log is a bit verbose, but some points of interest may be at 81.199631
where ELD is not yet available, 81.499301 retry after 300ms, 81.571388 fifo
underrun and 91.489083 playback write error)</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>