All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79338] New: Something's broken after llvm's svn commit 209067
Date: Tue, 27 May 2014 23:21:45 +0000	[thread overview]
Message-ID: <bug-79338-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 79338
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Something's broken after llvm's svn commit 209067
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: j.suarez.agapito@gmail.com
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Something seems to have been broken in llvm 3.5 after svn revision 209067.

What I am experiencing is that the system is stable for desktop usage but after
a few minutes from launching a game (I have tried with CKII, Witcher 2,
Watelands 2, Cities in motion, Deadfall Adventures and Serious Sam 3) or just
after a few seconds after exiting the game the desktop freezes, the screen goes
black (can't switch to vt to kill the game/desktop session) and the system
becomes unresponsive. I'm afraid I cannot obtain a dmesg log due to that
unresponsiveness.

If a dmesg log is needed to know the system's specs, the following attachement
of another bug report may be of use:
https://bugs.freedesktop.org/attachment.cgi?id=97787

I am using a llvm ppa to install llvm 3.5 git. I've tried to compile llvm with
no luck, so I cannot bisect. However, I still have in /var/cache/apt/archives
the deb packages for svn revisions 209564, 209581 and 209600 and those
revisions hang the system in the way described above. So judging by the R600
llvm backend activity
(https://github.com/llvm-mirror/llvm/commits/master/lib/Target/R600) and my
experience with those svn .deb packages I still have in the apt cache, it seems
the culprit must be a commit after 16 May.

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

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

             reply	other threads:[~2014-05-27 23:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 23:21 bugzilla-daemon [this message]
2014-05-27 23:36 ` [Bug 79338] Something's broken after llvm's svn commit 209067 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
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@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.