Bug 110478 - AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
Summary: AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-20 21:44 UTC by cmdrrdo
Modified: 2019-11-19 09:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log (64.98 KB, text/plain)
2019-04-20 21:44 UTC, cmdrrdo
no flags Details

Description cmdrrdo 2019-04-20 21:44:24 UTC
Created attachment 144053 [details]
xorg log

Hi,

I'm using a Ryzen 3550H laptop with integrated Vega graphics and an additional Radeon 560. Whenever I boot the laptop with a screen connected to the HDMI port, the screen turns blank upon lxdm start and I can see these error messages in the Xorg log:

[   263.699] (II) AMDGPU(0): Setting screen physical size to 1524 x 571
[   263.716] (EE) AMDGPU(0): failed to set mode: Cannot allocate memory
[   263.716] (WW) AMDGPU(0): Failed to set mode on CRTC 0
[   263.817] (EE) AMDGPU(0): failed to set mode: Cannot allocate memory
[   263.817] (WW) AMDGPU(0): Failed to set mode on CRTC 1
[   263.887] (EE) AMDGPU(0): Failed to enable any CRTC


Kernel: is a self-built 5.0.9, but the same has happened with debian experimental 5.0.2, as well as the debian buster's 4.19.
xserver-xorg-video-amdgpu: 19.0.1-1

If HDMI is not connected, everything is working.
Comment 1 cmdrrdo 2019-04-21 13:58:03 UTC
I guess this could also be in dri->drm/amdgpu.

I'm not sure how to narrow it down, I've tried with breakpoints for drmModeSetCrtc and drmmode_set_mode_major but I'm not seeing anything that sticks out.
Comment 2 Michel Dänzer 2019-04-23 08:58:10 UTC
Yeah, this is a kernel issue. There's only a small amount of VRAM available, so the 5760x2160 framebuffer can't fit, and the kernel driver doesn't support scanout from system memory with Raven Ridge yet.

Meanwhile, if the amount of VRAM can be increased in the BIOS setup, try that.
Comment 3 cmdrrdo 2019-04-23 13:27:20 UTC


(In reply to Michel Dänzer from comment #2)
> Yeah, this is a kernel issue. There's only a small amount of VRAM available,
> so the 5760x2160 framebuffer can't fit, and the kernel driver doesn't
> support scanout from system memory with Raven Ridge yet.
> 
> Meanwhile, if the amount of VRAM can be increased in the BIOS setup, try
> that.

Thank you very much for the explanation and workaround suggestion. My choices on this laptop are "128M" or "Auto". I think I have to poke Asus about this, but: With Auto I do get 2048 as per dmesg and it's working.

So again, thank you. :)
Comment 4 Martin Peres 2019-11-19 09:19:39 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/754.


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.