I found on this machine(https://certification.canonical.com/hardware/202304-31462/) which uses the same card RTL8168fp/RTL8117 (XID 54b, DASH: disabled), I suppose this is a single hardware issue, but not 100% sure.
I also tested against several ThinkStation/ThinkCentre machines with RTL8168fp/RTL8117 (XID 54a, DASH: disabled), they all works fine. Test output for 202304-31462: Results generated by fwts: Version V24.07.00 (2024-07-30 03:13:27). Some of this work - Copyright (c) 1999 - 2023, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2023, Canonical. Some of this work - Copyright (c) 2016 - 2023, IBM. Some of this work - Copyright (c) 2017 - 2023, ARM Ltd. This test run on 23/09/24 at 17:38:41 on host Linux ubuntu 6.8.0-44-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 22 15:00:55 UTC 2 x86_64. Command: "fwts --s3-multiple=5 s3". Running tests: s3. s3: Sleep suspend/resume test. -------------------------------------------------------------------------------- Test 1 of 1: Sleep suspend/resume test. s2idle cycle 1 of 5 Detecting the power method. Response to CanSuspend is yes User allowed to execute the CanSuspend action Using logind as the default power method. Requesting Suspend action Skipping the minimum delay (0) and using a 3 seconds delay instead s2idle duration = 32. wakeup source name: "00:00" wakeup event was signaled. pm-action returned 0 after 32 seconds. Spent 84.32% of 32s in hardware sleep state Suspend/Resume Timings: Suspend: 0.729 seconds. Resume: 1.430 seconds. s2idle cycle 2 of 5 Using logind as the default power method. Requesting Suspend action Skipping the minimum delay (0) and using a 3 seconds delay instead s2idle duration = 32. wakeup source name: "00:00" wakeup event was signaled. pm-action returned 0 after 32 seconds. Spent 87.83% of 32s in hardware sleep state Suspend/Resume Timings: Suspend: 0.660 seconds. Resume: 1.423 seconds. s2idle cycle 3 of 5 Using logind as the default power method. Requesting Suspend action Skipping the minimum delay (0) and using a 3 seconds delay instead s2idle duration = 31. wakeup source name: "00:00" wakeup event was signaled. pm-action returned 0 after 31 seconds. Spent 89.12% of 31s in hardware sleep state Suspend/Resume Timings: Suspend: 0.667 seconds. Resume: 1.422 seconds. s2idle cycle 4 of 5 Using logind as the default power method. Requesting Suspend action Skipping the minimum delay (0) and using a 3 seconds delay instead s2idle duration = 32. wakeup source name: "00:00" wakeup event was signaled. pm-action returned 0 after 32 seconds. Spent 87.73% of 32s in hardware sleep state Suspend/Resume Timings: Suspend: 0.721 seconds. Resume: 1.424 seconds. s2idle cycle 5 of 5 Using logind as the default power method. Requesting Suspend action Skipping the minimum delay (0) and using a 3 seconds delay instead s2idle duration = 31. wakeup source name: "00:00" wakeup event was signaled. pm-action returned 0 after 31 seconds. Spent 88.96% of 31s in hardware sleep state Suspend/Resume Timings: Suspend: 0.713 seconds. Resume: 1.415 seconds. Completed s2idle cycle(s) PASSED: Test 1, No kernel log errors detected. PASSED: Test 1, No PM related suspend issues detected. PASSED: Test 1, No device errors detected. PASSED: Test 1, No kernel oopses detected. PASSED: Test 1, No kernel WARN_ON warnings detected. PASSED: Test 1, No s2idle errors detected. PASSED: Test 1, Found no errors doing 5 suspend/resume cycle(s). PASSED: Test 1, All suspends took less than 15.00 seconds. PASSED: Test 1, All resumes took less than 15.00 seconds. ================================================================================ 9 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. ================================================================================ 9 passed, 0 failed, 0 warning, 0 aborted, 0 skipped, 0 info only. Test Failure Summary ================================================================================ Critical failures: NONE High failures: NONE Medium failures: NONE Low failures: NONE Other failures: NONE Test |Pass |Fail |Abort|Warn |Skip |Info | ---------------+-----+-----+-----+-----+-----+-----+ s3 | 9| | | | | | ---------------+-----+-----+-----+-----+-----+-----+ Total: | 9| 0| 0| 0| 0| 0| ---------------+-----+-----+-----+-----+-----+-----+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080454 Title: NIC(r8169) didn't link up after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2080454/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
