Laptop hangs during second time it suspends

[Jan W]

When I want to suspend my computer for the second time it hangs. It does not react to any keyboard input or the power button. The only way to recover is to hold the power button several seconds to reboot the computer.

I followed the procedure mentioned at https://wiki.ubuntu.com/DebuggingKernelSuspend. To reproduce I first completely suspend the laptop, e.g. by closing the lid or by using the pm-suspend command. After wakeup from suspend I start following the procedure. At the step where the command "echo devices > /sys/power/pm_test" is given the laptop hangs during suspend. It does not reach suspended state, as the power remains on. On reboot, the Magic number says: "memory memory48: hash matches"

I have a HP Pavilion 15 laptop with an Intel Skylake processor. I have experienced this on kernel 4.2.0 (Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3), but also on kernels 4.4.1 an 4.4.3 (taken from mainline kernel release). After installation of 15.10 I made the following changes for hardware support:
- I installed rtlwifi-new-dkms from http://ppa.launchpad.net/hanipouspilot/rtlwifi/ubuntu/. This has support for antenna selection which my wifi requires (auto selection does not work, I use parameter ant_sel for module rtl8723be)
- I installed nvidia-352-updates and bumblebee to support the graphics card
- I use kernel parameter pci=noaer to avoid dmesg being flooded with the same message (see bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173)

I upgraded to the latest BIOS.

One thing I noticed is that there is a difference between before the first suspend and after the first suspend to the contents of cat /proc/acpi/wakeup > wakeup.
After the boot, and before the first suspend this line is reported:
PXSX S5 *disabled pci:0000:04:00.0
After the first suspend and resume this line becomes:
PXSX S5 *enabled pci:0000:04:00.0

If I read lspci correctly device 0000:04:00.0 is "Signal processing controller [1180]: Intel Corporation Device [8086:1903] (rev 08)"

Thanks for looking into this.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-30-generic 4.2.0-30.35
ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jan 4087 F.... pulseaudio
CurrentDesktop: KDE
Date: Wed Mar 2 13:12:42 2016
HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272
InstallationDate: Installed on 2016-02-03 (27 days ago)
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b006 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 0bda:57eb Realtek Semiconductor Corp.
 Bus 001 Device 006: ID 0461:4d03 Primax Electronics, Ltd Kensington Mouse-in-a-box
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro quiet splash pci=noaer vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-30-generic N/A
 linux-backports-modules-4.2.0-30-generic N/A
 linux-firmware 1.156
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.77
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80A4
dmi.board.vendor: HP
dmi.board.version: 91.1C
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1C:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Jan W (ubuntu-kiekerjan)]

I followed the following procedure to reproduce the issue, and will add some additional logs I made.

1. Boot the computer
2. Store dmesg in dmesg_first.txt
3. Store output of cat /proc/acpi/wakeup in wakeup_first.txt
4. Suspend using command pm-suspend (I can also close the lid)
5. Resume by pressing a key on the keyboard
6. Store dmesg in dmesg_second.txt
7. Store output of cat /proc/acpi/wakeup in wakeup_second.txt
8. Give commands
sudo su
echo devices > /sys/power/pm_test
exit
9. Suspend using command sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
10. System hangs
11. Reboot
12. Store dmesg in dmesg_secondboot.txt

As requested somewhere I also add the output of lsusb -vnvn

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Jan van de Wijdeven, thank you for reporting this and helping make Ubuntu better.

Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

[Jan W (ubuntu-kiekerjan)]

There is no sticker on the computer, but my order says "HP Star Wars Special Edition laptop 15-AN000ND". The SKU number is P4A01EA#ABH.

[penalvch (penalvch)]

Jan van de Wijdeven, in order to obtain test environment diversity, could you please with a live environment via http://cdimage.ubuntu.com/daily-live/current/ and advise if this may suspend?

Please don't to install anything once booted, just attempt the suspend/resume cycle.

[Jan W (ubuntu-kiekerjan)]

I just booted into the live image. Suspend and resume seems to work as expected. I can suspend and resume multiple times in a row.

[penalvch (penalvch)]

Jan van de Wijdeven, would you need a backport to a release prior to 16.04 or may this be closed as Status Invalid?

[Jan W (ubuntu-kiekerjan)]

I'm not sure I understand. I'm totally fine with waiting for 16.04 if the issue is solved in that release. But why would that make this bug invalid?
Also, since you're asking for a backport, did you identify the cause of the bug?
And, let's not forget ;) Thank you Christopher for helping me.

[penalvch (penalvch)]

Jan van de Wijdeven, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216/comments/13 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Oli (oli)]

I see the same behaviour on a 16.04 desktop with a Nvidia 970.

Before this I was successfully suspending many times per session using 14.04 with a Wily HWE stack so I think that excludes 4.2 from directly being the problem. I have since disabled timed suspend but if the monitor has been turned off (via DPMS), first-time manual suspend fails.

The 16.04 Live image also suspends fine. That uses Nouveau though.

So I think the common factor between us is the proprietary Nvidia driver and Maxwell (we're on different generations but, still). I've tried versions 358 and 364 of the driver but both are broken for me on 16.04.

Unfortunately I upgraded to my 970 (from a 580) about the same time I upgraded to 16.04 so I can't rule out it being just a Maxwell issue.

You get anywhere with this?

[penalvch (penalvch)]

Oli, given this report is closed as it is fixed for the original reporter, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Oli (oli)]

Sorry, Christopher, I disagree with that assessment of the situation.

This when the Jan said the Live image worked. That isn't an indication that this is now fixed, it's an indication that the Live image works. It works for me too. On a technical level, that in itself is a clear indication this is related to the graphics stack.

This bug is still valid IMO. I'll shut up if Jan says this is fixed for them now (in a proper install) but otherwise I think this has just been improperly triaged.

[Jan W (ubuntu-kiekerjan)]

I have upgraded to 16.04. It seems that the issue is really solved in 16.04 as I can now suspend the computer multiple times.
There is one but, I don't have the Nvidia drivers installed at the moment due to bug 1577041 (https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1577041). I'll report back once that is resolved, but for now it looks good.

[Jan W (ubuntu-kiekerjan)]

I just managed to install the Nvidia drivers. Suspend still works as expected, so I'm happy ;)