From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208981] trace with B550I AORUS PRO AX and AMD Ryzen 5 PRO 4650G
Date: Fri, 16 Oct 2020 08:36:37 +0000 [thread overview]
Message-ID: <bug-208981-2300-K0Dy4j79Qn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208981-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208981
--- Comment #9 from florian.laroche@googlemail.com ---
Hello,
Am Mi., 14. Okt. 2020 um 11:44 Uhr schrieb
<bugzilla-daemon@bugzilla.kernel.org>:
> - Kernel 5.8.14 and 5.9 with mostly Gentoo kernel config
> - AMD Ryzen 7 PRO 4750G CPU+iGPU
> - ASRock A520M-ITX/ac mainboard + ECC UDIMM memory
>
> The trace mentioned above disappeared when I updated BIOS (v. 1.20 from
> 2020/9/18, it contains AGESA 1.0.8.0). However, I'm still not able to run
> ROCm
I have updated my motherboard Gigabyte B550I AORUS PRO AX to
BIOS F10 from 09/18/2020 with AMD AGESA ComboV2 1.0.8.1.
The trace is still present, so this issue is still open for me.
> OpenCL (tried various versions, including 3.7 and 3.8), system either hangs,
> or
> (if the program is killed early) dmesg shows
>
> Evicting PASID 0x8001 queues
>
> BTW, clinfo causes GPU resets, and leaves 99% GPU utilization, while dmesg
> shows something like
>
> qcm fence wait loop timeout expired
> The cp might be in an unrecoverable state due to an unsuccessful queues
> preemption
> amdgpu: Failed to evict process queues
> amdgpu: Failed to quiesce KFD
> amdgpu 0000:07:00.0: amdgpu: GPU reset begin!
> [drm] free PSP TMP buffer
> amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
> ...(and similarly for kernel 5.9.0)
>
> It is probably an off-topic, but it seems to be related to amdgpu driver, and
> I
> don't know how to move forward (and somebody reported that ROCk 3.7 driver
> works well with APU Renoir).
Seems this is all unrelated to my bug-report.
best regards,
Florian La Roche
--
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:[~2020-10-16 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 19:03 [Bug 208981] New: trace with B550I AORUS PRO AX and AMD Ryzen 5 PRO 4650G bugzilla-daemon
2020-08-20 19:08 ` [Bug 208981] " bugzilla-daemon
2020-08-20 19:28 ` bugzilla-daemon
2020-08-20 19:29 ` bugzilla-daemon
2020-09-06 0:43 ` bugzilla-daemon
2020-09-06 8:14 ` bugzilla-daemon
2020-09-12 9:44 ` bugzilla-daemon
2020-10-07 7:39 ` bugzilla-daemon
2020-10-14 9:44 ` bugzilla-daemon
2020-10-16 8:36 ` bugzilla-daemon [this message]
2021-08-04 13:19 ` 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-208981-2300-K0Dy4j79Qn@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.