From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 193651] Amdgpu error messages at boot with Amd RX460
Date: Mon, 03 Apr 2017 22:51:42 +0000 [thread overview]
Message-ID: <bug-193651-2300-BiGKfa7wRk@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 #20 from Christian Lanig (christian.lanig@gmail.com) ---
This bug report is partly a duplicate of that one:
https://bugs.freedesktop.org/show_bug.cgi?id=100443
I'm getting the same AVS/Powerplay messages, updating the firmware didn't help.
The topic headline is very unspecific and the replies appear very confusing to
me.
Has this issue been solved or not?
Does a custom Kernel change the messages? - I'm using the newest Ubuntu
mainline Kernel. Is something wrong with the configuration used to build this
Kernel by the Kernel team?
How is this issue related to Tonga GPUs? Polaris is the first dGPU with AVFS.
How many issues do we count here and which replies belong to which issue?
Perhaps someone could make a summary or something - that would be very
pleasant.
--
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-03 22:51 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 [this message]
2017-04-04 12:15 ` bugzilla-daemon
2017-04-04 13:36 ` bugzilla-daemon
2017-04-05 18:59 ` bugzilla-daemon
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-BiGKfa7wRk@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 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).