You are not logged in.

#1 2016-10-29 12:58:38

akoww
Member
Registered: 2016-10-29
Posts: 2

PRIME GPU offloading as User

Hi Guys, I got some problems with GPU offloading on my Intel/Radeon notebook.
I get the problem when I run anything as a user but it works as root. Tried downgrade everthing to some older versions but it doen't work.
Seems like there are some problems with access rights somewhere but can't find them, maybe u know more.

xorg-server  1.18.4-1
xf86-video-intel 1:2.99.917+713+geb01cc5-1
xf86-video-ati 1:7.7.1-1
linux 4.8.4-1

DRI_PRIME=1 glxgears
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

% xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 5 associated providers: 0 name:Intel
Provider 1: id: 0x3f cap: 0x0 crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:06:00.0

% xrandr --setprovideroffloadsink 0x3f Intel
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  34 (RRSetProviderOffloadSink)
  Value in failed request:  0x3f
  Serial number of failed request:  16
  Current serial number in output stream:  17

% dmesg
[   83.921502] radeon 0000:06:00.0: WB enabled
[   83.921504] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88022212ac00
[   83.921505] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88022212ac04
[   83.921505] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88022212ac08
[   83.921506] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88022212ac0c
[   83.921507] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88022212ac10
[   84.622880] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
[   84.622921] [drm:si_resume [radeon]] *ERROR* si startup failed on resume

Offline

#2 2016-10-29 13:06:33

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: PRIME GPU offloading as User

Provider 1: id: 0x3f cap: 0x0 crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:06:00.0
[   84.622880] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
[   84.622921] [drm:si_resume [radeon]] *ERROR* si startup failed on resume

Doesn't look like access problems to me, but a driver problem .

post lspci -k , full dmesg and xorg log please.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2016-10-29 13:14:35

akoww
Member
Registered: 2016-10-29
Posts: 2

Re: PRIME GPU offloading as User

My Bad, doesn't even work as root.

dmesg - https://paste.xinu.at/jGg/
xorg.log - https://paste.xinu.at/Kd6Uk/
lspci  -nnk - https://paste.xinu.at/pqh/
//edit fixed link

Last edited by akoww (2016-10-29 13:27:58)

Offline

#4 2016-10-29 13:22:43

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: PRIME GPU offloading as User

Your lspci link points to xorg.log. Please post the output of 'lspci -nnk'.

Edit:
It's probably related to power management, I've seen something similar when giving the experimental amdgpu support a try why a drm-next kernel.

With the "normal" radeon driver things kind of work, but if I try to offload anything more demanding that glxgears I get a hang. Funny thing is if I unplug the charger before I try it works just fine, so I suspect the bios/fw is probably messing around with something it shouldn't and it's getting in the way of the driver and making things hang.

I'm seeing this on a Lenovo laptop but a different model, so at least the brand is the same, which might point to a common firmware behavior problem (assuming I'm correct in my assumption given the datapoints I have).

Last edited by R00KIE (2016-10-29 13:37:32)


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

Board footer

Powered by FluxBB