From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98907] commit bf75ef3 causes Xorg lock-up
Date: Sun, 04 Dec 2016 20:07:05 +0000 [thread overview]
Message-ID: <bug-98907-502-zGC2o6fyFb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98907-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 697 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98907
--- Comment #3 from Hleb Valoshka <375gnu@gmail.com> ---
(In reply to Marek Olšák from comment #2)
> Would it be possible to run the game with "GALLIUM_DDEBUG=2000" set, wait
> for the hang, and attach the file created in ~/ddebug_dumps/ ?
When I had run it as "GALLIUM_DDEBUG=2000 ./bms.sh" it started like for the 1st
time and now I'm not able to reproduce this issue. Maybe it caches compiled
resources? Anyway I've tried 2 other Source powered games and they run without
issues as well. So it seems that you can close this ticket as unreproducible.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1539 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:[~2016-12-04 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 22:09 [Bug 98907] commit bf75ef3 causes Xorg lock-up bugzilla-daemon
2016-11-29 22:12 ` bugzilla-daemon
2016-11-30 0:10 ` bugzilla-daemon
2016-12-04 20:07 ` bugzilla-daemon [this message]
2016-12-04 22:41 ` bugzilla-daemon
2016-12-04 22:41 ` 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-98907-502-zGC2o6fyFb@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;
as well as URLs for NNTP newsgroup(s).