All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104192] [amdgpu][VEGA10] regular lockups with VM_L2_PROTECTION_FAULT_STATUS
Date: Mon, 11 Dec 2017 12:52:28 +0000	[thread overview]
Message-ID: <bug-104192-502-R5730Hq0pG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104192-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 497 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104192

--- Comment #10 from Tom Englund <tomenglund26@gmail.com> ---
(In reply to Michel Dänzer from comment #9)
> FWIW, I bisected some piglit regressions to LLVM SVN r319894.

thanks, that gave me some starting points to bisecting, narrowed things down
now to where r319882 works while r319894 freezes. starting to look like the
same regression you are facing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1390 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

  parent reply	other threads:[~2017-12-11 12:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 13:13 [Bug 104192] [amdgpu][VEGA10] regular lockups with VM_L2_PROTECTION_FAULT_STATUS bugzilla-daemon
2017-12-10 19:17 ` bugzilla-daemon
2017-12-10 22:58 ` bugzilla-daemon
2017-12-10 23:01 ` bugzilla-daemon
2017-12-10 23:16 ` bugzilla-daemon
2017-12-11  6:10 ` bugzilla-daemon
2017-12-11  7:16 ` bugzilla-daemon
2017-12-11  7:39 ` bugzilla-daemon
2017-12-11  7:54 ` bugzilla-daemon
2017-12-11 10:48 ` bugzilla-daemon
2017-12-11 12:52 ` bugzilla-daemon [this message]
2017-12-11 13:22 ` bugzilla-daemon
2017-12-12 16:57 ` bugzilla-daemon
2017-12-12 18:17 ` 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-104192-502-R5730Hq0pG@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.