radeon flooding "flip queue failed" in Xorg and system log

Mon Dec 4 16:38:20 UTC 2023

Hi Chrisitan,

you are right, after bumping the memory in BIOS the error goes away. Still would be nice if the error would point to "out of VMem" or something.

Best Regards
Christian König <ckoenig.leichtzumerken at gmail.com> schrieb am Montag, 4. Dezember 2023 um 16:18:

> Am 02.12.23 um 20:00 schrieb smesgr:
>
>> Hi,
>>
>> I have installed Debian 12 on my old Fujitsu S920 with AMD GX-424CC.
>> After the installation completed, my logs are flooded by the following error messages:
>>
>> dmesg:
>> [ 967.869183] radeon 0000:00:01.0: 000000003ba3c813 pin failed
>> [ 967.869212] [drm:radeon_crtc_page_flip_target [radeon]] *ERROR* failed to pin new rbo buffer before flip
>> [ 967.886254] radeon 0000:00:01.0: 0000000051be2216 pin failed
>> [ 967.886282] [drm:radeon_crtc_page_flip_target [radeon]] *ERROR* failed to pin new rbo buffer before flip
>> [ 967.907984] radeon 0000:00:01.0: 000000003ba3c813 pin failed
>> [ 967.908014] [drm:radeon_crtc_page_flip_target [radeon]] *ERROR* failed to pin new rbo buffer before flip
>> [ 967.925551] radeon 0000:00:01.0: 0000000051be2216 pin failed [ 967.925580] [drm:radeon_crtc_page_flip_target [radeon]] *ERROR* failed to pin new rbo buffer before flip
>>
>> Xorg.log
>> [ 47.777] (WW) RADEON(0): flip queue failed: Invalid argument
>> [ 47.777] (WW) RADEON(0): Page flip failed: Invalid argument [ 47.777] (EE) RADEON(0): present flip failed
>>
>> lspci:
>> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] (rev 01) (prog-if 00 [VGA controller])
>> Subsystem: Fujitsu Technology Solutions Mullins [Radeon R4/R5 Graphics]
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>> Latency: 0, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 35
>> Region 0: Memory at f8000000 (64-bit, prefetchable) [size=64M]
>> Region 2: Memory at fc000000 (64-bit, prefetchable) [size=8M]
>> Region 4: I/O ports at f000 [size=256]
>> Region 5: Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
>> Expansion ROM at 000c0000 [disabled] [size=128K]
>> Capabilities: [48] Vendor Specific Information: Len=08 <?>
>> Capabilities: [50] Power Management version 3
>> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>> Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
>> DevCap: MaxPayload 256 bytes, PhantFunc 0
>> ExtTag+ RBE+ FLReset-
>> DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
>> RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
>> MaxPayload 256 bytes, MaxReadReq 512 bytes
>> DevSta: CorrErr- NonFatalErr+ FatalErr- UnsupReq+ AuxPwr- TransPend-
>> DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
>> 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
>> EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
>> FRS-
>> AtomicOpsCap: 32bit- 64bit- 128bitCAS-
>> DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled,
>> AtomicOpsCtl: ReqEn-
>> Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
>> Address: 00000000fee08004 Data: 0023
>> Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
>> Capabilities: [270 v1] Secondary PCI Express
>> LnkCtl3: LnkEquIntrruptEn- PerformEqu-
>> LaneErrStat: 0
>> Capabilities: [2b0 v1] Address Translation Service (ATS)
>> ATSCap: Invalidate Queue Depth: 00
>> ATSCtl: Enable-, Smallest Translation Unit: 00
>> Capabilities: [2c0 v1] Page Request Interface (PRI)
>> PRICtl: Enable- Reset-
>> PRISta: RF- UPRGI- Stopped+
>> Page Request Capacity: 00000020, Page Request Allocation: 00000000
>> Capabilities: [2d0 v1] Process Address Space ID (PASID)
>> PASIDCap: Exec+ Priv+, Max PASID Width: 10
>> PASIDCtl: Enable- Exec- Priv-
>> Kernel driver in use: radeon  Kernel modules: radeon, amdgpu
>>
>> I'm a bit confused. Is this an kernel issue, Xorg issue or something else?
>
> Well, what is connected to the GPU? E.g. what monitor, projector or other display device do you use?
>
> What happens is that only 64MiB is assigned to the device and for some reason a process (maybe the compositor?) Is trying to do double or triple buffering and doesn't has enough memory for that.
>
> So it falls back to single buffering, that might work but will probably not look as good and you see tons of error messages.
>
> You most likely can go into the BIOS and reserve more memory to the GPU (it will just be stolen from system memory).
>
> Regards,
> Christian.
>
>> kernel:
>> Linux debian 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux
>>
>> Xorg:
>> [ 33.144]
>> X.Org X Server 1.21.1.7
>> X Protocol Version 11, Revision 0
>> [ 33.144] Current Operating System: Linux debian 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64
>> [ 33.144] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=4101c568-e073-42f4-8dfe-08373fceb13c ro quiet
>> [ 33.144] xorg-server 2:21.1.7-3 (https://www.debian.org/support)
>> [ 33.144] Current version of pixman: 0.42.2
>> [ 33.144] Before reporting problems, check http://wiki.x.org  to make sure that you have the latest version.
>>
>> I searched bug tracker and could only find this issue: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/-/issues/180 but I don't have a black screen. The system is rather sluggish but seems to work.
>> I did try older version of Debian back to 10.13. All have this issue. I'm very sure the eLux which came with the box did not have this.
>>
>> Any hints where to go next is very appreciated.
>>
>> Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20231204/9b2b0dec/attachment.htm>