<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 --- - Two GPU RV790, three screen setup locks up with dpm=1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70165">70165</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Two GPU RV790, three screen setup locks up with dpm=1
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Mathias.Froehlich@web.de
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Radeon
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Hi,
I have here a dual radeon RV790 gpu, three screen setup. Tried this out with
dpm=1 locks up the machine. The lockup happens either when X starts and lightdm
starts to paint the login widget or, if the machine survives this, it usually
occurs once the mouse crosses the borders of the two gpu's screens on the X
display.
I run fedora 19 with a recent patch level.
The kernel that runs in dpm mode is 7dee8dff47734ee52da2cd8b8ea9736e42c5062f
which is todays linus master tree and includes all of agd5f/drm-fixes-3.12.
Attached are, dmesg with and without dpm enabled, Xorg logs with these cases,
the xorg configuraton file for these three screens, and the video bioses of
these two only similar cards. The dpm variants are acquired logged in via ssh
on a session where lightdm did not manage to lock up the machine at the first
time but locked it when I moved the mouse across the screen borders.
Some observations when digging somehow into this problem:
1. The attached patch shows a minimal change to rv770_dpm_set_power_state that
makes the machine run as normal. I think that already narrows down the problem
a bit.
2. The pi->clk_regs.rv770.mpll_ss{1,2} values are set into the table that aims
to be activated above, but are never initialized like the other values beneath
on rv770. May be they need to be read initially from some gpu register?
3. Disabling aspm does not help.
4. Unplugging the second monitor on the second gpu makes the problem appear way
more seldom if it stays unplugged. Hotplugging this screen results in the same
reproducible lockup.
Greetings
Mathias</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>