Comment 31 for bug 1774950

@Matalak - took a look at your redhat bugzilla link and the behaviour that todd describes is an exact match! Curiously enough, todd seems to be using a standard PC setup rather than a laptop.

At the end of the redhat bugzilla post Laura Abbott suggests that todd files a bug report with the upstream maintainers at bugzilla.kernel.org and when I searched for suspend bugs I found: https://bugzilla.kernel.org/show_bug.cgi?id=199025 (last entry was 10th May)

A few thoughts:

- kernel bug 199025 'Suspend hangs. Never fully suspends and impossible to return to running state.' has been filed against this issue. The 'Status: NEEDINFO' and the last comment on it being from the 10th of May is not particularly encouraging :(

- I'm not entirely sure how all of this works (this is the first bug report that I've filed) but my initial thoughts were to get anyone with suspend issues to add to the bug report and list their hardware, so that there might be a clearer picture of how many people this was affecting and what machines seem to be affected.

- I assumed that nobody would pay any attention to this seemingly 'edge-case hardware combination issue' until it was ascertained that it affected a good many more people.

- I'm pleased to see that I was incorrect in my assumption and that as far as I can tell from an email (think I got added to a list for starting the bug) a canonical team member, Kai-Heng Feng, has been in touch with a kernel.org developer about the kernel bisection report, who has made a patch to test.

So I think what happens is that users report bugs to their specific distro (i.e Ubuntu, Fedora, Debian) and the distro developers/maintainers can then narrow it down and report the problem to the maintainers of the affected part of the project.

In this case, what seems to be a kernel-related problem is reported to the kernel maintainers by the Ubuntu developers.

Since it only seems to be affecting a few specific hardware combinations, it means any fixes will have to be tried out by someone with the 'problem hardware', who can then report back whether the issue is fixed.

(I don't mind testing things out but don't really know what I'm doing, so if there is a patch to try I wouldn't know how to apply it.)

I'm very tempted to let the bugzilla.kernel.org folks know that bug #199025 is affecting us too, but the Ubuntu maintainers might be in touch with them already.