From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel)
Date: Fri, 01 Dec 2017 09:06:22 +0000 [thread overview]
Message-ID: <bug-104001-502-L1zvtgxcJB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104001-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 404 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104001
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
Does "it occurs on latest staging kernel" mean it doesn't happen with an
earlier staging kernel or with another kernel version? If so, can you provide
more details about what kernels it doesn't happen with?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1316 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:[~2017-12-01 9:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 20:53 [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel) bugzilla-daemon
2017-12-01 9:06 ` bugzilla-daemon [this message]
2017-12-01 9:18 ` bugzilla-daemon
2017-12-05 16:56 ` bugzilla-daemon
2017-12-06 20:13 ` bugzilla-daemon
2017-12-07 17:08 ` bugzilla-daemon
2017-12-15 17:43 ` bugzilla-daemon
2017-12-21 18:27 ` bugzilla-daemon
2017-12-21 18:28 ` bugzilla-daemon
2018-01-03 9:58 ` [Bug 104001] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=6582, last emitted seq=6584 bugzilla-daemon
2018-01-03 9:58 ` bugzilla-daemon
2018-01-03 10:00 ` [Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel) bugzilla-daemon
2018-01-03 10:07 ` bugzilla-daemon
2018-01-05 12:14 ` bugzilla-daemon
2018-01-06 1:18 ` bugzilla-daemon
2018-01-06 1:20 ` bugzilla-daemon
2018-01-06 3:44 ` bugzilla-daemon
2018-01-07 17:00 ` bugzilla-daemon
2018-01-17 17:51 ` bugzilla-daemon
2018-01-18 21:05 ` bugzilla-daemon
2018-01-19 8:47 ` bugzilla-daemon
2018-01-19 18:00 ` bugzilla-daemon
2018-02-04 15:34 ` bugzilla-daemon
2018-02-28 3:43 ` bugzilla-daemon
2018-02-28 3:44 ` bugzilla-daemon
2018-03-01 4:19 ` bugzilla-daemon
2018-03-01 4:21 ` bugzilla-daemon
2018-03-01 9:06 ` bugzilla-daemon
2018-03-01 18:42 ` bugzilla-daemon
2018-03-02 20:21 ` bugzilla-daemon
2018-03-02 20:22 ` bugzilla-daemon
2018-03-24 14:28 ` bugzilla-daemon
2018-04-21 0:36 ` bugzilla-daemon
2018-04-21 16:31 ` bugzilla-daemon
2018-04-27 21:57 ` bugzilla-daemon
2018-05-05 8:56 ` bugzilla-daemon
2018-05-05 8:58 ` bugzilla-daemon
2018-05-05 9:14 ` bugzilla-daemon
2018-05-05 9:17 ` bugzilla-daemon
2018-05-06 4:19 ` bugzilla-daemon
2018-05-06 17:50 ` bugzilla-daemon
2018-05-06 20:23 ` bugzilla-daemon
2018-05-07 18:04 ` 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-104001-502-L1zvtgxcJB@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