Bug 90926

Summary:

Unusable GPU

Product:

DRI

Reporter:

Artivision <artivision3>

Component:

DRM/Radeon

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED MOVED

QA Contact:

Severity:

blocker

Priority:

high

Version:

XOrg git

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xorg.0.log	none
kernel.log	none
gpu-manager.log	none

Description Artivision 2015-06-10 15:59:58 UTC

Laptop with A6-6310 CPU and R5-M230 dedicated GPU. When using DRI_PRIME=1 the DGPU hangs in "power level 4" at 850mhz. It doesn't hang in "power level 0" at 300mhz. Disable DPM doesn't solve the problem. Disable Dynamic_Frequency_Scaling and start at 850mhz doesn't solve the problem. Kernel version, DRI version, Mesa version "Oibaf PPA or not", composition level (GL, XRender, or not), Apps 32-64bit, they don't make a difference. Everything hangs and so i cannot take terminal output from the almost all Apps. Wine hangs alone, but the terminal doesn't show any errors and then i have to close the terminal to kill Wine window. PCSX2 shows:

radeon: size : 128 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x000000000553a000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 128 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x000000000553a000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 128 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x000000000553a000
radeon: Failed to allocate virtual address for buffer:
radeon: size : 128 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
radeon: va : 0x000000000553a000

Configuration:

$ sudo cat /var/log/Xorg.0.log | grep -i dri3
[ 20.305] (**) RADEON(0): Option "DRI3" "on"
[ 23.069] (**) RADEON(G0): Option "DRI3" "on"
[ 23.076] (**) RADEON(G0): DRI3 enabled
[ 23.210] (**) RADEON(0): DRI3 enabled

$ xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x74 cap: 0x9, Source Output, Sink Offload crtcs: 2 outputs: 3 associated providers: 2 name:radeon
Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon
Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon

$ DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Gallium 0.4 on AMD HAINAN

Comment 1 Michel Dänzer 2015-06-11 05:33:03 UTC

Please attach the /var/log/Xorg.0.log file and the output of dmesg, preferably captured after the problem occurred.

Comment 2 Artivision 2015-06-13 15:33:41 UTC

Created attachment 116476 [details]
Xorg.0.log

Comment 3 Artivision 2015-06-13 15:39:49 UTC

Nothing has been logged into /var/log/dmesg. Do you need "dmesg | grep -i 'something'"?

Comment 4 Michel Dänzer 2015-06-15 01:19:35 UTC

(In reply to Artivision from comment #3)
> Nothing has been logged into /var/log/dmesg.

How about /var/log/kern.log*?

> Do you need "dmesg | grep -i 'something'"?

Just the unfiltered output of dmesg, if the above doesn't help. Might be worth capturing that once already before reproducing the problem, in case doing so fills up the kernel message ring buffer.

Comment 5 Artivision 2015-06-15 14:42:42 UTC

Created attachment 116518 [details]
kernel.log

Comment 6 Artivision 2015-06-15 14:43:17 UTC

Created attachment 116519 [details]
gpu-manager.log

Comment 7 Artivision 2015-06-15 14:44:02 UTC

I hope those help. If not i need further instructions.

Comment 8 Artivision 2015-06-16 22:15:26 UTC

Officially the Dgpu works fine at power_level_2 at 400mhz, if i force "battery" level. There is no way to test power_level_3. Finally, before or after the game is start, if i force "performance", terminal shows power_level_4 and 850mhz for only two seconds and everything hangs.

Comment 9 Martin Peres 2019-11-19 09:05:26 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/619.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.