Bug 217889

Summary: WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/ttm/ttm_bo.c:362 ttm_bo_release+0x309/0x330 [ttm] after resolution change
Product: Drivers Reporter: WojtasJD (wojtasjd)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: RESOLVED ANSWERED    
Severity: normal CC: wojtasjd
Priority: P3    
Hardware: All   
OS: Linux   
Kernel Version: Subsystem:
Regression: No Bisected commit-id:
Attachments: Ubuntu 22.04.2 Live session dmesg output

Description WojtasJD 2023-09-08 15:03:12 UTC
Created attachment 305071 [details]
Ubuntu 22.04.2 Live session dmesg output

After changing resolution (for example from 1920x1080 -> 1680x1050) from GUI (Displays section in GNOME Control Center or KDE systemsettings) I'm getting this ttm WARNING (dmesg).
It occurs in several distributions like:
- Ubuntu 22.04.2 (GNOME, X11) Live session, kernel: 5.19.0-32-generic (64-bit)
- openSUSE Leap 15.5 (KDE Plasma 5.27.4, X11), kernel 5.14.21-150500-55.19-default (64-bit)
- Manjaro (KDE Plasma 5.27.7, X11), kernel 6.1.49-1-MANJARO (64-bit)
- Manjaro (KDE Plasma 5.27.7, X11), kernel 6.5.0-1-MANJARO (64-bit)

It seems that changing resolution with xrandr (after reboot) does not cause this problem.

I'm attaching dmesg output from Ubuntu 22.04.2 (GNOME, X11) Live session.

$ inxi -b

System:
  Host: ubuntu Kernel: 5.19.0-32-generic x86_64 bits: 64 Desktop: GNOME 42.5
    Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5QL-CM v: Rev X.0x
    serial: <superuser required> BIOS: American Megatrends v: 0901
    date: 05/11/2010
CPU:
  Info: quad core Intel Xeon L5430 [MCP] speed (MHz): avg: 2003
    min/max: 2003/2670
Graphics:
  Device-1: AMD Turks PRO [Radeon HD 6570/7570/8550 / R5 230] driver: radeon
    v: kernel
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: ati,radeon
    unloaded: fbdev,modesetting,vesa gpu: radeon resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD TURKS (DRM 2.50.0 / 5.19.0-32-generic LLVM 15.0.6)
    v: 3.3 Mesa 22.2.5
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 163.56 GiB used: 62.6 MiB (0.0%)
Info:
  Processes: 257 Uptime: 24m Memory: 3.83 GiB used: 2.2 GiB (57.5%)
  Shell: Bash inxi: 3.3.13


# cat /sys/kernel/debug/dma_buf/bufinfo

Dma-buf Objects:
size    	flags   	mode    	count   	exp_name	ino     
03784704	00000000	00080005	00000003	drm	00000110	
	read fence:radeon radeon.gfx seq 6580 signalled
	read fence:radeon radeon.gfx seq 6576 signalled
	Attached Devices:
Total 0 devices attached

08355840	00000000	00080005	00000003	drm	00000106	
	read fence:radeon radeon.gfx seq 6552 signalled
	Attached Devices:
Total 0 devices attached

08355840	00000000	00080005	00000003	drm	00000105	
	write fence:radeon radeon.gfx seq 6578 signalled
	Attached Devices:
Total 0 devices attached

08355840	00000000	00080005	00000003	drm	00000104	
	write fence:radeon radeon.gfx seq 6576 signalled
	read fence:radeon radeon.gfx seq 5897 signalled
	Attached Devices:
Total 0 devices attached

08355840	00000000	00080005	00000003	drm	00000103	
	write fence:radeon radeon.gfx seq 6580 signalled
	Attached Devices:
Total 0 devices attached

08355840	00000000	00080005	00000002	drm	00000101	
	read fence:radeon radeon.gfx seq 4414 signalled
	Attached Devices:
Total 0 devices attached

03899392	00000000	00080005	00000003	drm	00000084	
	read fence:radeon radeon.gfx seq 6445 signalled
	read fence:radeon radeon.gfx seq 4345 signalled
	Attached Devices:
Total 0 devices attached

00004096	00000000	00080005	00000003	drm	00000083	
	Attached Devices:
Total 0 devices attached

01916928	00000000	00080005	00000003	drm	00000072	
	read fence:radeon radeon.gfx seq 5932 signalled
	Attached Devices:
Total 0 devices attached

00004096	00000000	00080005	00000003	drm	00000014	
	Attached Devices:
Total 0 devices attached

08294400	00000000	00080005	00000002	drm	00000011	
	read fence:radeon radeon.gfx seq 295 signalled
	Attached Devices:
Total 0 devices attached


Total 11 objects, 59682816 bytes
Comment 1 Artem S. Tashkinov 2023-09-08 17:16:27 UTC
Please report here instead https://gitlab.freedesktop.org/drm/amd/-/issues

Make sure you've tested and confirmed this issue is reproducible in 6.5.2.