linux-kernel - Re: crash during resume of PCIe bridge in v5.17 (v5.16 works)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <82b4d69a5b943aa5e8aa7cc33fcc00bce02e557c.camel@web.de>
Date: Tue, 20 Jan 2026 11:27:00 +0100
From: Bert Karwatzki <spasswolf@....de>
To: Thomas Gleixner <tglx@...nel.org>, linux-kernel@...r.kernel.org
Cc: linux-next@...r.kernel.org, spasswolf@....de, Mario Limonciello	
 <mario.limonciello@....com>, Sebastian Andrzej Siewior
 <bigeasy@...utronix.de>,  Clark Williams <clrkwllms@...nel.org>, Steven
 Rostedt <rostedt@...dmis.org>, Christian König	
 <christian.koenig@....com>, regressions@...ts.linux.dev, 
	linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org, "Rafael J . Wysocki"
	 <rafael.j.wysocki@...el.com>, acpica-devel@...ts.linux.dev, Robert Moore	
 <robert.moore@...el.com>, Saket Dumbre <saket.dumbre@...el.com>, Bjorn
 Helgaas	 <bhelgaas@...gle.com>, Clemens Ladisch <clemens@...isch.de>,
 Jinchao Wang	 <wangjinchao600@...il.com>, Yury Norov
 <yury.norov@...il.com>, Anna Schumaker	 <anna.schumaker@...cle.com>,
 Baoquan He <bhe@...hat.com>, "Darrick J. Wong"	 <djwong@...nel.org>, Dave
 Young <dyoung@...hat.com>, Doug Anderson	 <dianders@...omium.org>,
 "Guilherme G. Piccoli" <gpiccoli@...lia.com>, Helge Deller <deller@....de>,
 Ingo Molnar <mingo@...nel.org>, Jason Gunthorpe <jgg@...pe.ca>,  Joanthan
 Cameron <Jonathan.Cameron@...wei.com>, Joel Granados
 <joel.granados@...nel.org>, John Ogness	 <john.ogness@...utronix.de>, Kees
 Cook <kees@...nel.org>, Li Huafei	 <lihuafei1@...wei.com>, "Luck, Tony"
 <tony.luck@...el.com>, Luo Gengkun	 <luogengkun@...weicloud.com>, Max
 Kellermann <max.kellermann@...os.com>, Nam Cao <namcao@...utronix.de>,
 oushixiong <oushixiong@...inos.cn>, Petr Mladek	 <pmladek@...e.com>,
 Qianqiang Liu <qianqiang.liu@....com>, Sergey Senozhatsky	
 <senozhatsky@...omium.org>, Sohil Mehta <sohil.mehta@...el.com>, Tejun Heo	
 <tj@...nel.org>, Thomas Zimemrmann <tzimmermann@...e.de>, Thorsten Blum	
 <thorsten.blum@...ux.dev>, Ville Syrjala <ville.syrjala@...ux.intel.com>, 
 Vivek Goyal <vgoyal@...hat.com>, Yunhui Cui <cuiyunhui@...edance.com>,
 Andrew Morton	 <akpm@...ux-foundation.org>, W_Armin@....de
Subject: Re: crash during resume of PCIe bridge in v5.17 (v5.16 works)

There are exitining news here:
I tested older linux versions with this script

#!/bin/bash
for i in {0..20000}
do
	echo $i
	evolution &
	sleep 5
	killall evolution
	sleep 5
done

with the following results:
Version v5.17, v6.1 and v6.8 show more or less the same
behaviour as v6.12+, i.e. repreated resumes crash after a 
while (sometimes the discrete GPU is lost without a crash)

Version v5.15 shows a different behaviour:
5.15.0-stable-dirty			booted 14:28, 16.1.2026 error 14:52 (25min, 142 resumes)
[ 1453.515962] [  T18093] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[ 1453.515978] [  T18093] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
[ 1453.516046] [  T18093] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62). (-ETIME!)
5.15.0-stable-dirty			booted 17:09, 16.1.2026 error 20:18 (3h, 1102 resumes)
[11337.547257] [ T157373] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[11337.547273] [ T157373] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
[11337.547358] [ T157373] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
5.15.0-stable-dirty			booted 20:51, 16.1.2026 error 21:20 (30min, 164 resumes)
[ 1698.065653] [  T22129] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[ 1698.065665] [  T22129] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
[ 1698.065734] [  T22129] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
5.15.0-stable-dirty			booted 21:25, 16.1.2026 error 21:41 (10min, 91 resumes)
[  965.908197] [   T3843] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[  965.908212] [   T3843] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
[  965.908284] [   T3843] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
5.15.0-stable-dirty			booted 21:46, 16.1.2026 error 1:43 17.1.2026 (4h, 1411 resumes)
[14220.044577] [ T203585] amdgpu 0000:03:00.0: amdgpu: Failed to setup smc hw!
[14220.044593] [ T203585] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
[14220.044662] [ T203585] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).

In all 5 tests the resume failed, but with an error message not seen before, also no crash occured.

And most importantly v5.16 did not crash at all, and also did not show any GPU suspend/resume related error
despite being tested for 36h and 11644 resumes:
Testing (dirty because of -Wno-error=use-after-free and -Wno-error=format-truncation compile fix)
5.16.0-stable-dirty			booted 2:09, 17.1.2026 14:20, 18.1.2026 no error (neither crash or loss of device)
					(36h, 11644 resumes)

So the whole issue seems to be a pure software issue after all (not just an issue related to
probably broken hardware). I'm currently bisecting this between v5.16 and v5.17, but getting a
result can take 2 weeks given the length of the testruns.

The first step of the bisection is already finished and GOOD:
Testing (dirty because of -Wno-error=use-after-free and -Wno-error=format-truncation compile fix)
5.16.0-bisect-07203-g22ef12195e13-dirty booted 14:27, 18.1.2026 no error 1:57 (35.5h, 12508 resumes)

Bert Karwatzki