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 83416] [radeonsi] Serious Sam 3 lockup during its start
Date: Wed, 03 Sep 2014 10:25:05 +0000	[thread overview]
Message-ID: <bug-83416-502-CXIvlW9tGi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83416-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from smoki <smoki00790@gmail.com> ---
(In reply to comment #2)
> I get no lockup either, but I do see the same GPUVM protection faults:
> 
>  radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0FF00819
> 
> The FF bits make me suspect bits 32-4x of the GPUVM address are getting
> clobbered, maybe because of the LLVM backend generating invalid shader code.

 For me nothing new in dmesg, but there is something very interesting here
happen. When radeonsi.so is striped this trace segfault for me, if not striped
it pass fine no segfault, what that can be? Hmm...

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

[-- Attachment #1.2: Type: text/html, Size: 1567 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-09-03 10:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 21:15 [Bug 83416] New: [radeonsi] Serious Sam 3 lockup during its start bugzilla-daemon
2014-09-02 23:45 ` [Bug 83416] " bugzilla-daemon
2014-09-03  9:05 ` bugzilla-daemon
2014-09-03 10:09 ` bugzilla-daemon
2014-09-03 10:12 ` bugzilla-daemon
2014-09-03 10:25 ` bugzilla-daemon [this message]
2014-09-03 10:28 ` bugzilla-daemon
2014-09-03 10:53 ` bugzilla-daemon
2014-09-03 11:35 ` bugzilla-daemon
2014-09-03 12:21 ` bugzilla-daemon
2014-09-03 13:24 ` bugzilla-daemon
2014-09-03 14:18 ` bugzilla-daemon
2014-09-03 22:54 ` bugzilla-daemon
2014-09-04  1:50 ` bugzilla-daemon
2014-09-04  4:31 ` bugzilla-daemon
2014-09-04 15:21 ` bugzilla-daemon
2014-09-04 15:42 ` bugzilla-daemon
2014-09-04 16:06 ` bugzilla-daemon
2014-09-04 16:26 ` bugzilla-daemon
2014-11-18 15:44 ` bugzilla-daemon
2014-11-18 15:45 ` 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-83416-502-CXIvlW9tGi@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