10de:1205 [Asus P8H67-M PRO] Resume from Suspend - X Crashes

[Avi Marcus]

After I suspend in 14.04, when it comes back it looks fine. But rather soon X crashes.
Sometimes ctrl-ALT F1 doesn't even work. Other times it does, I try killing X or lightdm but I'm not really sure I'm doing the right thing.

Today, I had two different ways it crashed: I tried opening a video. Audio was playing in totem, but no video. It wouldn't close.
Also today, I had a chrome window open. I clicked a dropdown and it didn't even display what was in the dropdown, it just froze everything.

I am using gnome-metacity (since I'm not such a fan of unity). I have a nvidia card, but the nvidia drivers didn't seem to be configurable. I am using nouveau but setting the 2nd screen's resolution manually.

WORKAROUND: Use 12.04.2 with nvidia drivers.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: avi 2550 F.... pulseaudio
 /dev/snd/controlC1: avi 2550 F.... pulseaudio
 /dev/snd/controlC0: avi 2550 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-25 (10 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=bd9df8bf-7b4a-40df-b999-647914e439b8 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/17/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M 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.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Avi Marcus (avi-amarcus)]

I can do the resume-trace here if needed: https://wiki.ubuntu.com/DebuggingKernelSuspend
I couldn't find exactly my bug elsewhere... maybe you could just point me to bug report if it's duplicate.

Version: Ubuntu 3.13.0-24.46-generic 3.13.9

Wakeup:
Device S-state Status Sysfs node
UAR1 S4 *disabled pnp:00:08
PS2K S4 *enabled pnp:00:09
BR20 S3 *disabled
EUSB S4 *enabled pci:0000:00:1d.0
USBE S4 *enabled pci:0000:00:1a.0
P0P3 S4 *disabled
P0P4 S4 *disabled
P0P1 S4 *disabled pci:0000:00:01.0
P0P2 S4 *disabled
PEX0 S4 *disabled pci:0000:00:1c.0
PEX1 S4 *disabled
PEX2 S4 *disabled
PEX3 S4 *disabled
PEX4 S4 *disabled pci:0000:00:1c.4
PEX5 S4 *disabled pci:0000:00:1c.5
PEX6 S4 *disabled pci:0000:00:1c.6
PEX7 S4 *disabled pci:0000:00:1c.7
BR19 S4 *disabled pci:0000:06:00.0

[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 1316121

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.

[Avi Marcus (avi-amarcus)]

I'm sorry --- wakeup is from: "cat /proc/acpi/wakeup" (I couldn't find an edit button)

And I also uploaded the wrong xlog -- that's the working one, now attached is the .old

[Avi Marcus (avi-amarcus)]

Also: I was using this hardware with Linux Mint 13 and the nvidia driver and resume/suspend was fine. So this is a new configuration issue or bug.

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[Avi Marcus (avi-amarcus)]

apport information

[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.15 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.15-rc4-utopic/

[Avi Marcus (avi-amarcus)]

I installed 3 debs for v3.15-rc4--
linux-headers-3.15.0-031500rc4-generic_3.15.0-031500rc4.201405042135_amd64.deb
linux-headers-3.15.0-031500rc4_3.15.0-031500rc4.201405042135_all.deb
linux-image-3.15.0-031500rc4-generic_3.15.0-031500rc4.201405042135_amd64.deb

Grub automatically selected 3.15 but once it got past the ubuntu splash screen, both screens were just blank.... so that didn't seem to help at all. I'm not sure how to debug the kernel, or if you wish me to. Adding the tag kernel-unable-to-test-upstream.

Thanks for the help so far!

[Avi Marcus (avi-amarcus)]

OK I updated the BIOS (I couldn't get freedos to execute the exe, but apparents asus has an application to install the ROM right in the bios.. cool!)

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
3904
04/27/2013

The issue does indeed still exist.

A more rigid explanation of the issue, at least this time:
1) I booted, opened a video in totem -- saw there was video and audio -- and then closed it.
2) I hit suspend in the menu. (I had tried pm-suspend once, and apparently that's the same command?)
3) I waited about 10 seconds, and hit a button on the keyboard to wake it up.
4) I re-opened the same video. I got audio right away, but no video. The totem window is unresponsive.
5) I was able to ctrl-alt-F1 to kill -9 the pid for xorg, which brought me back to a a gui login... but... actually, totem still doesn't show the video and it is unresponsive. I guess I'll reboot for real now...

