From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer
Date: Fri, 15 Sep 2017 20:01:29 +0000 [thread overview]
Message-ID: <bug-102800-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4711 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102800
Bug ID: 102800
Summary: DRI_PRIME regression- radeon: Failed to allocate
virtual address for buffer
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: higuita@gmx.net
Using a ubuntu 17.04 with a kernel 4.13.2, mesa 1.3-git and libdrm 2.4.83 on a
lenovo thinkpad S440 with a intel haswell and a radeon HD8670M/8690M
doing this commands i get a error:
+ xrandr --setprovideroffloadsink 0x3f 0x66
+ 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 : 0x800000
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 : 0x800000
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 : 0x800000
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 : 0x800000
radeonsi: Failed to create a context.
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 31
Current serial number in output stream: 33
In the dmesg, i can see this:
[ 1059.004670] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for
more than 5secs aborting
[ 1059.004693] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing 746C (len 237, WS 0, PS 4) @ 0x747A
[ 1059.004703] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing 6E04 (len 74, WS 0, PS 8) @ 0x6E39
[ 1059.012106] [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0
[ 1059.012110] [drm] PCIE gen 2 link speeds already enabled
[ 1059.448659] [UFW ALLOW] IN= OUT=wlan0 SRC=10.42.42.80 DST=140.172.138.79
LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=44245 DF PROTO=TCP SPT=50408 DPT=80
WINDOW=30498 RES=0x00 ACK FIN URGP=0
[ 1059.476638] radeon 0000:06:00.0: Wait for MC idle timedout !
[ 1059.708499] radeon 0000:06:00.0: Wait for MC idle timedout !
[ 1059.714600] [drm] PCIE GART of 2048M enabled (table at 0x0000000000040000).
[ 1059.714727] radeon 0000:06:00.0: WB enabled
[ 1059.714730] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr
0x0000000080000c00 and cpu addr 0xffff8c2c59b12c00
[ 1059.714731] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr
0x0000000080000c04 and cpu addr 0xffff8c2c59b12c04
[ 1059.714732] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr
0x0000000080000c08 and cpu addr 0xffff8c2c59b12c08
[ 1059.714732] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr
0x0000000080000c0c and cpu addr 0xffff8c2c59b12c0c
[ 1059.714733] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr
0x0000000080000c10 and cpu addr 0xffff8c2c59b12c10
[ 1060.424258] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=0xCAFEDEAD)
[ 1060.424283] [drm:si_resume [radeon]] *ERROR* si startup failed on resume
All this setup worked fine in a previous kernel versions, IIRC, 4.11 and below
and started to fail in 4.12 and above
I also notice that the dedicated card switch fron DynOff to DynPwr in
/sys/kernel/debug/vgaswitcheroo/switch for a few seconds when trying to run the
glxgears
Finally, If i boot the system with radeon.runpm=1, it works
Let me know if you need more logs
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6021 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:[~2017-09-15 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 20:01 bugzilla-daemon [this message]
2017-09-15 20:08 ` [Bug 102800] DRI_PRIME regression- radeon: Failed to allocate virtual address for buffer bugzilla-daemon
2017-09-15 20:16 ` bugzilla-daemon
2017-09-15 20:29 ` bugzilla-daemon
2017-09-15 20:30 ` bugzilla-daemon
2017-09-15 20:30 ` bugzilla-daemon
2017-10-04 15:58 ` bugzilla-daemon
2017-10-09 23:18 ` bugzilla-daemon
2017-10-10 13:21 ` bugzilla-daemon
2017-10-10 13:25 ` bugzilla-daemon
2017-10-10 23:50 ` bugzilla-daemon
2017-11-06 3:38 ` bugzilla-daemon
2017-11-13 20:12 ` bugzilla-daemon
2017-11-13 21:02 ` bugzilla-daemon
2017-11-17 2:04 ` bugzilla-daemon
2017-11-21 23:40 ` bugzilla-daemon
2017-11-24 22:22 ` bugzilla-daemon
2017-12-19 4:16 ` bugzilla-daemon
2018-01-11 23:14 ` bugzilla-daemon
2018-01-12 16:22 ` bugzilla-daemon
2018-01-17 18:21 ` bugzilla-daemon
2019-11-19 9:30 ` 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-102800-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox