From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110717] [Regression][bisected] Patch: update buffer descriptors ... causes hangs
Date: Mon, 20 May 2019 16:37:19 +0000 [thread overview]
Message-ID: <bug-110717-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110717
Bug ID: 110717
Summary: [Regression][bisected] Patch: update buffer
descriptors ... causes hangs
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: gw.fossdev@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
With 78e35df52aa2f7d770f929a0866a0faa89c261a9 I see hangs on [AMD/ATI] Baffin
[Radeon RX 560D / Pro 450/455/460/555/560] (rev e5).
Specifically, when I run "Outlast" through a virgl/vtest setup with this
hardware on the host, the whole X-session hangs after the very first loading
screen. I can still log into the machine but even a reboot hangs and a reboot
can only be forced by ctrl-alt-sysrq-B (or turning the laptop on and off).
I'll try to get a host trace to add a bit more info here.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2561 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-05-20 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 16:37 bugzilla-daemon [this message]
2019-05-21 7:08 ` [Bug 110717] [Regression][bisected] Patch: update buffer descriptors ... causes hangs 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-110717-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox