[Apple Computer, Inc. MacBookPro2,2] suspend/resume failure

[Paul Oranje]

on resume: OOPS

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
Annotation: This occurred during a previous suspend, and prevented the system from resuming properly.
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gdm 1230 F.... pulseaudio
                      paul 1630 F.... pulseaudio
Date: Mon Oct 9 16:06:32 2017
DuplicateSignature: suspend/resume:Apple Computer, Inc. MacBookPro2,2:MBP22.88Z.00A5.B07.0708131242
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=50186c73-ecfa-4adb-b6f5-f58e122e4efa
InstallationDate: Installed on 2016-05-09 (518 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
InterpreterPath: /usr/bin/python3.6
MachineType: Apple Computer, Inc. MacBookPro2,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=6e9f60c0-8848-4ceb-bb41-857369395b7d ro nomodeset quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic N/A
 linux-firmware 1.169
SourcePackage: linux
Title: [Apple Computer, Inc. MacBookPro2,2] suspend/resume failure
UpgradeStatus: Upgraded to artful on 2017-10-03 (6 days ago)
UserGroups:

dmi.bios.date: 08/13/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP22.88Z.00A5.B07.0708131242
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F42187C8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F42187C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP22.88Z.00A5.B07.0708131242:bd08/13/07:svnAppleComputer,Inc.:pnMacBookPro2,2:pvr1.0:rvnAppleComputer,Inc.:rnMac-F42187C8:rvrPVT:cvnAppleInc.:ct8:cvrMac-F42187C8:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro2,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Paul Oranje (por)]

Extra info:
In grub "nomodeset" is added to the kernel command line, without the MBP does not boot and seems to hang in initrd. It seems that something goes wrong within the radeon driver. With nomodeset set KMS is skipped and the radeon driver (GPU X1600) is used, Wayland isn't run, but xorg-server is run instead.

The reported logs apply to running with nomodeset, maybe on resume it still tries to load radeon.
A fix that would allow using the radeon driver with KMS (and run Wayland on top of that) might also fix the resume issue.

[Joseph Salisbury (jsalisbury)]

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.14 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.14-rc4

[Paul Oranje (por)]

A test with the upstream kernel 4.14 RC4 yielded same (erroneous) result; the requested has been added. The bug status has been set to Confirmed as requested (though that state should not be set by the reporter, i.e. me).

Running the system with Kali (kernel 4.13.0) also OOPs on resume.

Before the upgrade to Ubuntu 17.10, the system ran version 17.04, but on a **Macbook 2,1** that has an integrated GPU (Intel GMA 950) and which ran fine. After moving the hard disk into the MacbookPro 2,2 the resume OOPS was directly present (as was the problem when booted **without** nomodeset on the kernel command line). The upgrade to 17.10 was because I hoped it would be solved with the newer kernel.

A complication might be that the MBP2,2 boots loads from an i386 UEFI; the 64 bits kernel calls into the 32 bits UEFI runtime services. On the Macbook 2,1 where this was also the case, it worked well though.

[Kai-Heng Feng (kaihengfeng)]

Can you paste the dmesg with OOPS message?

[Paul Oranje (por)]

Could not produce a dmesg with the OOPS.

Though reproducible with pm-suspend which at wake-up always results in a reboot, no "BUG:" "Oops" or "Stack trace" can be found in any logfile afterwards. The file /var/log/dmesg is always empty, neither contains /var/log/kern.log OOPS traces.

Suggestions on how to catch it are welcome (to my knowledge no serial or net console are available easily on the MBP).

[Kai-Heng Feng (kaihengfeng)]

Don't use pm-suspend. Use `systemctl suspend` instead.
Also, file an upstream bug at https://bugzilla.freedesktop.org.

[Paul Oranje (por)]

When the MBP is booted in BIOS legacy mode, suspend and resume work.

[Kai-Heng Feng (kaihengfeng)]

This guide might be a good place to start:

https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

[Kai-Heng Feng (kaihengfeng)]

Please try kernel here:

http://people.canonical.com/~khfeng/lp1722285/