All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90484] LLVM >=r237140 causes gpu lockups Spec Ops: The Line
Date: Mon, 18 May 2015 16:08:10 +0000	[thread overview]
Message-ID: <bug-90484-502-P3PginvE9n@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90484-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Arek Ruśniak <arek.rusi@gmail.com> ---
It's complicated a little bit more than i thought.
r237139 is affected too, but need more time(about 100-120 sec)to trigger, this
is why i didn't see it before. Now i've tried r230876 and time to trigger ~ 11
min. And a really dunno what interval should i take. 

But still trying.

Sylvain i will try it and give feedback to you. (and i have Cape Verde XT
(hd7770), I should buy Pitcairn but i was to stingy:)

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

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

  parent reply	other threads:[~2015-05-18 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 16:14 [Bug 90484] LLVM >=r237140 causes gpu lockups Spec Ops: The Line bugzilla-daemon
2015-05-16 18:51 ` bugzilla-daemon
2015-05-16 21:03 ` bugzilla-daemon
2015-05-18  3:14 ` bugzilla-daemon
2015-05-18 13:52 ` bugzilla-daemon
2015-05-18 16:08 ` bugzilla-daemon [this message]
2015-05-19  1:00 ` bugzilla-daemon
2015-05-19  7:44 ` bugzilla-daemon
2015-07-31  9:26 ` bugzilla-daemon
2015-07-31  9:26 ` 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-90484-502-P3PginvE9n@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.