[Acer Aspire V5-573G] suspend/resume failure

[Maxim Kizub]

Suspend doesn't work.

As per kernel bisection:
# first bad commit: [faae404ebdc6bba744919d82e64c16448eb24a36] ACPICA: Add "Windows 2013" string to _OSI support.

WORKAROUND: Add boot kernel parameter:
acpi_osi="!Windows 2013"

---
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mkizub 1527 F.... pulseaudio
 /dev/snd/controlC0: mkizub 1527 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=fa0d1b45-8989-4536-a8a1-0295cda9bddb
InstallationDate: Installed on 2015-08-09 (35 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Acer Aspire V5-573G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-45-generic.efi.signed root=UUID=0bca80e2-1d3f-4756-adac-3cf832509f5a ro quiet splash "acpi_osi=!Windows 2013" vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-45-generic N/A
 linux-backports-modules-3.16.0-45-generic N/A
 linux-firmware 1.127.11
Tags: trusty
Uname: Linux 3.16.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
WifiSyslog: Sep 14 19:41:34 solliy kernel: [ 586.110463] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000002 FAULT at 0x4188ac [ IBUS ]
_MarkForUpload: True
dmi.bios.date: 01/12/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.30:bd01/12/2015:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-573G
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Maxim Kizub, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1483467

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[Maxim Kizub (mkizub)]

apport information

[penalvch (penalvch)]

Maxim Kizub, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Maxim Kizub (mkizub)]

Tested upstream kernel 4.2-unstable and 4.3 daily builds (current) - the bug is still there (my notebook hangs on resume) and fix (boot kernel param acpi_osi="!Windows 2013") still helps.

[penalvch (penalvch)]

Maxim Kizub, to advise, using a WORKAROUND is not considered "kernel-fixed-upstream".

To clarify, did you test the latest mainline kernel (4.3-rc1), or the daily folder (which was specifically requested not to test)?

[Maxim Kizub (mkizub)]

Sorry, 4.2 (not 4.3-rc1) and from daily folder (I missed the comment to not test daily builds).

[penalvch (penalvch)]

Maxim Kizub, no problem.

Could you please test 4.3-rc1 precisely and advise to the results?

[Maxim Kizub (mkizub)]

Christopher, I've just tested 4.3-rc1 and the result is the same, my notebook hangs on resume.

[penalvch (penalvch)]

Maxim Kizub, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Maxim Kizub (mkizub)]

1. Any way to suspend leads to the same problem with resume - computer hangs. If screen is set to not lock on resume - then screen is restored, but computer does not respond. Any way of suspension (gui, pm-suspend and others) blocks in the same way.
2. Content of /proc/acpi/wakeup is attached
3. Boot (resume) log on kernel 4.3-rc1 follows in next message.
4. I cannot connect by SSH to my computer that hangs on resume.

[Maxim Kizub (mkizub)]

"resume-trace" debugging procedure for finding buggy drivers is attached.
It has logged

[ 0.797599] Magic number: 0:235:725
[ 0.797601] hash matches /home/kernel/COD/linux/drivers/base/power/main.c:515
[ 0.797603] hash matches /home/kernel/COD/linux/drivers/base/power/main.c:740
[ 0.797615] block loop5: hash matches
[ 0.797640] pci 0000:01:00.0: hash matches

and lspci points to NVIDIA card, if I understand correctly:

$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 (rev e4)
00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 (rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1)
04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01)
05:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 14)

[Maxim Kizub (mkizub)]

I was talking about
01:00.0 3D controller: NVIDIA Corporation GK107M

Anyway, here's attached the output of lspci -vvvnn

[Maxim Kizub (mkizub)]

same with sudo
sudo sh -c "lspci -vvvnn >sudo-lspci-vvvnn.txt"

[Maxim Kizub (mkizub)]

https://bugs.freedesktop.org/show_bug.cgi?id=92049

[penalvch (penalvch)]

Maxim Kizub, please disregard my last comment. Instead, given the regression commit, could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Zhang Rui, Bob Moore, Lv Zheng, Rafael J. Wysocki, and Jiri Slaby, CC linux-acpi)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.