Impossible to be sure without logs, but the issue they are describing appears to be a problem with "modern standby" S0 vs good old-fashioned S3. Just guessing,

Impossible to be sure without logs, but the issue they are describing appears to be a problem with "modern standby" S0 vs good old-fashioned S3. Just guessing, some device is not correctly entering a deep sleep state (like an ssd not entering d3cold). So the machine isn't actually fully asleep. Honestly, I'm not sure of the technical benefits, but on the surface, modern standby sucks. I've seen reports of machines having sleep issues even under Windows, but Microsoft pushed it and here we are. Some machines, that support both, default to modern standby and can be changed to S3 with a kernel flag or bios setting. Some, less fortunate, have S3 fully disabled without a way of turning it on, save maybe recompiling your DSDT table.