From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 193651] New: Amdgpu error messages at boot with Amd RX460
Date: Mon, 30 Jan 2017 13:58:17 +0000 [thread overview]
Message-ID: <bug-193651-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=193651
Bug ID: 193651
Summary: Amdgpu error messages at boot with Amd RX460
Product: Drivers
Version: 2.5
Kernel Version: 4.11-wip
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: fin4478@hotmail.com
Regression: No
Created attachment 253581
--> https://bugzilla.kernel.org/attachment.cgi?id=253581&action=edit
dmesg logfile
I have Gigabyte RX460 2GB gpu card, Debian testing Xfce and adg5f
drm-next-4.11-wip kernel downloaded and compiled as today. Computer works ok
but the dmesg command shows the following boot errors that might interest
amdgou driver developers. Mounting my home partiton fails amdgpu IB tests:
[ 7.001953] [drm] ib test on ring 12 succeeded
[ 7.055163] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts:
(null)
[ 8.011874] [drm:0xffffffffa01360ce] *ERROR* amdgpu: IB test timed out.
[ 8.011910] [drm:0xffffffffa00e1b4b] *ERROR* amdgpu: failed testing IB on
ring 13 (-110).
[ 8.011943] [drm:0xffffffffa00be574] *ERROR* ib ring test failed (-110).
Some powerplay errors:
[ 4.888584] amdgpu: [powerplay] [AVFS] Something is broken. See log!
[ 4.891452] amdgpu: [powerplay] Can't find requested voltage id in
vdd_dep_on_sclk table!
[ 4.894807] amdgpu: [powerplay]
failed to send message 309 ret is 254
[ 4.894824] amdgpu: [powerplay]
failed to send pre message 14e ret is 254
Bios recognition errors:
[ 4.729628] [drm] BIOS signature incorrect 20 7
[ 4.729635] amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xffff
--
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 reply other threads:[~2017-01-30 13:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 13:58 bugzilla-daemon [this message]
2017-01-31 16:26 ` [Bug 193651] Amdgpu error messages at boot with Amd RX460 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
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@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).