MBP Sequoia, recurrent restarts, Sleep/Wake hang detected

My MBP (2019), currently running Sequoia 15.2 (but the problem has been recurrent since 3 or 4 OS updates ago) regularly restarts itself whenever I leave it idle for around an hour or more. After such restarts, it displays a message informing me that a USB memory stick had not been correctly ejected before it was disconnected, despite the fact that the memory stick was never either ejected or disconnected. The USB memory stick is connected via a Belken hub connected in turn to a Lifetech 2.0 USB hub with a separate power supply. I suspect that the problem may lie with (a) a faulty cable or connector, (b) a faulty Belken hub, or (c) a faulty Lifetech 2.0 USB hub. The question is how can I identify which component is at fault.

I have copied and pasted the error report below on the off chance that this may reveal something useful to someone who knows how to read these things.

Many thanks to anyone who can provide useful information.

***

panic(cpu 1 caller 0xfffffff01b567c84): Sleep/Wake hang detected @IOPMrootDomain.cpp:12937

Debugger message: panic

Memory ID: 0xff

OS release type: User

OS version: 22P2093

macOS version: 24C101

Kernel version: Darwin Kernel Version 24.2.0: Fri Nov 15 17:52:09 PST 2024; root:xnu-11215.61.3~3/RELEASE_ARM64_T8010

KernelCache UUID: 84C4DFD4F014A07D2C9EB258EE7A9EDF

Kernel UUID: EF3A374F-9BAF-3918-906D-8577FF003DA3

Boot session UUID: 878B2EA8-FAD9-4FEE-8FB4-2708334B06B9

iBoot version: iBoot-11881.61.3

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0xe

x86 System State: 0x1

x86 Power State: 0x2

x86 Shutdown Cause: 0xec

x86 Previous Power Transitions: 0x200020002

PCIeUp link state: not available

macOS kernel slide: 0x8200000

Paniclog version: 14

Kernel slide: 0x0000000013d58000

Kernel text base: 0xfffffff01ad5c000

mach_absolute_time: 0xcab45e8eb3

Epoch Time: sec usec

Boot : 0x67755fda 0x0004b3b5

Sleep : 0x6775fd27 0x0007a7f7

Wake : 0x6775fd27 0x000cf9ff

Calendar: 0x6775fd52 0x0001dbda

Zone info:

Zone map: 0xffffffdc07010000 - 0xffffffe207010000

. VM : 0xffffffdc07010000 - 0xffffffdced674000

. RO : 0xffffffdced674000 - 0xffffffdd3a340000

. GEN0 : 0xffffffdd3a340000 - 0xffffffde209a4000

. GEN1 : 0xffffffde209a4000 - 0xffffffdf07008000

. GEN2 : 0xffffffdf07008000 - 0xffffffdfed670000

. GEN3 : 0xffffffdfed670000 - 0xffffffe0d3cd8000

. DATA : 0xffffffe0d3cd8000 - 0xffffffe207010000

Metadata: 0xffffffee2e9ac000 - 0xffffffee301ac000

Bitmaps : 0xffffffee301ac000 - 0xffffffee302c8000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xffffffde20339050 0: 0x0000000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffff01b0a2594, LR=0xfffffff01b0a2590, FP=0xffffffee303abe60

CORE 1 is the one that panicked. Check the full backtrace for details.

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xffffffdfed6d6a38: 0 pages, 231 threads: pid 0: kernel_task

Panicked thread: 0xffffffde20339050, backtrace: 0xffffffee3046b820, tid: 195481

lr: 0xfffffff01af66020 fp: 0xffffffee3046b890

lr: 0xfffffff01b0a042c fp: 0xffffffee3046b900

lr: 0xfffffff01b09f520 fp: 0xffffffee3046b9f0

lr: 0xfffffff01af256bc fp: 0xffffffee3046ba00

lr: 0xfffffff01af65a60 fp: 0xffffffee3046bdd0

lr: 0xfffffff01b64e6d8 fp: 0xffffffee3046bdf0

lr: 0xfffffff01b567c84 fp: 0xffffffee3046be30

lr: 0xfffffff01afc1908 fp: 0xffffffee3046bf20

lr: 0xfffffff01af306c4 fp: 0x0000000000000000