Comment 103 for bug 1791427

I think you should try it again, even if wireguard is not working. Just for testing and creating a log of your issue, which would probably be very helpful for AaronMa and thus for all of us if this damn bug is finally resolved. Just try somehow to get "journalctl -b 0 -k > journal.log" after a resume/suspend and the other logs as AaronMa described.

Remember this kernel seems to be based on 4.20rc3 so the wireguard issue etc. can be caused by this and could already be fixed in 4.20.3 (current mainline version). You could get 4.20rc3 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ and test if you could reproduce your issue with this version and check if it is fixed in 4.20.3. If you can reproduce it and it is not fixed in 4.20.3 you could/should create a new issue for this bug.

We have a kernel dev looking into this issue who ties to fix the crap lenovo sells. Thus we have to use this chance :)