<blockquote>Adam Colligan, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked.
Thank you for your understanding.</blockquote>
I have followed all of those instructions to the best of my ability. I sent the full initial report to the maintainer address listed in my attachment at comment #9, and this morning I sent the same address the additional debugging information attached to #15. Those instructions included providing a link to a Launchpad bug report, which is why I re-opened this report, so that there would be a live and current target for such a link. I am not sure about how to find a link to my actual email to <email address hidden> ; I do not see it at http://rss.gmane.org/messages/excerpts/gmane.linux.power-management.general . I don't know if this means it could have been filtered for some reason; it was a very long plain text message with everything in-line, which I believe is what was instructed. I don't know if it's possible that it being PGP/SMIME could mess it up? I don't want to spam the list with duplicates.
Re: video drivers used for testing --
My nominal setup is to use Nvidia drivers. However, testing upstream kernels tends to break my entire video setup and has necessitated very long periods of recovery to resume any function. I think that previous failures have taken place with both Nvidia and nouveau drivers.
For the latest testing, I switched to nouveau drivers before downloading and booting on the latest kernel. Therefore, all of the current debugging information involves no proprietary drivers. While this is unfortunate because it is not my normal setup, suspend (and hibernate, for that matter) still fails as usual, and I am too run down by this issue to spend more hours un-breaking my configuration after each test.
I got an earlier email update on this thread as
<blockquote>Adam Colligan, the issue you are reporting is an upstream one. Could you /wiki.ubuntu. com/Bugs/ Upstream/ kernel ?
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https:/
Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked.
Thank you for your understanding. </blockquote>
I have followed all of those instructions to the best of my ability. I sent the full initial report to the maintainer address listed in my attachment at comment #9, and this morning I sent the same address the additional debugging information attached to #15. Those instructions included providing a link to a Launchpad bug report, which is why I re-opened this report, so that there would be a live and current target for such a link. I am not sure about how to find a link to my actual email to <email address hidden> ; I do not see it at http:// rss.gmane. org/messages/ excerpts/ gmane.linux. power-managemen t.general . I don't know if this means it could have been filtered for some reason; it was a very long plain text message with everything in-line, which I believe is what was instructed. I don't know if it's possible that it being PGP/SMIME could mess it up? I don't want to spam the list with duplicates.
Re: video drivers used for testing --
My nominal setup is to use Nvidia drivers. However, testing upstream kernels tends to break my entire video setup and has necessitated very long periods of recovery to resume any function. I think that previous failures have taken place with both Nvidia and nouveau drivers.
For the latest testing, I switched to nouveau drivers before downloading and booting on the latest kernel. Therefore, all of the current debugging information involves no proprietary drivers. While this is unfortunate because it is not my normal setup, suspend (and hibernate, for that matter) still fails as usual, and I am too run down by this issue to spend more hours un-breaking my configuration after each test.