This is our old friend i915 soiling the bed once again. It would appear to be a bug in the resumption/wakeup code given the modules which were active in the stack trace.
Long story short - I915 bug with your meteor lake hardware.
I’m led to believe that the xe drivers are the replacement for i915. They are apparently more performant too, so given the number of issues you’re seeing on this kit with the i915 driver, perhaps trying the Xe drivers might calm stuff down a bit. The counter argument is that they are not yet fully stable and so might be even worse, but you never know until you try.
/etc/modprobe.d/disable-i915.conf:
options i915 force_probe=*
blacklist i915
options xe force_probe=*
This should (I can’t test) disable i915 and switch on the xe driver. If it’s no good, just revert the file to the original contents.