dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79338] Something's broken after llvm's svn commit 209067
Date: Thu, 29 May 2014 21:33:40 +0000	[thread overview]
Message-ID: <bug-79338-502-Qpq63C4QPX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79338-502@http.bugs.freedesktop.org/>


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

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

--- Comment #7 from José Suárez <j.suarez.agapito@gmail.com> ---
Hmmm... the problem actually seems to not be related to llvm.

I managed to obtain a crash dmesg log (see attachment above) while using llvm
3.5 svn 209067 which in theory was a good llvm svn revision. That made me
rethink the cause of the problem and now I think the problem is coming from the
kernel.

So I tried linux 3.14 (3.14.0-031400-generic #201403310035), which I had used
before the 3.15 rc's started to come out. The thing is that with llvm 3.5 svn
209708 and linux 3.14 the gpu does not lock up. This svn 209708 llvm revision
was making the gpu hang quite fast with linux 3.15-rc6 when launching a game.

GPU hang with 3.15-rc6 with llvm revs higher than 209067 was quite frequent, so
could this be that those higher revs are hitting a bug in linux 3.15-rc6?

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

[-- Attachment #1.2: Type: text/html, Size: 1788 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:[~2014-05-29 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 23:21 [Bug 79338] New: Something's broken after llvm's svn commit 209067 bugzilla-daemon
2014-05-27 23:36 ` [Bug 79338] " bugzilla-daemon
2014-05-27 23:37 ` bugzilla-daemon
2014-05-28  2:58 ` bugzilla-daemon
2014-05-28 10:09 ` bugzilla-daemon
2014-05-29  8:19 ` bugzilla-daemon
2014-05-29 21:22 ` bugzilla-daemon
2014-05-29 21:33 ` bugzilla-daemon [this message]
2014-05-29 22:22 ` 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-79338-502-Qpq63C4QPX@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