[Bug 1206864] New: Direct Rendering Manager trouble upon resume from suspend to RAM
http://bugzilla.opensuse.org/show_bug.cgi?id=1206864 Bug ID: 1206864 Summary: Direct Rendering Manager trouble upon resume from suspend to RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: karl.mistelberger@nefkom.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 863857 --> http://bugzilla.opensuse.org/attachment.cgi?id=863857&action=edit journal The system readily suspends. But resume is very slow and exhibits trouble with drm: [ 195.129982] kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000). [ 195.831331] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 196.343309] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 196.855320] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 197.367318] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 197.879296] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 198.391313] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 198.903334] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 199.415327] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 199.927300] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 200.439297] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 200.951299] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 201.463085] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 201.975089] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 202.487089] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 202.999090] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 203.511090] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 204.023091] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 204.535091] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 205.047358] kernel: [drm] Fence fallback timer expired on ring sdma0 [ 205.123518] kernel: [drm] UVD and UVD ENC initialized successfully. [ 205.223510] kernel: [drm] VCE initialized successfully. See also attached journal. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206864 http://bugzilla.opensuse.org/show_bug.cgi?id=1206864#c2 --- Comment #2 from Karl Mistelberger <karl.mistelberger@nefkom.net> --- (In reply to Takashi Iwai from comment #1)
Looks like a problem of amdgpu.
I suppose it's something new in 6.1.x, and not happening with 6.0.x kernel? If yes, please report to the upstream, e.g. gitlab.freedesktop.org Issues.
Last (almost) known good kernel is 5.18.11-1: Jan 05 03:20:49 erlangen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000). Jan 05 03:20:49 erlangen kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 05 03:20:49 erlangen kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 05 03:20:49 erlangen kernel: [drm] UVD and UVD ENC initialized successfully. Jan 05 03:20:49 erlangen kernel: [drm] VCE initialized successfully. All 6.0 and newer fail.
In anyway, please give the hardware details.
erlangen:~ # inxi -zaG Graphics: Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] vendor: Sapphire driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 2b:00.0 chip-ID: 1002:699f class-ID: 0300 temp: 49.0 C Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 192 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Samsung LU28R55 serial: <filter> built: 2038 res: 3840x2160 hz: 60 dpi: 154 gamma: 1.2 size: 632x360mm (24.88x14.17") diag: 727mm (28.6") ratio: 16:9 modes: max: 3840x2160 min: 720x400 API: OpenGL v: 4.6 Mesa 22.3.2 renderer: AMD Radeon RX 550 / 550 Series (polaris12 LLVM 15.0.6 DRM 3.46 5.18.11-1-default) direct render: Yes erlangen:~ # -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206864 http://bugzilla.opensuse.org/show_bug.cgi?id=1206864#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- (In reply to Karl Mistelberger from comment #2)
(In reply to Takashi Iwai from comment #1)
Looks like a problem of amdgpu.
I suppose it's something new in 6.1.x, and not happening with 6.0.x kernel? If yes, please report to the upstream, e.g. gitlab.freedesktop.org Issues.
Last (almost) known good kernel is 5.18.11-1:
Jan 05 03:20:49 erlangen kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000). Jan 05 03:20:49 erlangen kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 05 03:20:49 erlangen kernel: [drm] Fence fallback timer expired on ring sdma0 Jan 05 03:20:49 erlangen kernel: [drm] UVD and UVD ENC initialized successfully. Jan 05 03:20:49 erlangen kernel: [drm] VCE initialized successfully.
Aha, so the message itself appeared in 5.18, but they were fewer, and the shorter blockage.
All 6.0 and newer fail.
How about 5.19.x? And, as far as I understand correctly, it doesn't "fail" but just takes much longer time, right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206864 http://bugzilla.opensuse.org/show_bug.cgi?id=1206864#c4 --- Comment #4 from Karl Mistelberger <karl.mistelberger@nefkom.net> --- (In reply to Takashi Iwai from comment #3)
Aha, so the message itself appeared in 5.18, but they were fewer, and the shorter blockage.
Yep.
All 6.0 and newer fail. How about 5.19.x?
5.19.x already suffered from the multiple timeouts.
And, as far as I understand correctly, it doesn't "fail" but just takes much longer time, right?
There is an annoying ten seconds delay. However the system eventually recovers and stays usable. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com