All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90266] Unigine Heaven 4.0 logging vm faults since radeon/llvm: Run LLVM's instruction combining pass
Date: Fri, 01 May 2015 11:03:37 +0000	[thread overview]
Message-ID: <bug-90266-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 90266
           Summary: Unigine Heaven 4.0 logging vm faults since
                    radeon/llvm: Run LLVM's instruction combining pass
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Related to 

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

Unlike valley I thought heaven 4.0 wasn't affected by above as it runs and
looks OK.

There is however an issue, again "fixed" by reverting mesa commit 

commit c6d79ed289a75f13c65f011be870f7e43a0fedc7
Author: Tom Stellard <thomas.stellard@amd.com>
Date:   Fri Apr 10 17:07:16 2015 +0000

    radeon/llvm: Run LLVM's instruction combining pass


This issue is thousands of lines of logging like below.

This happens with or without the llvm fix in the valley bug.

Will attach R600_DEBUG=ps,vs,gs with and without above mesa commit reverted.
The debug logs were done with todays llvm,mesa so the valley fix in in llvm.

The errors -

[ 7288.184664] VM fault (0x01, vmid 14) at page 185032279, read from TC (4)
[ 7288.184667] radeon 0000:01:00.0: GPU fault detected: 147 0x0afc0401
[ 7288.184668] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0B075E57
[ 7288.184670] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x1C004001
[ 7288.184671] VM fault (0x01, vmid 14) at page 185032279, read from TC (4)
[ 7288.184695] radeon 0000:01:00.0: GPU fault detected: 147 0x0afc0401
[ 7288.184696] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
0x0B075E57
[ 7288.184698] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x1C004001

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

[-- Attachment #1.2: Type: text/html, Size: 3610 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:[~2015-05-01 11:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 11:03 bugzilla-daemon [this message]
2015-05-01 11:06 ` [Bug 90266] Unigine Heaven 4.0 logging vm faults since radeon/llvm: Run LLVM's instruction combining pass bugzilla-daemon
2015-05-01 11:07 ` bugzilla-daemon
2015-05-01 21:12 ` bugzilla-daemon
2015-05-04 15:15 ` bugzilla-daemon
2015-05-04 16:28 ` bugzilla-daemon
2015-05-07 22:25 ` bugzilla-daemon
2015-05-08 11:06 ` bugzilla-daemon
2015-05-09 11:17 ` bugzilla-daemon
2015-05-12 19:26 ` bugzilla-daemon
2015-05-12 19:42 ` 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-90266-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.