[Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl]

Bug #1055475 reported by Mario Vukelic
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Note: When the problem occurred and the apport bug report was created, the non-free wl module was loaded (compiled from bcmwl-kernel-source) to enable the Broadcom wifi. However, the same problem happens after removing the wl module and rebooting.

On this machine, suspend/resume has worked in released Ubuntu versions since its purchase mid-2009, when IIRC it received a development version install of Karmic (9.10). Hibernate/resume worked just as reliably. The latest fresh install was Oneiric (11.10), later upgraded to Precise (12.04) after release. The machine usually ran the proprietary NVidia graphics drivers, therefore I am unsure if suspend/hibernate/resume also worked with the nouveau drivers (however I seem to remember so).

I now performed a reinstall with 12.04.1 (using the BIOS image, not the EFI image) and immediately upgraded to Quantal. (For some reason I could not make Quantal CDs boot). The machine is now using the nouveau drivers because currently the backlight adjustment does not work with NVidia drivers.

In Quantal with nouveau, resume from suspend never worked for me. When going into suspended state all at first appears fine. However, the machine does not resume properly. When trying to resume, the fan and optical drive starts, however the screen remains black and I can't tell if its responsive. I pressed the power button for 5 seconds and the machine rebooted fine. After logging in, an apport prompt appeared, from which I created this bug report.
I don't know about hibernate since due to using an encrypted home directory it is not available anymore.

WORKAROUND: Resume works correctly with the proprietary nvidia-current drivers.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-15-generic 3.5.0-15.22
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mario 2337 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Mon Sep 24 09:05:58 2012
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=58df2950-5d89-42a8-a44c-3bf5410313aa
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
InterpreterPath: /usr/bin/python3.2mu
MachineType: Apple Inc. MacBookPro5,4
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 ro 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.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-15-generic N/A
 linux-backports-modules-3.5.0-15-generic N/A
 linux-firmware 1.93
RfKill:
 0: brcmwl-0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl]
UpgradeStatus: Upgraded to quantal on 2012-09-15 (8 days ago)
UserGroups:

dmi.bios.date: 06/15/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP53.88Z.00AC.B03.0906151647
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22587A1
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro5,4
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22587A1
dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1:
dmi.product.name: MacBookPro5,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Possibly similar to LP #1027828

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: kernel-suspend-watch
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.6-rc7-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

I tested the mainline kernel from [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/ as instructed.

The resume from suspend failed just like it did with the Ubuntu kernel. I should add here that like I hinted at in my original report, the machine does indeed somewhat resume: I can hear the fan starting and also the keyboard lights come on. It might just be the screen that stays black.

This is the case with the nouveau driver only. I took the opportunity to test the nvidia-current and nvidia-experimental drivers, and both the Ubuntu and the mainline kernel resume correctly from suspend with those.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

tags: added: needs-bisect
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'd also like to perform a bisect to identify the commit that caused the regression in Quantal.

Just to confirm, you don't see this bug in Precise? If that is the case, it would be helpful if you could test the following kernels:

v3.3 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
v3.5-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

tags: added: performing-bisect
removed: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

@Joseph, I don't know about Precise - when I used Precise on the machine I always ran the NVidia drivers, and with those the suspend/resume works in Quantal as well as of now. The only time I ran nouveau on Precise was the short period between installing 12.04.1 and the immediate upgrade to Quantal - and I didn't test the suspend/resume then.
I seem to remember that in earlier Ubuntu releases there were times I ran nouveau, and that suspend/resume worked back then. But it's been a long time and memory is not reliable.

I will try to find the time to open an upstream bug. It may take a few days though since some urgent stuff has unexpectedly come up on my end.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

@Joseph, after reading the upstream bug report guidelines I feel confident that I can do this, provided I don't mess it up from the start ;) Therefore a quick question if I may, thanks in advance.

For this problem, am I right in assuming that the correct maintainer is this:

6712 SUSPEND TO RAM
6713 M: Len Brown <email address hidden>
6714 M: Pavel Machek <email address hidden>

in http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS

Right?

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Sorry for spamming with description updates earlier, wanted to make sure all is clear.

I now sent the completed upstream bug report to <email address hidden> and cc'ed <email address hidden>. However Launchpad sent an error reply about a missing known GPG signature, hope that's ok then.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Repeated the test with mainline 3.6.1, still broken. I do not yet have info from the linux-pm mailing list. Will try once more and then wait again :)

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

