From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201273] Fatal error during GPU init amdgpu RX560
Date: Tue, 09 Oct 2018 21:44:12 +0000 [thread overview]
Message-ID: <bug-201273-2300-56M5FSHHmP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201273-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #2 from quirin.blaeser@freenet.de ---
Created attachment 278973
--> https://bugzilla.kernel.org/attachment.cgi?id=278973&action=edit
dmesg old + new
The RX560 is new. Error happens only from time to time and only at bootup and i
have to press reset mostly. While bisecting
https://bugzilla.kernel.org/show_bug.cgi?id=201275
i had created two more files with output of dmesg. I have included all of them
in archive. Maybe v4.18.0 is affected too. I could use an older Kernel to
verify, but since this is not an predictible case, i would have to use it for
several days to check this. Rarely it happens that Monitor blacks out ( really
black, back lights and sound off too), but this may be an hardware issue.
Fiddling at the hdmi plug on the monitors side resolves that. This may be an
issue, if code is affected at init, but i don´t think it is.
I could disable CONFIG_DRM_AMDGPU_CIK to test, if this is related too.
--
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:[~2018-10-09 21:44 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 16:37 [Bug 201273] New: Fatal error during GPU init amdgpu bugzilla-daemon
2018-10-09 13:00 ` [Bug 201273] Fatal error during GPU init amdgpu RX560 bugzilla-daemon
2018-10-09 17:36 ` bugzilla-daemon
2018-10-09 21:44 ` bugzilla-daemon [this message]
2018-10-10 15:47 ` bugzilla-daemon
2018-10-17 5:56 ` bugzilla-daemon
2018-10-17 9:27 ` bugzilla-daemon
2018-10-18 13:21 ` bugzilla-daemon
2018-10-18 13:22 ` bugzilla-daemon
2018-10-23 14:00 ` bugzilla-daemon
2018-11-05 6:22 ` bugzilla-daemon
2018-11-05 15:39 ` bugzilla-daemon
2018-11-05 19:52 ` bugzilla-daemon
2018-11-09 17:24 ` bugzilla-daemon
2018-11-21 18:10 ` bugzilla-daemon
2018-11-23 16:00 ` bugzilla-daemon
2018-11-23 21:34 ` bugzilla-daemon
2018-11-24 18:03 ` bugzilla-daemon
2018-11-25 20:41 ` bugzilla-daemon
2018-12-08 7:12 ` bugzilla-daemon
2018-12-10 19:51 ` bugzilla-daemon
2018-12-13 6:36 ` bugzilla-daemon
2018-12-13 15:23 ` bugzilla-daemon
2018-12-13 17:24 ` bugzilla-daemon
2018-12-13 18:25 ` bugzilla-daemon
2018-12-14 7:59 ` bugzilla-daemon
2018-12-16 10:49 ` bugzilla-daemon
2018-12-17 14:53 ` bugzilla-daemon
2018-12-22 17:57 ` bugzilla-daemon
2018-12-24 11:32 ` bugzilla-daemon
2019-01-05 22:46 ` bugzilla-daemon
2019-01-13 9:22 ` bugzilla-daemon
2019-01-22 16:58 ` bugzilla-daemon
2019-01-23 9:29 ` bugzilla-daemon
2019-01-27 12:42 ` bugzilla-daemon
2019-02-09 20:50 ` bugzilla-daemon
2019-02-09 21:04 ` bugzilla-daemon
2019-02-19 17:25 ` bugzilla-daemon
2019-03-06 17:20 ` bugzilla-daemon
2019-03-07 21:01 ` bugzilla-daemon
2019-03-25 18:14 ` bugzilla-daemon
2019-04-04 21:00 ` bugzilla-daemon
2019-04-05 6:25 ` bugzilla-daemon
2019-04-11 19:54 ` bugzilla-daemon
2019-04-24 12:16 ` bugzilla-daemon
2019-04-24 19:44 ` bugzilla-daemon
2019-04-26 11:43 ` bugzilla-daemon
2019-04-27 19:22 ` bugzilla-daemon
2019-04-28 15:46 ` bugzilla-daemon
2019-04-30 19:12 ` bugzilla-daemon
2019-05-01 18:43 ` bugzilla-daemon
2019-05-01 19:25 ` bugzilla-daemon
2019-05-02 20:36 ` bugzilla-daemon
2019-05-03 10:33 ` bugzilla-daemon
2019-05-03 10:34 ` bugzilla-daemon
2019-05-03 17:04 ` bugzilla-daemon
2019-05-09 9:27 ` bugzilla-daemon
2019-06-08 9:09 ` bugzilla-daemon
2019-06-08 11:23 ` bugzilla-daemon
2022-07-28 15:35 ` 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-201273-2300-56M5FSHHmP@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.