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: Mon, 24 Feb 2014 22:38:36 +0000	[thread overview]
Message-ID: <bug-75005-502-4FyzXGxniI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75005-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Christoph Haag <haagch.christoph@googlemail.com> ---
Created attachment 94690
  --> https://bugs.freedesktop.org/attachment.cgi?id=94690&action=edit
GPU fault after it sort of works with patch from #3

Well.

At least initially it does not crash anymore. It does start now. Nice!

The problems begin very quickly after gameplay with GPU faults in the attached
dmesg. Amazingly it keeps running with decent FPS for some time while these GPU
faults are dumped into the log. But eventually the system will hard lockup (I
got to 160 MB log before the lockup so I arbitrarily trimmed after the first
few GPU fault messages).
This was with R600_DEBUG=nohyperz, by the way.



I have also once seen another segfault in radeonsi, but I didn't have debug
symbols at that time and haven't reproduced it with debug symbols now, because
the hard lockup after a few seconds of gameplay is a bit annoying when trying
to reproduce something. :)
Maybe I can give a better backtrace later, but maybe it's unrelated.

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

[-- Attachment #1.2: Type: text/html, Size: 2117 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-02-24 22:38 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 [this message]
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
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-4FyzXGxniI@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