[Avi Marcus (avi-amarcus)]

Follow up:

6) While in the newly spawned Xorg, I opened https://help.ubuntu.com in chrome. When I clicked a drop-down it was blank, the whole screen locked up, and after about 10-15 seconds, spit me out to a new GUI window. Even when I logged back in, playing videos still didn't work. I did indeed HAVE to reboot.

[penalvch (penalvch)]

Avi Marcus, did this problem not occur in a release prior to Trusty?

[Avi Marcus (avi-amarcus)]

Correct, as stated in one of my comments:

I was using this hardware with Linux Mint 12 (based on Ubuntu Oneiric 11.10) and the nvidia driver and resume/suspend was fine. So this is a new configuration issue or bug.

I'm now using nouveu, which I'd expect would be more likely to work. I couldn't get nvidia to allow me to configure the screens, for some reason, and I got nouveu to work.

[Avi Marcus (avi-amarcus)]

... forgot and again, don't see an edit button. I checked -- suspend worked on Linux Mint 12 from the start and through kernel 3.0.0.0-32, the most recent I had updated it.

[penalvch (penalvch)]

Avi Marcus, just to clarify, did this problem not happen on a release of Ubuntu (not Mint or some other distro) prior to Trusty?

[Avi Marcus (avi-amarcus)]

Yes -- on a clean 12.04 with minimal additions, suspend worked just fine:

It's running the nvidia screen driver, not neuvoeu.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

avi@avi-i7:~$ uname -r
3.5.0-23-generic

$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PS2K S4 *enabled pnp:00:0c
UAR1 S4 *disabled pnp:00:0d
P0P1 S4 *disabled
RP01 S4 *disabled pci:0000:00:1c.0
PXSX S4 *disabled
RP02 S4 *disabled
PXSX S4 *disabled
RP03 S4 *disabled
PXSX S4 *disabled
RP04 S4 *disabled
PXSX S4 *disabled
RP05 S4 *disabled pci:0000:00:1c.4
PXSX S4 *disabled
RP06 S4 *disabled pci:0000:00:1c.5
PXSX S4 *enabled pci:0000:04:00.0
RP07 S4 *disabled pci:0000:00:1c.6
PXSX S4 *enabled pci:0000:05:00.0
PEG0 S4 *disabled pci:0000:00:01.0
PEGP S4 *disabled
PEG1 S4 *disabled
PEG2 S4 *disabled
PEG3 S4 *disabled
RP08 S4 *disabled pci:0000:00:1c.7
PXSX S4 *disabled pci:0000:06:00.0
GLAN S4 *disabled
EHC1 S4 *enabled pci:0000:00:1d.0
EHC2 S4 *enabled pci:0000:00:1a.0
HDEF S4 *disabled pci:0000:00:1b.0

[penalvch (penalvch)]

Avi Marcus, to further clarify, did this problem not happen with nouveau only in a release prior to Trusty?

[Avi Marcus (avi-amarcus)]

I don't know how to switch to nouveau on 12.04... but it said in "additional drivers" settings that the nvidia driver was "activated but not in use".

I installed nouveau-firmware which mentions nvidia in it, but that didn't make any difference even after a reboot.

I got nvidia driver working on Trusty by importing my old x11 file, but then I lost it again and I don't know how to get the nvidia settings to work.
I installed nvidia-331 and then went and activated in software & updates -> additional drivers and tried nvidia-311 and nvidia-304, activated it, and rebooted. Both still had the crashing issue.... so it's probably not actually the specific driver issue?

What now? I'd really like suspend to work... or at least a way to save open windows & files...