The post to linux-pm with the info required in the upstream reporting guidelines: http://marc.info/?l=linux-pm&m=134987827814983&w=2

Revision history for this message
In , mario.vukelic (mario.vukelic-linux-kernel-bugs) wrote :
Download full text (42.2 KiB)

[1.] One line summary of the problem (downstream bug title)

[Apple Inc. MacBookPro5,4] suspend/resume failure [non-free: wl]

[2.] Full description of the downstream problem/report:
(Downstream report URL:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1055475)

Note: When the problem occurred and the apport bug report was created,
the non-free wl module was loaded (compiled from bcmwl-kernel-source) to
enable the Broadcom wifi. However, the same problem happens after
removing the wl module and rebooting.

On this machine, suspend/resume has worked in released Ubuntu versions
since its purchase mid-2009, when IIRC it received a development version
install of Karmic (9.10). Hibernate/resume worked just as reliably. The
latest fresh install was Oneiric (11.10), later upgraded to Precise
(12.04) after release. The machine usually ran the proprietary NVidia
graphics drivers, therefore I am unsure if suspend/hibernate/resume also
worked with the nouveau drivers (however I seem to remember so).

Recently I performed a reinstall with 12.04.1 (using the BIOS image, not
the EFI image) and immediately upgraded to Quantal. (For some reason I
could not make Quantal CDs boot). The machine is now using the nouveau
drivers because currently the backlight adjustment does not work with
NVidia drivers.

In Quantal with nouveau, resume from suspend never worked for me. When
going into suspended state all at first appears fine. However, the
machine does not resume properly. When trying to resume, the fan and
optical drive starts, however the screen remains black and I can't tell
if its responsive. I pressed the power button for 5 seconds and the
machine rebooted fine. After logging in, an apport prompt appeared, from
which I created this bug report.

Resume works correctly with the proprietary nvidia-current drivers.

I don't know about hibernate since due to using an encrypted home
directory it is not available anymore.

[3.] Keywords

amd64 resume suspend nouveau

[4.] Kernel version (from /proc/version):

Linux version 3.6.1-030601-generic (apw@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201210071322 SMP Sun Oct 7 17:23:28
UTC 2012

[5.] Output of Oops.. message

None that I know of, but the automated Ubuntu report says "ProblemType:
KernelOops"

[6.] A small shell script or example program which triggers the problem
(if possible)

None. Reproducible by suspending and resuming the machine.

[7.] Environment (lsb_release -rd)

Description: Ubuntu 12.10
Release: 12.10

[7.1.] Software (add the output of the ver_linux script here)

Linux chronic 3.6.1-030601-generic #201210071322 SMP Sun Oct 7 17:23:28
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Gnu C 4.7
Gnu make 3.81
binutils 2.22.90.20120924
util-linux 2.20.1
mount support
module-init-tools 3.16
e2fsprogs 1.42.5
pcmciautils 018
PPP 2.4.5
Linux C Library 2.15
Dynamic linker (ldd) 2.15
Procps 3.3.3
Net-tools 1.60
Kbd 1.15.3
Sh-utils 8.13
Modules Loaded msr michael_mic arc4 dm_crypt
snd_hda_c...

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

There was no reply to my mailing list post, so I created an upstream bug report and linked the Launchpad bug. I tried to do everything as required by the instructions, and I hope I managed ...

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Mario Vukelic, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

description: updated
Changed in linux (Ubuntu):
importance: Medium → Low
status: Triaged → Incomplete
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

This was resolved somewhere along the way long ago

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
In , mario.vukelic (mario.vukelic-linux-kernel-bugs) wrote :

This got fixed somewhere along the way quite long ago. Thank you

Changed in linux:
status: Confirmed → Invalid
Brad Figg (brad-figg)
tags: added: cscc
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.