From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103489] [Regression bisected]: vblank time outs and machine hangs on RX560 drm-next-4.15-dc
Date: Fri, 27 Oct 2017 17:24:40 +0000 [thread overview]
Message-ID: <bug-103489-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103489
Bug ID: 103489
Summary: [Regression bisected]: vblank time outs and machine
hangs on RX560 drm-next-4.15-dc
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: oschowa@web.de
Created attachment 135115
--> https://bugs.freedesktop.org/attachment.cgi?id=135115&action=edit
dmesg
Running the most recent code of agd5f/drm-next-4.15-dc leads to dmesg spam
about vblank time outs (see attachment) and eventual full machine hangs when a
4k screen is connected to my RX560. The maching does not hang if only a 1080p
screen is connected and it was running fine on commit
d7205d5c0f2b09d900231de9026b97105c37d343.
Bisecting produced d050f8ed14494ea23c6e10b5893010946ef0f78b as the first bad
commit, although on this commit the machine hangs immediatly after boot, so it
might be a different issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2656 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 reply other threads:[~2017-10-27 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 17:24 bugzilla-daemon [this message]
2017-10-30 10:08 ` [Bug 103489] [Regression bisected]: vblank time outs and machine hangs on RX560 drm-next-4.15-dc bugzilla-daemon
2017-10-30 18:45 ` bugzilla-daemon
2017-11-05 2:01 ` bugzilla-daemon
2017-11-30 23:00 ` 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-103489-502@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 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.