Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

radeon-profile unable to fetch GPU memory data #14

Open
SleepyMario opened this issue Sep 30, 2018 · 1 comment
Open

radeon-profile unable to fetch GPU memory data #14

SleepyMario opened this issue Sep 30, 2018 · 1 comment

Comments

@SleepyMario
Copy link

SleepyMario commented Sep 30, 2018

Hello, first of all thanks for this great piece of work. This is truly a lifesaver.
At the moment I'm using the radeon-profile-daemon in conjunction with radeon-profile. I'm on Gentoo, and not using systemd (using openrc instead), so for now i'm just starting radeon-profile-daemon as the root user.

Almost everything seems to be working fine, apart from the GPU memory fetch. Also, when I just start radeon-profile as the root user (without the daemon) this error will not occur and everything works 100%. I personally have no idea what could be wrong, do you?

Below is the error it shows when starting radeon-profile in a terminal:

(The error just goes on forever with the same messages, I just pasted a part of it so you get an idea)

/dev/dri/renderD128: Permission denied
DRM_IOCTL_AMDGPU_INFO: Permission denied
Unable to lock the shared memory: "QSharedMemory::lock: unable to lock"
Unable to lock the shared memory: "QSharedMemory::lock: unable to lock"
DRM_IOCTL_AMDGPU_INFO: Permission denied
Unable to lock the shared memory: "QSharedMemory::lock: unable to lock"
DRM_IOCTL_AMDGPU_INFO: Permission denied
DRM_IOCTL_AMDGPU_INFO: Permission denied
nable to lock the shared memory: "QSharedMemory::lock: unable to lock"
DRM_IOCTL_AMDGPU_INFO: Permission denied
DRM_IOCTL_AMDGPU_INFO: Permission denied
Unable to lock the shared memory: "QSharedMemory::lock: unable to lock"
DRM_IOCTL_AMDGPU_INFO: Permission denied
DRM_IOCTL_AMDGPU_INFO: Permission denied
Unable to lock the shared memory: "QSharedMemory::lock: unable to lock"
DRM_IOCTL_AMDGPU_INFO: Permission denied

@PorcelainMouse
Copy link

Can anyone knowledgeable comment? This error still happening. Yet, sometimes, profile is able to report memory usage, which doesn't make sense. Why does it work sometimes and not other times?

Now, I'm getting massive amounts of repeat errors in the journal, too. That just started. I should at least be able to prevent that, but I don't know how.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@PorcelainMouse @SleepyMario and others