I only figured it was systemd because systemd, from what I know is
responsible for initiating suspend, and I figured waking up from it
afterwards.  But I'm not discounting the possibility it is a kernel issue.
If there is any testing you want me to do (logs and that sort of thing) to
determine what is causing this, I will be happy to try and oblige.  And if
you truly think this is a kernel issue, and have the authority to reassign
the bug to the kernel team, then by all means please do so.  My only
interest is trying to get this issue solved.

Also I'm not sure why I didn't get your reply to my posting.  So sorry for
the late follow-up.

Reply via email to