Oops during every suspend on Gateway NV570P laptop

[Tom]

Every time I close the lid or suspend the system from the menu, the screen goes dark, but the machine does not enter suspend. I have to hold the power button to kill it and reboot. I did not have this problem until a recent kernel package update that was automatically installed.

I have attached the /var/crash log that was created.
---
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tshanks 1726 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=b4ff469f-9e94-4c44-979a-c55c570b8421
InstallationDate: Installed on 2015-06-17 (96 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gateway NV570P
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=49d109e7-a349-4b4d-b67e-ed9424a2b93a ro noprompt quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-28-generic N/A
 linux-backports-modules-3.19.0-28-generic N/A
 linux-firmware 1.143.3
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Gateway
dmi.board.version: V2.06
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.06
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNV570P:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
dmi.product.name: NV570P
dmi.product.version: V2.06
dmi.sys.vendor: Gateway

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1498229

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

apport information

[Tom (tom-reportbug)]

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

[ 1.776729] evm: HMAC attrs: 0x1
[ 1.777194] Magic number: 15:927:959
[ 1.777247] memory memory10: hash matches

[penalvch (penalvch)]

Thomas, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Tom (tom-reportbug)]

@Brad: I did what you said and another script closed my bug as invalid. What am I supposed to do when you tell me one thing, but another automatic process tells me that doing what you asked is wrong?