Suspend to RAM is broken

[Ravenise]

I have not shut my computer off for 1.5 years non stop due to this bug. Suspend to ram doesn't work, leaving a backlit HDMI LCD monitor with blinking cursor. Computer fans remain running, power light remains steady, when should be blinking. Does not wake from this state. USB Keyboard and mouse unresponsive, leaving no way to access virtual consoles using ctrl+alt+f1. Hard reboot is necessary.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.16.0-24-generic 3.16.0-24.32
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 2985 F.... pulseaudio
 /dev/snd/controlC2: ubuntu 2985 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 2985 F.... pulseaudio
CasperVersion: 1.346
CurrentDesktop: Unity
Date: Sun Feb 1 01:35:31 2015
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141108)
MachineType: System manufacturer P5Q-PRO
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Ravenise (ravenise)]

Full install, linux mint 17 pm-suspend.log, via terminal: PM_DEBUG=true pm-suspend, will post Ubuntu 15 pm-suspend.log asap.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Ravenise (ravenise)]

Full install, latest Ubunt, 15.04 pm-suspend.log, via terminal: PM_DEBUG=true pm-suspend, with latest Nvidia Proprietary driver installed.

[Ravenise (ravenise)]

pm-suspend.log With Nouveau display driver. (latest Ubuntu, 15.04 , via terminal: PM_DEBUG=true pm-suspend)

[Ravenise (ravenise)]

Original pm-suspend.log without 'PM_DEBUG=true'

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-rc7-vivid/

[Ravenise (ravenise)]

Ok, done. So it is an upstream bug. What does this mean? What should I do simply and concisely for my particular bug, step by step, by a means simple linux users like me can comprehend and get done A.S.A.P?

How often are mainline repairs and patches incorporated into typical upstream kernel updates? Is this a weekly, monthly, or yearly rotation...etc?

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel