<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108654">bug 108654</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;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>REOPENED
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108654#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI][DRMTIP] igt@pm_rpm@* - dmesg-warn - *ERROR* DBus power enable timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108654">bug 108654</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>(In reply to Imre Deak from <a href="show_bug.cgi?id=108654#c21">comment #21</a>)
<span class="quote">> (In reply to Martin Peres from <a href="show_bug.cgi?id=108654#c20">comment #20</a>)
> > (In reply to Jani Saarinen from <a href="show_bug.cgi?id=108654#c19">comment #19</a>)
> > > Resolving again to wait CI results.
> >
> > There is NEEDINFO for that...
> >
> > And anyway, the patch is a workaround, not a fix. So re-opening.
>
> The patch does fix the problem where we tried to enable/disable DBuf slices
> incorrectly. As a result we shouldn't get the timeout error and possibly
> other related failures.
>
> So imo the reported bug is fixed, we shouldn't get these error
> messages/conditions. It would be also good to be certain in this by way of
> having the bug open only if the error messages/conditions reappear. The task
> to toggle the second Dbuf slice on-demand should be tracked separately imo.</span >
ACK. I'll tentatively resolve the bug then, and wait for some time before
closing it for real (after getting enough data to prove it got fixed).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>