From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82455] Failed to allocate virtual address for buffer
Date: Fri, 15 Aug 2014 07:17:46 +0000 [thread overview]
Message-ID: <bug-82455-502-ZGIKukI6em@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82455-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82455
--- Comment #10 from charlie <407883775@qq.com> ---
Created attachment 104657
--> https://bugs.freedesktop.org/attachment.cgi?id=104657&action=edit
detail
Our system PAGE_SIZE is 8k, but the GPU PAGE_SIZE is 4k. I have changed the
mesa radeonsi driver memory 8K alignment . So, the virtual address allocate
conflict disappear . But the new problem is come out .
The log message is :
[ 3574.344456] radeon 0000:01:00.0: GPU fault detected: 147 0x01424802
[ 3574.344481] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x0002020A
[ 3574.344499] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x02048002
[ 3574.344518] VM fault (0x02, vmid 1) at page 131594, read from TC (72)
[ 3574.344543] radeon 0000:01:00.0: GPU fault detected: 147 0x01424802
[ 3574.344563] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR
0x00000000
[ 3574.344583] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x00000000
[ 3574.344601] VM fault (0x00, vmid 0) at page 0, read from unknown (0)
what's fault with it? The GPU cannot detected?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2052 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
next prev parent reply other threads:[~2014-08-15 7:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 9:16 [Bug 82455] New: Failed to allocate virtual address for buffer bugzilla-daemon
2014-08-11 9:22 ` [Bug 82455] " bugzilla-daemon
2014-08-11 9:36 ` bugzilla-daemon
2014-08-11 11:47 ` bugzilla-daemon
2014-08-11 11:55 ` bugzilla-daemon
2014-08-12 1:20 ` bugzilla-daemon
2014-08-12 1:22 ` bugzilla-daemon
2014-08-12 1:26 ` bugzilla-daemon
2014-08-12 1:33 ` bugzilla-daemon
2014-08-14 9:07 ` bugzilla-daemon
2014-08-15 2:29 ` bugzilla-daemon
2014-08-15 7:17 ` bugzilla-daemon [this message]
2014-08-19 9:23 ` bugzilla-daemon
2014-08-19 9:59 ` bugzilla-daemon
2014-08-19 10:01 ` bugzilla-daemon
2014-08-19 13:37 ` bugzilla-daemon
2014-08-19 14:16 ` bugzilla-daemon
2014-08-20 1:54 ` bugzilla-daemon
2014-08-20 2:43 ` bugzilla-daemon
2014-08-20 3:38 ` bugzilla-daemon
2014-08-20 13:23 ` bugzilla-daemon
2014-08-21 9:35 ` bugzilla-daemon
2014-08-27 3:36 ` bugzilla-daemon
2014-08-27 6:26 ` bugzilla-daemon
2014-08-27 8:12 ` bugzilla-daemon
2014-08-27 8:15 ` bugzilla-daemon
2014-08-27 8:19 ` bugzilla-daemon
2014-08-27 9:13 ` bugzilla-daemon
2014-08-28 2:46 ` bugzilla-daemon
2014-08-28 3:31 ` bugzilla-daemon
2014-08-28 13:58 ` bugzilla-daemon
2014-08-29 1:18 ` bugzilla-daemon
2014-08-29 1:19 ` bugzilla-daemon
2014-09-01 6:43 ` bugzilla-daemon
2014-09-15 8:25 ` bugzilla-daemon
2014-09-17 6:57 ` bugzilla-daemon
2015-08-02 10:53 ` [Bug 82455] [SPARC] " bugzilla-daemon
2018-08-31 6:17 ` 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-82455-502-ZGIKukI6em@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