You are not logged in.

#1 2021-08-05 07:43:08

duyinthee
Member
Registered: 2015-06-14
Posts: 154

File 'radeon_ring_gfx' in directory '0' already present!

I use Arch + Awesome using xinitrc.
After the recent update, the followings are shown in the message of $ startx and dmesg.

[   66.785135] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[   66.785141] debugfs: File 'radeon_ring_cp1' in directory '0' already present!
[   66.785143] debugfs: File 'radeon_ring_cp2' in directory '0' already present!
[   66.785145] debugfs: File 'radeon_ring_dma1' in directory '0' already present!
[   66.785148] debugfs: File 'radeon_ring_dma2' in directory '0' already present!

Xorg session starts successfully and everything works fine.

What does it mean and is it an error or problem?
Is there anything what I am supposed to do?
Thanks in advance.

Offline

#2 2021-08-05 08:23:51

seth
Member
Registered: 2012-09-03
Posts: 25,035

Re: File 'radeon_ring_gfx' in directory '0' already present!

Something™ tries to create a node in /sys/kernel/debug/[likely dri/0] that already exists.
In and by itself that's meaningless, but might indicate a crash-restart of amdgpu/radeon - check dmesg or the system journal for related events.

Offline

#3 2021-08-06 21:39:02

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 93

Re: File 'radeon_ring_gfx' in directory '0' already present!

I have these messages since kernel 5.13.0 with small difference - directory is '1'.
Previous kernel versions were without these messages.
My DE is KDE Plasma (Xorg) and works OK.

Offline

#4 2021-08-07 03:20:20

duyinthee
Member
Registered: 2015-06-14
Posts: 154

Re: File 'radeon_ring_gfx' in directory '0' already present!

Thanks for replies,

Yes, it works fine although the messages persist.
So, I have ignored and stay vigilant.

Last edited by duyinthee (2021-08-07 03:21:13)

Offline

#5 2021-10-12 12:09:40

jiffyteeth
Member
Registered: 2018-02-15
Posts: 5

Re: File 'radeon_ring_gfx' in directory '0' already present!

I get sometimes the same message after resuming from suspend.
It's not all the time, but when it happens I have to reboot.
Swaywm wayland

Offline

#6 2021-10-21 16:40:00

firegem
Member
Registered: 2020-12-10
Posts: 1

Re: File 'radeon_ring_gfx' in directory '0' already present!

I get the same issue as #5 when suspending from a Wayland compositor (river). It only happens intermittently. FS for main partition is btrfs if that is related at all.

