From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106259] [bisected] UVD hangs system on Vega10 linux-4.17
Date: Fri, 04 May 2018 05:52:05 +0000 [thread overview]
Message-ID: <bug-106259-502-rNlJXCL8OM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106259-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106259
--- Comment #2 from James Harvey <lothmordor@gmail.com> ---
Hi Christian, thanks for taking the time to look at this.
I'm seeing this issue on the mainline linux-4.17 release candidates. I skipped
testing rc1, ran the bisect after seeing this on rc2, then tested
http://cgit.freedesktop.org/~agd5f/linux/?h=drm-fixes-4.17 prior to the rc3
release, just in case it was already fixed. Still present on rc3.
In order to bisect, I did need to cherrypick
[fdb401d03d311399d844b9f23ec5ab98a2811f58] drm/amd/display: Fix multiple
definitions of handle_crc_irq, otherwise I would get linker errors.
I'm using the firmware from git.kernel.org dated 2018-04-16.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1681 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-05-04 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:15 [Bug 106259] [bisected] UVD hangs system on Vega10 linux-4.17 bugzilla-daemon
2018-05-03 17:32 ` bugzilla-daemon
2018-05-04 5:52 ` bugzilla-daemon [this message]
2018-05-09 19:34 ` bugzilla-daemon
2018-05-09 21:33 ` bugzilla-daemon
2018-06-05 0:41 ` bugzilla-daemon
2018-06-17 4:42 ` 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-106259-502-rNlJXCL8OM@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