From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204611] amdgpu error scheduling IBs when waking from sleep
Date: Mon, 26 Aug 2019 23:47:21 +0000 [thread overview]
Message-ID: <bug-204611-2300-JMaPCbKQq3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204611-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204611
--- Comment #2 from tones111@hotmail.com ---
The problem is after v5.1, and before v5.2. It's very reproducible on v5.2 but
might be less frequent as the bisect progresses. Attempts have driven me into
the weeds, but I'm still trying.
It looks like another user reported the same issue here:
https://bugzilla.kernel.org/show_bug.cgi?id=204227
During my bisect I was seeing visual artifacts without the lockup so I believe
they're separate issues.
--
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:[~2019-08-26 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 20:32 [Bug 204611] New: amdgpu error scheduling IBs when waking from sleep bugzilla-daemon
2019-08-24 0:33 ` [Bug 204611] " bugzilla-daemon
2019-08-26 3:16 ` bugzilla-daemon
2019-08-26 23:47 ` bugzilla-daemon [this message]
2019-09-16 0:44 ` bugzilla-daemon
2019-10-02 1:13 ` bugzilla-daemon
2019-10-06 13:20 ` bugzilla-daemon
2019-10-06 13:21 ` bugzilla-daemon
2020-04-08 14:52 ` bugzilla-daemon
2020-05-22 21:09 ` bugzilla-daemon
2020-05-24 11:41 ` bugzilla-daemon
2020-05-24 17:19 ` bugzilla-daemon
2020-06-14 18:27 ` bugzilla-daemon
2022-01-29 19:55 ` bugzilla-daemon
2022-01-29 19:59 ` bugzilla-daemon
2022-01-30 2:39 ` 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-204611-2300-JMaPCbKQq3@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).