From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94874] radeon: Failed to allocate virtual address for buffer
Date: Fri, 08 Apr 2016 20:07:38 +0000 [thread overview]
Message-ID: <bug-94874-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3616 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94874
Bug ID: 94874
Summary: radeon: Failed to allocate virtual address for buffer
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: paulo.miguel.dias@gmail.com
with mesa git after 2abe4f8d7dcdcff75c28958e1a691ebf6cdee1ac, radeon is failing
intermittently, with the following errors:
DRI_PRIME=1 glxgears
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x0000000000800000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x0000000000800000
radeonsi: Failed to create a context.
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x0000000000800000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x0000000000800000
radeon: Failed to deallocate virtual address for buffer:
radeon: size : 65536 bytes
radeon: va : 0x0000000000800000
radeonsi: Failed to create a context.
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 30
Current serial number in output stream: 32
dmesg:
[ 999.461532] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[ 999.461537] [drm] PCIE gen 2 link speeds already enabled
[ 999.468703] [drm] PCIE GART of 2048M enabled (table at 0x00000000002E8000).
[ 999.468827] radeon 0000:03:00.0: WB enabled
[ 999.468829] radeon 0000:03:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0xffff8801a322bc00
[ 999.468831] radeon 0000:03:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0xffff8801a322bc04
[ 999.468832] radeon 0000:03:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0xffff8801a322bc08
[ 999.468834] radeon 0000:03:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0xffff8801a322bc0c
[ 999.468835] radeon 0000:03:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0xffff8801a322bc10
[ 999.470457] radeon 0000:03:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc90001435a18
[ 999.480817] radeon 0000:03:00.0: VCE init error (-22).
[ 1000.212739] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=0xCAFEDEAD)
[ 1000.212764] [drm:si_resume [radeon]] *ERROR* si startup failed on resume
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4849 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-04-08 20:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:07 bugzilla-daemon [this message]
2016-04-08 20:10 ` [Bug 94874] radeon: Failed to allocate virtual address for buffer bugzilla-daemon
2016-04-08 21:24 ` bugzilla-daemon
2016-04-08 21:25 ` bugzilla-daemon
2016-04-08 23:35 ` bugzilla-daemon
2016-04-15 16:40 ` bugzilla-daemon
2016-04-17 1:55 ` bugzilla-daemon
2016-04-19 6:22 ` bugzilla-daemon
2016-04-20 2:52 ` bugzilla-daemon
2016-04-20 2:52 ` bugzilla-daemon
2016-04-20 2:53 ` bugzilla-daemon
2016-04-20 2:54 ` bugzilla-daemon
2016-04-20 2:57 ` bugzilla-daemon
2016-04-20 3:05 ` bugzilla-daemon
2016-04-20 3:14 ` bugzilla-daemon
2016-04-20 3:14 ` bugzilla-daemon
2016-04-25 17:18 ` bugzilla-daemon
2016-04-25 17:26 ` 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-94874-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.