From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92974] Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled
Date: Sat, 18 Jun 2016 11:03:50 +0000 [thread overview]
Message-ID: <bug-92974-502-eURc8oJuvA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92974-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92974
--- Comment #17 from charlie <bug0xa3d2@hushmail.com> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2017 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-18 11:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 2:11 [Bug 92974] Fiji Nano long boot up and long X startup with amdgpu-powerplay enabled bugzilla-daemon
2015-11-19 2:55 ` bugzilla-daemon
2015-11-21 3:58 ` bugzilla-daemon
2015-11-24 3:42 ` bugzilla-daemon
2015-11-24 22:39 ` bugzilla-daemon
2015-12-04 8:58 ` bugzilla-daemon
2015-12-05 2:45 ` bugzilla-daemon
2015-12-05 2:47 ` bugzilla-daemon
2015-12-05 2:49 ` bugzilla-daemon
2015-12-21 0:12 ` bugzilla-daemon
2015-12-21 21:12 ` bugzilla-daemon
2015-12-21 21:24 ` bugzilla-daemon
2015-12-21 22:44 ` bugzilla-daemon
2016-06-16 3:50 ` bugzilla-daemon
2016-06-16 16:19 ` bugzilla-daemon
2016-06-16 16:24 ` bugzilla-daemon
2016-06-17 6:57 ` bugzilla-daemon
2016-06-18 11:03 ` bugzilla-daemon [this message]
2019-11-19 8:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-92974-502-eURc8oJuvA@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).