<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - vram sizes reported by the kernel totally off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106872">106872</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>vram sizes reported by the kernel totally off
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bas@basnieuwenhuizen.nl
</td>
</tr></table>
<p>
<div>
<pre>With Pierre-Loup's desktop we have an issue where the reported VRAM and CPU
visible VRAM are totally off.
e.g. the last report we had kernel reported total VRAM size of
0xfffffffb3070f000 (16.0 EiB) and a visible VRAM size of 0x86135000 (2.09 GiB).
The system is a large aperture system, so expected is ~8 GiB for both, and it
is most of the time. The system typically boots in a good state and eventually
after a while transitions to a bad state and sometimes it transitions back.
We have not been able to find a pattern and on one of the earlier cases the
debugfs vram_mm file reported reasonable size & utilization.
The kernels that have been tried include amd-staging-drm-next and a released
kernel (need to look up whether it was 4.15 or 4.16 if that information is
needed)</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>