<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 - Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92974">92974</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI 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/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bug0xa3d2@hushmail.com
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=119727" name="attach_119727" title="Output of dmesg after startup.">attachment 119727</a> <a href="attachment.cgi?id=119727&action=edit" title="Output of dmesg after startup.">[details]</a></span>
Output of dmesg after startup.
With AMD Powerplay enabled in the kernel (cloned from
<a href="http://cgit.freedesktop.org/~agd5f/linux/?h=amdgpu-powerplay)--when">http://cgit.freedesktop.org/~agd5f/linux/?h=amdgpu-powerplay)--when</a> the
computer boots there is text, as usual, before modesetting tries to switch to
the native resolution of the monitor. At this point, the monitor backlight
turns off for about 5 seconds and then stays on for approximately 2 minutes
displaying nothing as if the computer locked up with no other boot activity
occuring. The Alt+PrintScreen+E/I/U/R button combo still works at this time.
If left alone the system finishes booting normally after about 2 minutes.
dmesg gives these new error/messages: "Failed to send Previous Message." and
..."[drm] ib test on ring 12 succeeded" that I have not noticed when AMD
Powerplay is disabled.
Trying to run, "startx" at the console also simulates a system freeze for about
2 minutes or so then X starts normally.
To work around the long boot and long X startup bug the kernel option, "Device
Drivers/Graphics support/Direct Rendering Manager/Enable legacy fbdev support
for your modesetting driver" must be set with, "n". This gives a black screen
or no console after the machine boots to log in blind with. X can also be
started blind and displayed normally with no startup delay. Another option is
to autologin with KDM or such like to boot directly into X after legacy fbdev
has been disabled in the kernel options.
With AMD Powerplay disabled in the kernel there are no startup issues.
Toggling or including/excluding these kernel boot, "lilo.conf" options have no
effect on the bug: "amdgpu.enable_scheduler=0 ; radeon.modeset=1 ;
radeon.hw_i2c=1 ; radeon.disp_priority=2 ; radeon.fastfb=1 ; radeon.backlight=1
; radeon.pcie_gen2=-1 ; radeon.hard_reset=0"
These patches (applied and not applied) have no effect on the bug:
<a href="http://people.freedesktop.org/~agd5f/0001-radeonsi-fix-fiji-raster-config.patch">http://people.freedesktop.org/~agd5f/0001-radeonsi-fix-fiji-raster-config.patch</a>
<a href="http://people.freedesktop.org/~agd5f/0001-drm-amdgpu-update-Fiji-s-tiling-mode-table.patch">http://people.freedesktop.org/~agd5f/0001-drm-amdgpu-update-Fiji-s-tiling-mode-table.patch</a>
Hardware: Fury Nano
git:
<a href="http://cgit.freedesktop.org/~agd5f/linux/commit/?h=amdgpu-powerplay&id=256ca780500bc445752763f32b246dc9ee396b62">http://cgit.freedesktop.org/~agd5f/linux/commit/?h=amdgpu-powerplay&id=256ca780500bc445752763f32b246dc9ee396b62</a>
Sidenote: hang check timer is disabled in the kernel.</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>