<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 --- - bisected: GALLIUM_HUD hangs radeon 7970M (PRIME)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82628">82628</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>bisected: GALLIUM_HUD hangs radeon 7970M (PRIME)
</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>haagch@frickel.club
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Component</th>
<td>Mesa core
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=104629" name="attach_104629" title="journalctl log including the hang in the report">attachment 104629</a> <a href="attachment.cgi?id=104629&action=edit" title="journalctl log including the hang in the report">[details]</a></span>
journalctl log including the hang in the report
I'm using only DRI_PRIME=1 GALLIUM_HUD="fps,VRAM-usage+GTT-usage". I have not
tested much different combinations.
Tested on linux 3.16 mainline.
I'm not 100% sure, but I think this is my bisect result:
1cfcd0164e1be7d7b05b693f60a262ad735b7565 is the first bad commit
I haven't tested that much applications because it has a good chance of a hard
lockup of the whole machine. But often it recovers after killing the
application with the HUD.
With the Unreal Engine Cave Effects demo I think I can reproduce it every time
and in fact it is immediately visible whether it will work (when changing mesa
versions) because when it works immediately a black window with the HUD is
visible until the demo loads and when it won't work, a few fat white garbage
lines will be visible in the window or something like that.
I only tried glxgears as another application a few times and sometimes it
worked and sometimes it produced the lockup.
radeon 0000:01:00.0: ring 0 stalled for more than 10003msec
radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000011 last fence id
0x000000000000000d on ring 0)
radeon 0000:01:00.0: Saved 269 dwords of commands on ring 0.
radeon 0000:01:00.0: GPU softreset: 0x0000004D
radeon 0000:01:00.0: GRBM_STATUS = 0xB3525028
radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x2F800002
radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x2F800002
radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0
radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40000000
radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00408002
radeon 0000:01:00.0: R_008680_CP_STAT = 0x84228647
radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83146
radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100
radeon 0000:01:00.0: GRBM_STATUS = 0x00003028
radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006
radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006
radeon 0000:01:00.0: SRBM_STATUS = 0x200400C0
radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000
radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Without the HUD it always works.
Oh and sometimes with the buggy mesa revisions *and* with the HUD it just won't
start and there is immediately the message that the kernel rejected the CS
stream or whatever the message is. I have not seen this without the HUD.</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>