Oct 21 12:25:22 satellite systemd[1]: Reached target Sleep.
Oct 21 12:25:22 satellite systemd[1]: Starting System Suspend...
Oct 21 12:25:22 satellite systemd-sleep[1954]: Entering sleep state 'suspend'...
Oct 21 12:25:22 satellite kernel: PM: suspend entry (deep)
Oct 21 12:25:23 satellite kernel: Filesystems sync: 0.557 seconds
Oct 21 12:25:52 satellite kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 21 12:25:52 satellite kernel: OOM killer disabled.
Oct 21 12:25:52 satellite kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 21 12:25:52 satellite kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 21 12:25:52 satellite kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 21 12:25:52 satellite kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 21 12:25:52 satellite kernel: ACPI: PM: Preparing to enter system sleep state S3
Oct 21 12:25:52 satellite kernel: ACPI: PM: Saving platform NVS memory
Oct 21 12:25:52 satellite kernel: Disabling non-boot CPUs ...
Oct 21 12:25:52 satellite kernel: smpboot: CPU 1 is now offline
Oct 21 12:25:52 satellite kernel: smpboot: CPU 2 is now offline
Oct 21 12:25:52 satellite kernel: smpboot: CPU 3 is now offline
Oct 21 12:25:52 satellite kernel: ACPI: PM: Low-level resume complete
Oct 21 12:25:52 satellite kernel: ACPI: PM: Restoring platform NVS memory
Oct 21 12:25:52 satellite kernel: LVT offset 0 assigned for vector 0x400
Oct 21 12:25:52 satellite kernel: LVT offset 1 assigned for vector 0xf9
Oct 21 12:25:52 satellite kernel: Enabling non-boot CPUs ...
Oct 21 12:25:52 satellite kernel: x86: Booting SMP configuration:
Oct 21 12:25:52 satellite kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 21 12:25:52 satellite kernel: microcode: CPU1: patch_level=0x07030105
Oct 21 12:25:52 satellite kernel: ACPI: \_PR_.C001: Found 2 idle states
Oct 21 12:25:52 satellite kernel: CPU1 is up
Oct 21 12:25:52 satellite kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Oct 21 12:25:52 satellite kernel: microcode: CPU2: patch_level=0x07030105
Oct 21 12:25:52 satellite kernel: ACPI: \_PR_.C002: Found 2 idle states
Oct 21 12:25:52 satellite kernel: CPU2 is up
Oct 21 12:25:52 satellite kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 21 12:25:52 satellite kernel: microcode: CPU3: patch_level=0x07030105
Oct 21 12:25:52 satellite kernel: ACPI: \_PR_.C003: Found 2 idle states
Oct 21 12:25:52 satellite kernel: CPU3 is up
Oct 21 12:25:52 satellite kernel: ACPI: PM: Waking up from system sleep state S3
Oct 21 12:25:52 satellite kernel: ath: phy0: ASPM enabled: 0x42
Oct 21 12:25:52 satellite kernel: sd 0:0:0:0: [sda] Starting disk
Oct 21 12:25:52 satellite kernel: [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: WB enabled
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000078d30
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000c18
Oct 21 12:25:52 satellite kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_cp1' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_cp2' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_dma1' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_dma2' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: [drm] ring test on 0 succeeded in 3 usecs
Oct 21 12:25:52 satellite kernel: [drm] ring test on 1 succeeded in 2 usecs
Oct 21 12:25:52 satellite kernel: [drm] ring test on 2 succeeded in 2 usecs
Oct 21 12:25:52 satellite kernel: [drm] ring test on 3 succeeded in 4 usecs
Oct 21 12:25:52 satellite kernel: [drm] ring test on 4 succeeded in 4 usecs
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_uvd' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: [drm] ring test on 5 succeeded in 1 usecs
Oct 21 12:25:52 satellite kernel: [drm] UVD initialized successfully.
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_vce1' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: debugfs: File 'radeon_ring_vce2' in directory '0' already present!
Oct 21 12:25:52 satellite kernel: [drm] ring test on 6 succeeded in 7 usecs
Oct 21 12:25:52 satellite kernel: [drm] ring test on 7 succeeded in 2 usecs
Oct 21 12:25:52 satellite kernel: [drm] VCE initialized successfully.
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Oct 21 12:25:52 satellite kernel: usb 2-1.2: reset high-speed USB device number 3 using ehci-pci
Oct 21 12:25:52 satellite kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci
Oct 21 12:25:52 satellite kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 21 12:25:52 satellite kernel: ata2.00: configured for UDMA/100
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 5 succeeded
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 6 succeeded
Oct 21 12:25:52 satellite kernel: [drm] ib test on ring 7 succeeded
Oct 21 12:25:52 satellite kernel: usb 1-1.1: reset full-speed USB device number 3 using ehci-pci
Oct 21 12:25:52 satellite kernel: psmouse serio1: synaptics: queried max coordinates: x [..5634], y [..4598]
Oct 21 12:25:52 satellite kernel: OOM killer enabled.
Oct 21 12:25:52 satellite systemd-sleep[1954]: System returned from sleep state.
Oct 21 12:25:52 satellite kernel: Restarting tasks ... done.
Oct 21 12:25:52 satellite kernel: PM: suspend exit

Offline

#7 2021-11-24 09:07:51

jiffyteeth
Member
Registered: 2018-02-15
Posts: 5

Re: File 'radeon_ring_gfx' in directory '0' already present!

A Topic with the same Error appeared on reddit/r/debian
https://www.reddit.com/r/debian/comment … rectory_0/

journalctl parts from todays failed resume-from-suspend:

Nov 24 06:00:22 archlinux kernel: serial 00:08: activated
Nov 24 06:00:22 archlinux kernel: [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: WB enabled
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000078d30
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000c18
Nov 24 06:00:22 archlinux kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_gfx' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_cp1' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_cp2' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_dma1' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_dma2' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 0 succeeded in 3 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 1 succeeded in 2 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 2 succeeded in 2 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 3 succeeded in 3 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 4 succeeded in 3 usecs
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_uvd' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 5 succeeded in 1 usecs
Nov 24 06:00:22 archlinux kernel: [drm] UVD initialized successfully.
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_vce1' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: debugfs: File 'radeon_ring_vce2' in directory '0' already present!
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 6 succeeded in 8 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ring test on 7 succeeded in 3 usecs
Nov 24 06:00:22 archlinux kernel: [drm] VCE initialized successfully.
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Nov 24 06:00:22 archlinux kernel: usb 7-2: reset full-speed USB device number 2 using ohci-pci
Nov 24 06:00:22 archlinux kernel: usb 8-1: reset high-speed USB device number 2 using xhci_hcd
Nov 24 06:00:22 archlinux kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 24 06:00:22 archlinux kernel: ata1.00: configured for UDMA/133
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 5 succeeded
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 6 succeeded
Nov 24 06:00:22 archlinux kernel: [drm] ib test on ring 7 succeeded
Nov 24 06:00:22 archlinux kernel: OOM killer enabled.
Nov 24 06:00:22 archlinux kernel: Restarting tasks ... 
Nov 24 06:00:22 archlinux kernel: audit: type=1334 audit(1637730022.303:1030): prog-id=273 op=LOAD
Nov 24 06:00:22 archlinux kernel: done.
Nov 24 06:00:22 archlinux kernel: PM: suspend exit

dmesg parts - this is from the restart, right? How do I get the logs from the failed resume-from-suspend?

 3.680516] [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
[    3.680666] radeon 0000:00:01.0: WB enabled
[    3.680687] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
[    3.680691] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04
[    3.680694] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08
[    3.680696] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
[    3.680698] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10
[    3.681204] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000078d30
[    3.681406] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000c18
[    3.681409] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c
[    3.700098] radeon 0000:00:01.0: radeon: using MSI.
[    3.700129] [drm] radeon: irq initialized.
[    3.702718] [drm] ring test on 0 succeeded in 2 usecs
[    3.702799] [drm] ring test on 1 succeeded in 2 usecs
[    3.702812] [drm] ring test on 2 succeeded in 2 usecs
[    3.702959] [drm] ring test on 3 succeeded in 3 usecs
[    3.702966] [drm] ring test on 4 succeeded in 3 usecs

Not sure if relevant, VGA controller details:

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313]
	Subsystem: ASRock Incorporation Device [1849:1313]
	Kernel driver in use: radeon
	Kernel modules: radeon, amdgpu

This is about as extensive as I can do, but I am keen to learn more to provide further information.

Offline

#8 2021-11-24 09:46:55

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 93

Re: File 'radeon_ring_gfx' in directory '0' already present!

As I understand it, these directories are created two times - one time for radeon module, one time for amdgpu module.
I get rid of them after disabling radeon module and enabling amdgpu only, as described here:

https://wiki.archlinux.org/title/AMDGPU … K)_support

In my case it invokes another problems, as I have Hainan/Kaveri combination and Hainan is not fully supported in amdgpu.

Last edited by GeorgeJP (2021-11-24 10:19:44)

Offline

#9 2021-11-25 10:38:16

jiffyteeth
Member
Registered: 2018-02-15
Posts: 5

Re: File 'radeon_ring_gfx' in directory '0' already present!

Thank you, following the link I decided to first try to "Specify the correct module order"
Now I get the debugfs warning in the journal every resume but without any consequences, it has not yet locked up.

How did you get rid of the directory, I have no Idea what to search for for an explanation of "directory '0'"
I am hesitant to touch it until I get a better understanding of the matter.

Offline

#10 2021-11-25 19:25:41

GeorgeJP
Member
From: Czech Republic
Registered: 2020-01-28
Posts: 93

Re: File 'radeon_ring_gfx' in directory '0' already present!

I did following changes to modprobe settings ...

options amdgpu si_support=1
options amdgpu cik_support=1
options radeon si_support=0
options radeon cik_support=0

... so radeon module is disabled and amdgpu is used.
After this change messages about duplicate directories disappeared.

... but ...

Now i have new message:

kernel: kfd kfd: amdgpu: HAINAN  not supported in kfd

I'm using Kaveri, so I ignore this.

Offline

#11 2021-11-30 11:33:31

jiffyteeth
Member
Registered: 2018-02-15
Posts: 5

Re: File 'radeon_ring_gfx' in directory '0' already present!

What I described in #9 did not fix the issue.
I made the changes from #8, #10 and the logs look promising.
To check that the changes are applied I ran

$ lspci -nnk | grep VGA -A3
0:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313]
	Subsystem: ASRock Incorporation Device [1849:1313]
	Kernel driver in use: amdgpu
	Kernel modules: radeon, amdgpu

Thanks George

Last edited by jiffyteeth (2021-11-30 12:13:55)

Offline

Board footer

Powered by FluxBB