From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 193651] Amdgpu error messages at boot with Amd RX460
Date: Wed, 05 Apr 2017 18:59:23 +0000 [thread overview]
Message-ID: <bug-193651-2300-m0tJLluzi4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-193651-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #23 from Milo (milomak@gmail.com) ---
(In reply to Christian Lanig from comment #22)
> Thanks for clarification. That means building the Kernel was not a possible
> fix for the messages but for getting the driver to start with Tonga.
>
> So the AVFS- issue and missing/wrong value in the voltage dependency table
> is still existent. As well as your remaining Powerplay messages.
i didn't have the avfs issue but the other two on my r9 m390 and booting
taking as long as 10 minutes when i moved from kernel 4.8 to 4.9/4.10
having built 4.11-rc4, my boot times are back down to around 30 seconds but the
messages still persist in dmesg. and it seems i have added some ib related
messages.
so i was just confirming that from my perspective there is an issue that was
solved though not the messages that led me here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-05 18:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 13:58 [Bug 193651] New: Amdgpu error messages at boot with Amd RX460 bugzilla-daemon
2017-01-31 16:26 ` [Bug 193651] " bugzilla-daemon
2017-01-31 16:26 ` bugzilla-daemon
2017-01-31 16:26 ` bugzilla-daemon
2017-01-31 16:27 ` bugzilla-daemon
2017-01-31 16:33 ` bugzilla-daemon
2017-01-31 16:35 ` bugzilla-daemon
2017-02-01 22:11 ` bugzilla-daemon
2017-02-02 10:19 ` bugzilla-daemon
2017-02-02 10:32 ` bugzilla-daemon
2017-02-02 15:01 ` bugzilla-daemon
2017-02-02 15:49 ` bugzilla-daemon
2017-02-02 22:26 ` bugzilla-daemon
2017-02-02 22:28 ` bugzilla-daemon
2017-02-02 22:31 ` bugzilla-daemon
2017-03-25 20:58 ` bugzilla-daemon
2017-03-26 3:22 ` bugzilla-daemon
2017-03-26 7:50 ` bugzilla-daemon
2017-03-26 10:16 ` bugzilla-daemon
2017-03-26 10:18 ` bugzilla-daemon
2017-04-03 22:51 ` bugzilla-daemon
2017-04-04 12:15 ` bugzilla-daemon
2017-04-04 13:36 ` bugzilla-daemon
2017-04-05 18:59 ` bugzilla-daemon [this message]
2017-06-01 12:34 ` bugzilla-daemon
2017-09-15 21:48 ` bugzilla-daemon
2017-10-23 18:11 ` bugzilla-daemon
2017-10-24 17:18 ` bugzilla-daemon
2017-11-13 7:51 ` bugzilla-daemon
2018-12-05 2:29 ` bugzilla-daemon
2019-11-11 11:05 ` 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-193651-2300-m0tJLluzi4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.