From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108521] RX 580 as eGPU amdgpu: gpu post error!
Date: Wed, 24 Oct 2018 06:24:44 +0000 [thread overview]
Message-ID: <bug-108521-502-qPXOL03chC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108521-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1001 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108521
--- Comment #4 from Robert Strube <rstrube@gmail.com> ---
I decided to apply a hack to 4.19 and see if I could get the eGPU to
initialize. I noticed that this code in /drivers/gpu/drm/amd/amdgpu/atom.c
if ((jiffies_to_msecs(cjiffies) > 5000)) {
DRM_ERROR("atombios stuck in loop for more than 5secs aborting\n");
ctx->abort = true;
}
is where the error is being thrown, so I thought I would try giving the eGPU
more time. I increased the 5000 value to 15000, recompiled the kernel, and
tried to attach the eGPU. Unfortunately I received the same error, but this
time after 15 seconds of trying to initialize the GPU. Should I increase the
time even more?
I'm not sure if the issue is actually related to not having enough time, or if
it's something else entirely.
I'll bump it up to 30 seconds in a final last ditch attempt.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1777 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:[~2018-10-24 6:24 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 5:14 [Bug 108521] RX 580 as eGPU amdgpu: gpu post error! bugzilla-daemon
2018-10-23 14:25 ` bugzilla-daemon
2018-10-23 16:00 ` bugzilla-daemon
2018-10-23 16:00 ` bugzilla-daemon
2018-10-23 20:08 ` bugzilla-daemon
2018-10-24 6:24 ` bugzilla-daemon [this message]
2018-10-24 20:44 ` bugzilla-daemon
2018-10-25 1:13 ` bugzilla-daemon
2018-10-25 1:15 ` bugzilla-daemon
2018-10-25 1:34 ` bugzilla-daemon
2018-10-25 2:12 ` bugzilla-daemon
2018-10-25 2:16 ` bugzilla-daemon
2018-10-25 3:06 ` bugzilla-daemon
2018-10-25 3:21 ` bugzilla-daemon
2018-10-25 7:05 ` bugzilla-daemon
2018-10-25 14:56 ` bugzilla-daemon
2018-10-25 15:01 ` bugzilla-daemon
2018-10-25 15:02 ` bugzilla-daemon
2018-10-25 15:07 ` bugzilla-daemon
2018-10-25 15:11 ` bugzilla-daemon
2018-10-25 15:12 ` bugzilla-daemon
2018-10-25 15:12 ` bugzilla-daemon
2018-10-25 15:13 ` bugzilla-daemon
2018-10-25 20:05 ` bugzilla-daemon
2018-10-26 4:42 ` bugzilla-daemon
2018-10-26 5:11 ` bugzilla-daemon
2018-10-26 5:14 ` bugzilla-daemon
2018-10-26 5:15 ` bugzilla-daemon
2018-10-26 5:30 ` bugzilla-daemon
2018-10-26 10:35 ` bugzilla-daemon
2018-10-26 16:49 ` bugzilla-daemon
2018-11-29 22:54 ` bugzilla-daemon
2018-11-29 23:47 ` bugzilla-daemon
2018-11-30 1:26 ` bugzilla-daemon
2018-11-30 1:35 ` bugzilla-daemon
2018-11-30 1:43 ` bugzilla-daemon
2018-11-30 1:51 ` bugzilla-daemon
2019-01-09 21:05 ` bugzilla-daemon
2019-01-09 21:08 ` bugzilla-daemon
2019-01-09 21:09 ` bugzilla-daemon
2019-01-09 21:10 ` bugzilla-daemon
2019-01-09 21:13 ` bugzilla-daemon
2019-01-09 22:26 ` bugzilla-daemon
2019-03-29 10:01 ` bugzilla-daemon
2019-03-29 10:06 ` bugzilla-daemon
2019-03-29 13:00 ` bugzilla-daemon
2019-03-29 13:10 ` bugzilla-daemon
2019-03-29 13:56 ` bugzilla-daemon
2019-03-29 16:31 ` bugzilla-daemon
2019-03-29 17:43 ` bugzilla-daemon
2019-03-30 11:42 ` bugzilla-daemon
2019-03-30 11:44 ` bugzilla-daemon
2019-03-30 11:51 ` bugzilla-daemon
2019-04-01 16:14 ` bugzilla-daemon
2019-04-19 19:46 ` bugzilla-daemon
2019-04-25 0:18 ` bugzilla-daemon
2019-04-25 0:18 ` bugzilla-daemon
2019-04-25 0:19 ` bugzilla-daemon
2019-11-02 9:13 ` bugzilla-daemon
2019-11-02 9:15 ` bugzilla-daemon
2019-11-02 9:37 ` bugzilla-daemon
2019-11-02 9:39 ` [Bug 108521] RX 580 / Vega56 " bugzilla-daemon
2019-11-20 7:53 ` 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-108521-502-qPXOL03chC@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).