I have the Framework 13 AMD with the 7840U processor.
It’s running Fedora Silverblue 39, which should behave identically to stock Fedora 39, at least from a kernel (6.6.6-200.fc39.x86_64) perspective.
I’m loving it but there’s one persistent issue I haven’t been able to resolve:
Sometimes when I open the lid from a suspend state, the laptop reboots - I see the Framework logo and then I’m prompted to enter my LUKS password.
I’m not 100% sure what leads to this situation, but I think it happens when I disconnect an external USB mouse (plugged into a USB-A expansion card, front right) whilst the laptop is suspended. This causes it to resume but with the lid still closed, which may be where it gets confused.
The output of journalctl -k -r -b -1 --lines=100 immediately after such a reboot looks like this:
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: wlp1s0: deauthenticating from a2:c9:eb:d8:7e:92 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:16:18 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 12:15:57 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:d8:7e:92
Dec 19 12:15:57 perch kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 19 12:15:57 perch kernel: wlp1s0: associated
Dec 19 12:15:56 perch kernel: wlp1s0: RX AssocResp from a2:c9:eb:d8:7e:92 (capab=0x1511 status=0 aid=6)
Dec 19 12:15:56 perch kernel: wlp1s0: associate with a2:c9:eb:d8:7e:92 (try 1/3)
Dec 19 12:15:56 perch kernel: wlp1s0: authenticated
Dec 19 12:15:56 perch kernel: wlp1s0: send auth to a2:c9:eb:d8:7e:92 (try 1/3)
Dec 19 12:15:56 perch kernel: wlp1s0: authenticate with a2:c9:eb:d8:7e:92
Dec 19 12:15:53 perch kernel: PM: suspend exit
Dec 19 12:15:53 perch kernel: random: crng reseeded on system resumption
Dec 19 12:15:53 perch kernel: done.
Dec 19 12:15:53 perch kernel: usb 1-1: USB disconnect, device number 2
Dec 19 12:15:53 perch kernel: Restarting tasks ...
Dec 19 12:15:53 perch kernel: OOM killer enabled.
Dec 19 12:15:53 perch kernel: PM: resume devices took 2.571 seconds
Dec 19 12:15:53 perch kernel: ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-22)
Dec 19 12:15:53 perch kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 1
Dec 19 12:15:53 perch kernel: ucsi_acpi USBC000:00: failed to re-enable notifications (-5)
Dec 19 12:15:53 perch kernel: [drm] ring sdma_32779.3.3 ib test pass
Dec 19 12:15:53 perch kernel: [drm] ring compute_32779.2.2 ib test pass
Dec 19 12:15:53 perch kernel: [drm] ring gfx_32779.1.1 ib test pass
Dec 19 12:15:53 perch kernel: [drm] ring sdma_32779.3.3 was added
Dec 19 12:15:53 perch kernel: [drm] ring compute_32779.2.2 was added
Dec 19 12:15:53 perch kernel: [drm] ring gfx_32779.1.1 was added
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Dec 19 12:15:53 perch kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Dec 19 12:15:53 perch kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Dec 19 12:15:53 perch kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
Dec 19 12:15:53 perch kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Dec 19 12:15:53 perch kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Dec 19 12:15:53 perch kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Dec 19 12:15:53 perch kernel: atkbd serio0: Unknown key released (translated set 2, code 0x6b on isa0060/serio0).
Dec 19 12:15:53 perch kernel: atkbd serio0: Use 'setkeycodes 6b <keycode>' to make it known.
Dec 19 12:15:53 perch kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x6b on isa0060/serio0).
Dec 19 12:15:53 perch kernel: nvme nvme0: 16/0/0 default/read/poll queues
Dec 19 12:15:53 perch kernel: ACPI: EC: interrupt unblocked
Dec 19 12:15:53 perch kernel: ACPI: EC: interrupt blocked
Dec 19 12:15:53 perch kernel: PM: suspend devices took 0.180 seconds
Dec 19 12:15:53 perch kernel: queueing ieee80211 work while going to suspend
Dec 19 12:15:53 perch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 19 12:15:53 perch kernel: Freezing remaining freezable tasks completed (elapsed 0.085 seconds)
Dec 19 12:15:53 perch kernel: Freezing remaining freezable tasks
Dec 19 12:15:53 perch kernel: OOM killer disabled.
Dec 19 12:15:53 perch kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Dec 19 12:15:53 perch kernel: Freezing user space processes
Dec 19 09:24:00 perch kernel: Filesystems sync: 0.027 seconds
Dec 19 09:24:00 perch kernel: PM: suspend entry (s2idle)
Dec 19 09:24:00 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: wlp1s0: deauthenticating from a2:c9:eb:d8:7e:92 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 19 09:23:59 perch kernel: lockdown_is_locked_down: 1 callbacks suppressed
Dec 19 09:23:38 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:d8:7e:92
Dec 19 09:23:38 perch kernel: wlp1s0: associated
Dec 19 09:23:37 perch kernel: wlp1s0: RX AssocResp from a2:c9:eb:d8:7e:92 (capab=0x1511 status=0 aid=3)
Dec 19 09:23:37 perch kernel: wlp1s0: associate with a2:c9:eb:d8:7e:92 (try 1/3)
Dec 19 09:23:37 perch kernel: wlp1s0: authenticated
Dec 19 09:23:37 perch kernel: wlp1s0: send auth to a2:c9:eb:d8:7e:92 (try 1/3)
Dec 19 09:23:37 perch kernel: wlp1s0: authenticate with a2:c9:eb:d8:7e:92
Dec 19 09:23:34 perch kernel: PM: suspend exit
Dec 19 09:23:34 perch kernel: random: crng reseeded on system resumption
Dec 19 09:23:34 perch kernel: Restarting tasks ... done.
Dec 19 09:23:34 perch kernel: OOM killer enabled.
Dec 19 09:23:34 perch kernel: PM: resume devices took 0.668 seconds
Dec 19 09:23:34 perch kernel: [drm] ring sdma_32779.3.3 ib test pass
Dec 19 09:23:34 perch kernel: [drm] ring compute_32779.2.2 ib test pass
Dec 19 09:23:34 perch kernel: [drm] ring gfx_32779.1.1 ib test pass
Dec 19 09:23:34 perch kernel: [drm] ring sdma_32779.3.3 was added
Dec 19 09:23:34 perch kernel: [drm] ring compute_32779.2.2 was added
Dec 19 09:23:34 perch kernel: [drm] ring gfx_32779.1.1 was added
Dec 19 09:23:34 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Has anyone else seen this? Where would you go next to debug it?
Troubleshooting steps you’ve probably tried, but helpful from my recent experience with similar issues:
Install latest Fedora updates (sounds like you’ve done that).
Ensure that all your expansion cards are attached to slots that they are compatible with.
Noting the log and the kernel_lockdown manpage, have you set up hibernation and secure boot settings correctly? I haven’t done this personally but I’ve seen others have issues setting up deep suspend on this forum.
Unencrypted hibernation/suspend to swap are disallowed as the kernel image is saved to a medium that can then be accessed.
I’ve done 1 & 2 but maybe that’s it for #3 - my whole disk is encrypted with LUKS so maybe there’s nowhere I can hibernate to. Have you got a link to documentation to help me tune or disable this?
I would concur with @variegated.vanilla in that this is going to be the best bet. We do not test against hibernation as I have found it works great until it doesn’t and I lack the personnel to track the changes ongoing.
Thanks! I’m not fussed about hibernation so I’m happy to disable it. But this isn’t something I changed from Fedora defaults - is there a setup step I’ve missed somewhere and that’s why it’s affecting me but not other users? How would you disable hibernation if you were setting up a new Framework?
which I thought would disable hybernation altogether. However, I woke up this morning to find my laptop booting up when I opened the lid, and the following in journalctl -k -r -b -1 --lines=100:
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: wlp1s0: deauthenticating from a2:c9:eb:d8:7e:92 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:38:35 perch kernel: lockdown_is_locked_down: 1 callbacks suppressed
Dec 30 23:38:24 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:d8:7e:92
Dec 30 23:38:24 perch kernel: wlp1s0: associated
Dec 30 23:38:24 perch kernel: wlp1s0: RX ReassocResp from a2:c9:eb:d8:7e:92 (capab=0x1511 status=0 aid=3)
Dec 30 23:38:24 perch kernel: wlp1s0: associate with a2:c9:eb:d8:7e:92 (try 1/3)
Dec 30 23:38:24 perch kernel: wlp1s0: authenticated
Dec 30 23:38:24 perch kernel: wlp1s0: send auth to a2:c9:eb:d8:7e:92 (try 1/3)
Dec 30 23:38:24 perch kernel: wlp1s0: authenticate with a2:c9:eb:d8:7e:92
Dec 30 23:38:24 perch kernel: wlp1s0: disconnect from AP a2:c9:eb:e9:80:64 for new auth to a2:c9:eb:d8:7e:92
Dec 30 23:38:12 perch kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Dec 30 23:38:12 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:e9:80:64
Dec 30 23:38:12 perch kernel: wlp1s0: associated
Dec 30 23:38:12 perch kernel: wlp1s0: RX AssocResp from a2:c9:eb:e9:80:64 (capab=0x1511 status=0 aid=3)
Dec 30 23:38:12 perch kernel: wlp1s0: associate with a2:c9:eb:e9:80:64 (try 1/3)
Dec 30 23:38:12 perch kernel: wlp1s0: authenticated
Dec 30 23:38:12 perch kernel: wlp1s0: send auth to a2:c9:eb:e9:80:64 (try 1/3)
Dec 30 23:38:12 perch kernel: wlp1s0: authenticate with a2:c9:eb:e9:80:64
Dec 30 23:38:08 perch kernel: PM: suspend exit
Dec 30 23:38:08 perch kernel: random: crng reseeded on system resumption
Dec 30 23:38:08 perch kernel: Restarting tasks ... done.
Dec 30 23:38:08 perch kernel: OOM killer enabled.
Dec 30 23:38:08 perch kernel: PM: resume devices took 0.258 seconds
Dec 30 23:38:08 perch kernel: [drm] ring sdma_32775.3.3 ib test pass
Dec 30 23:38:08 perch kernel: [drm] ring compute_32775.2.2 ib test pass
Dec 30 23:38:08 perch kernel: [drm] ring gfx_32775.1.1 ib test pass
Dec 30 23:38:08 perch kernel: [drm] ring sdma_32775.3.3 was added
Dec 30 23:38:08 perch kernel: [drm] ring compute_32775.2.2 was added
Dec 30 23:38:08 perch kernel: [drm] ring gfx_32775.1.1 was added
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Dec 30 23:38:08 perch kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resumed successfully!
Dec 30 23:38:08 perch kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is resuming...
Dec 30 23:38:08 perch kernel: [drm] PCIE GART of 512M enabled (table at 0x00000080FFD00000).
Dec 30 23:38:08 perch kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Dec 30 23:38:08 perch kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Dec 30 23:38:08 perch kernel: nvme nvme0: 16/0/0 default/read/poll queues
Dec 30 23:38:08 perch kernel: ACPI: EC: interrupt unblocked
Dec 30 23:38:08 perch kernel: ACPI: EC: interrupt blocked
Dec 30 23:38:08 perch kernel: PM: suspend devices took 0.144 seconds
Dec 30 23:38:08 perch kernel: queueing ieee80211 work while going to suspend
Dec 30 23:38:08 perch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 30 23:38:08 perch kernel: Freezing remaining freezable tasks completed (elapsed 0.175 seconds)
Dec 30 23:38:08 perch kernel: Freezing remaining freezable tasks
Dec 30 23:38:08 perch kernel: OOM killer disabled.
Dec 30 23:38:08 perch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Dec 30 23:38:08 perch kernel: Freezing user space processes
Dec 30 23:36:52 perch kernel: Filesystems sync: 0.038 seconds
Dec 30 23:36:52 perch kernel: PM: suspend entry (s2idle)
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: wlp1s0: deauthenticating from a2:c9:eb:d8:7e:92 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:36:51 perch kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Dec 30 23:31:44 perch kernel: i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
Dec 30 23:28:29 perch kernel: i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
Dec 30 23:26:02 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:d8:7e:92
Dec 30 23:26:02 perch kernel: wlp1s0: associated
Dec 30 23:26:02 perch kernel: wlp1s0: RX ReassocResp from a2:c9:eb:d8:7e:92 (capab=0x1511 status=0 aid=4)
Dec 30 23:26:02 perch kernel: wlp1s0: associate with a2:c9:eb:d8:7e:92 (try 1/3)
Dec 30 23:26:02 perch kernel: wlp1s0: authenticated
Dec 30 23:26:02 perch kernel: wlp1s0: send auth to a2:c9:eb:d8:7e:92 (try 1/3)
Dec 30 23:26:02 perch kernel: wlp1s0: authenticate with a2:c9:eb:d8:7e:92
Dec 30 23:26:02 perch kernel: wlp1s0: disconnect from AP a2:c9:eb:e9:80:64 for new auth to a2:c9:eb:d8:7e:92
Dec 30 23:24:28 perch kernel: wlp1s0: Limiting TX power to 27 (30 - 3) dBm as advertised by a2:c9:eb:e9:80:64
Dec 30 23:24:28 perch kernel: wlp1s0: associated
Dec 30 23:24:28 perch kernel: wlp1s0: RX AssocResp from a2:c9:eb:e9:80:64 (capab=0x1511 status=0 aid=2)
Dec 30 23:24:28 perch kernel: wlp1s0: associate with a2:c9:eb:e9:80:64 (try 1/3)
Dec 30 23:24:28 perch kernel: wlp1s0: authenticated
Dec 30 23:24:28 perch kernel: wlp1s0: send auth to a2:c9:eb:e9:80:64 (try 1/3)
Dec 30 23:24:28 perch kernel: wlp1s0: authenticate with a2:c9:eb:e9:80:64
Dec 30 23:24:25 perch kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
Dec 30 23:24:24 perch kernel: usb 1-4: reset full-speed USB device number 3 using xhci_hcd
lines 44-100/100 (END)
The only other notable thing is that yesterday afternoon the laptop became extremely sluggish (mouse taking 5+ seconds to move, video only showing one frame every 5 seconds or so) which would suggest a high load but when I opened top there were no processes using excessive amounts of RAM or CPU. I rebooted following that and it was that subsequent boot that the logs above are from.
Any ideas extremely welcome! It would be good to know if this is a hardware thing but I am finding it very hard to debug.