From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93264] Tonga VM Faults since llvm ScheduleDAGInstrs: Rework schedule graph builder.
Date: Tue, 08 Dec 2015 22:12:14 +0000 [thread overview]
Message-ID: <bug-93264-502-Ce7v5EHswk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93264-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1649 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93264
--- Comment #3 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Time to document some information I've gathered.
I can now confirm that Mesa has nothing to do with it. Something must have gone
wrong with my builds initially, sorry for having caused confusion.
I captured an apitrace for better reproducibility[0] and ran it with shader
dumps enabled and flushing after each draw call in the "interesting" region.
I am going to attach the R600_DEBUG=check_vm dump which I've cross-referenced
with R600_DEBUG=vm to obtain the shaders that were active during the draw call
(file names with prefix llvm-c0a189c.mesa-caf12bebd). I then matched the
shaders to those dumped by a run with a good version of LLVM (commit just
before the bad one, file names with prefix llvm-26ddca1.mesa-caf12bebd).
Clearly, the LLVM changes caused some significant re-ordering of the
instruction schedule, and that somehow, surprisingly, seems to be responsible
for the VM faults.
Another aspect to note is that the shaders are compiled before draw call
174000, while the VM faults happen shortly after draw call 178000. This seems
to suggest that the shaders alone only cause VM faults in conjunction with some
other state. However, the VM faults have always happened in exactly the same
point so far, so it does appear to be deterministic.
[0] The demo always causes VM faults, so I'm not going to upload the giant
trace; however, the timing varies between runs, so it's cleaner to reproduce
using a trace.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2500 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-08 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 18:24 [Bug 93264] Tonga VM Faults since llvm ScheduleDAGInstrs: Rework schedule graph builder bugzilla-daemon
2015-12-07 1:16 ` bugzilla-daemon
2015-12-07 22:32 ` bugzilla-daemon
2015-12-08 22:12 ` bugzilla-daemon [this message]
2015-12-08 22:13 ` bugzilla-daemon
2015-12-08 22:13 ` bugzilla-daemon
2015-12-08 22:14 ` bugzilla-daemon
2015-12-08 22:14 ` bugzilla-daemon
2015-12-08 22:14 ` bugzilla-daemon
2015-12-08 22:15 ` bugzilla-daemon
2015-12-08 22:54 ` bugzilla-daemon
2015-12-09 8:19 ` bugzilla-daemon
2015-12-14 14:09 ` bugzilla-daemon
2015-12-14 18:38 ` bugzilla-daemon
2015-12-19 1:41 ` bugzilla-daemon
2015-12-19 10:38 ` 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-93264-502-Ce7v5EHswk@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