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 75005] "Upvoid" segfault in radeonsi/llvm
Date: Sun, 13 Apr 2014 13:49:11 +0000	[thread overview]
Message-ID: <bug-75005-502-invcIqk0sA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75005-502@http.bugs.freedesktop.org/>


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

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

Christoph Haag <haagch.christoph@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #94690|0                           |1
        is obsolete|                            |

--- Comment #8 from Christoph Haag <haagch.christoph@googlemail.com> ---
Created attachment 97307
  --> https://bugs.freedesktop.org/attachment.cgi?id=97307&action=edit
dmesg with patched llvm

Sorry, I wasn't very active recently.

I'm not sure what you're asking for. In comment #4 there is a whole dmesg, but
I can add another one...

I am using linux 3.14 by now and recent mesa git, but with your branch of llvm.

I can maybe add a few details to the behavior:
When starting upvoid it displays a menu over a view of the game world. The gpu
faults start appearing in dmesg right when it starts displaying this. It
doesn't directly lockup and keeps rendering relatively well. When starting the
game I can walk and look around a bit and I noticed: When looking at the ground
the messages stop, but when looking in the distance, the messages are again
created, so I would think it's directly related to the complexity of the stuff
it is rendering.

After a while the game window stops reacting. At this point the game will take
up 100% "red" cpu time in htop and shortly after that the whole machine will
hard lockup.

I can't say if the lockup is because of excessive error logging or not. dmesg
--follow | pv > /dev/null says it's about 35 kilobyte/second.

The dmesg here is from starting the game, waiting a few seconds and then
killing it. When killing it early enough it doesn't seem to cause any problems,
seems to recover nicely.

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

[-- Attachment #1.2: Type: text/html, Size: 3343 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-04-13 13:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 22:08 [Bug 75005] New: "Upvoid" segfault in radeonsi/llvm bugzilla-daemon
2014-02-14 22:10 ` [Bug 75005] " bugzilla-daemon
2014-02-14 22:13 ` bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-24 17:48 ` bugzilla-daemon
2014-02-24 22:38 ` bugzilla-daemon
2014-03-03 19:54 ` bugzilla-daemon
2014-03-03 22:34 ` bugzilla-daemon
2014-03-31 15:13 ` bugzilla-daemon
2014-04-13 13:49 ` bugzilla-daemon [this message]
2014-04-13 13:54 ` bugzilla-daemon
2014-04-13 14:42 ` bugzilla-daemon
2014-04-28 20:52 ` bugzilla-daemon
2014-04-29 16:36 ` bugzilla-daemon
2014-04-29 21:37 ` bugzilla-daemon
2014-04-29 22:46 ` bugzilla-daemon
2014-05-16 19:29 ` bugzilla-daemon
2015-02-06  1:35 ` 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-75005-502-invcIqk0sA@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