<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 - kernel panic and freeze on resume in [radeon] [ttm]"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91291">91291</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>kernel panic and freeze on resume in [radeon] [ttm]
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</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/Radeon
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>kparal@redhat.com
</td>
</tr></table>
<p>
<div>
<pre>A few times in a month, my computer fails to resume and just hangs, with black
screen, and needs hard reset. This time I got lucky and kernel panic text was
shown on my screen, so I took a shot of it. There's a lot of [ttm] and [radeon]
strings in it, so it looks like it is related to my Radeon card. The text on
the screen has "scrolled" once in a while (it seemed to be rotation), I hope I
captured everything important.
Components:
Radeon R9 270:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811]
fully updated Fedora 22:
kernel-4.0.7-300.fc22.x86_64
xorg-x11-server-Xorg-1.17.2-1.fc22.x86_64
xorg-x11-drv-ati-7.5.0-3.fc22.x86_64
libdrm-2.4.61-3.fc22.x86_64
mesa-dri-drivers-10.6.1-1.20150629.fc22.x86_64
Please tell me if I can add more useful information somehow. That issue is not
easily reproducible, it happens rarely and usually I just see a black screen,
so I can't even tell whether it is always the same issue or not.</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>