[Alienware Alienware 13 R2] hibernate/resume failure [non-free: nvidia_uvm nvidia_modeset nvidia]

Bug #1568703 reported by Jan Stutzki
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

As standby is not working I tried it with hibernate. Unfortunately the same error occurs (EXT4-fs error) after the message that nvme0n1 is not available.

ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-18-generic 4.4.0-18.34
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly.
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 1306 F.... pulseaudio
                      stutzki 2131 F.... pulseaudio
Date: Mon Apr 11 08:34:00 2016
DuplicateSignature: hibernate/resume:Alienware Alienware 13 R2:1.2.12
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=45b1ef11-e9d4-4daf-9cb1-f253e996f6b4
InstallationDate: Installed on 2016-04-01 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
InterpreterPath: /usr/bin/python3.5
MachineType: Alienware Alienware 13 R2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=9bc7e2b8-0f93-4332-b217-19fdb84e9e0d ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-18-generic N/A
 linux-backports-modules-4.4.0-18-generic N/A
 linux-firmware 1.157
SourcePackage: linux
Title: [Alienware Alienware 13 R2] hibernate/resume failure [non-free: nvidia_uvm nvidia_modeset nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/22/2016
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.12
dmi.board.name: Alienware 13 R2
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnAlienware:bvr1.2.12:bd03/22/2016:svnAlienware:pnAlienware13R2:pvr1.2.12:rvnAlienware:rnAlienware13R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 13 R2
dmi.product.version: 1.2.12
dmi.sys.vendor: Alienware

Revision history for this message
Jan Stutzki (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1-launchpad) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 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'.

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/v4.6-rc4-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jan Stutzki (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1-launchpad) wrote :

Unfortunately the identical problem persists with all the kernels I tried recently:
4.2.0-27-generic
4.4.0-16-generic
4.4.0-17-generic
4.4.0-21-generic
4.5.2-040502-generic
4.6.0-999-generic #201604262201 SMP Wed Apr 27 02:03:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (from the ppa "daily")

When booted from USB stick the system suspends and wakes up but is unable to access any filesystems as the stick has moved from /dev/sda to /dev/sdb. The nvme0n1 device is available before standby an is missing after. Same goes for all devices on a PCI bus other than 01:

These devices go missing after suspend/standby:
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)
03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

My current guess is an issue with the UEFI/BIOS.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-1.2.13
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan Stutzki (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1-launchpad) wrote :

1) sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.2.13
04/15/2016
2) No improvement. Same behaviour as previously.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jan Stutzki, could you please test the latest mainline kernel (4.7-rc2) and advise to the results?

tags: added: latest-bios-1.2.13
removed: bios-outdated-1.2.13
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan Stutzki (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1-launchpad) wrote :

Dell released another BIOS update (1.2.14) which I installed. Using 4.4.0-22 the error message unfortunately remains the same.

Using Mainline Kernele 4.7-rc2 the system does not suspend anymore. The HD activity indicator is permanently on and judging by the sound of the ac adapter the CPU is under load.

Revision history for this message
penalvch (penalvch) wrote :

Jan Stutzki, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Revision history for this message
Jan Stutzki (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1-launchpad) wrote :

As requested:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.2.14
05/20/2016

Revision history for this message
penalvch (penalvch) wrote :

Jan Stutzki, to clarify, did you test hibernate (not suspend) with 4.7-rc2?

tags: added: latest-bios-1.2.14
removed: latest-bios-1.2.13
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
dez (dezza) wrote :

I have the same problem as described by Jan.

Revision history for this message
Sergey Korolev (knopki) wrote :

I have the same problem as described by Jan but on Alienware 15 r2.

These devices go missing after suspend/standby:
3b:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
3c:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
3d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)

Also, bug is not Ubuntu-related. I try Arch linux with 4.6.4 and 4.7.2 kernels with same results.

Revision history for this message
penalvch (penalvch) wrote :

Sergey Korolev, 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.

Revision history for this message
Sergey Korolev (knopki) wrote :

Jan Stutzki, if the problem is still relevant.
Temporary workaround found: acpiphp.disable=1 boot parameter.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.