<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c17">Comment # 17</a> on <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">bug 92974</a> from <a class="email" href="mailto:bug0xa3d2@hushmail.com" title="charlie <bug0xa3d2@hushmail.com>"> charlie</a> <pre>The bios was updated from 0801 to 2603. The machine booted normally with an unpatched kernel. I restored previous overclocking settings and the long boot bug returned. Among testing a few bios parameters I found that adjusting "NB Configuration--PCIEX16_1"--like forcing auto(PCIEX16_2), X16 or X8--has no effect on the bug. "APU Frequency" or base clock is the only setting found to effect the long boot/startx bug. Any base clock values greater than 100 causes the bug. Underclocking CPU, NB and RAM has no effect when base clock is set to 101--the bug remains. This behavior did not occur before the commit mentioned earlier in this bug report thread as the base clock remained the same since before I first submitted the bug and until my recent testing today. With "amdgpu.pcie_gen_cap=0x00030003" applied through LILO this machine is capable of running at 104 base clock stable with system RAM near 2500mhz--without the long boot/startx bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>