Resume From Suspend Unresponsive with Quantal 3.5.0-5 kernel on Quantal

[Stefan Skotte]

After updating from Quantal kernel 3.5.0-4 -> 3.5.0-5 I cannot resume the machine after suspend to ram anymore.

It worked great in 3.5.0-4, so there must be a regression / change somewhere.

This happens if I leave the computer for more than 10-15 minutes in suspend (ie. just suspending, and waking it up immediately works fine).

[Stefan Skotte (screemo)]

This happens for me on an UX32VD (ivy bridge, core i7).

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1027380

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[johannes (di)]

same here

[johannes (di)]

ApportVersion: 2.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: johannes 1895 F.... pulseaudio
CRDA:
 country CH:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=1142866e-9e92-4e17-bbd7-33a039a00c85
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: ASUSTeK Computer Inc. UX31E
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-5-generic root=UUID=ebb35ad3-43af-4746-84fb-fb6ab7996063 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-5-generic N/A
 linux-backports-modules-3.5.0-5-generic N/A
 linux-firmware 1.85
StagingDrivers: rts5139
Tags: quantal staging
Uname: Linux 3.5.0-5-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-06-23 (28 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[johannes (di)]

apport information

[Rik Mills (rikmills)]

Duplicate of bug? #1027182

[Rik Mills (rikmills)]

Sorry. Meant https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1027182

[johannes (di)]

could very well be, that might explain why it is only an issue to resume after a longer period of time and not when waking up immediately again.

[Rik Mills (rikmills)]

If it is that, then a daily mainline build from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

should not have the same problem as was apparently fixed upstream on Monday.

[johannes (di)]

I can confirm that i can sucessfully resume after being suspended for about 1 hour with this kernel:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc1-quantal/linux-image-3.5.0-030500rc1-generic_3.5.0-030500rc1.201206022335_amd64.deb

[Rik Mills (rikmills)]

Well, that is a RC1.

So as the above bug wasn't introduced until the RC7 kernel, the fact that the RC1 is not effected is not surprising.

Can you try with a post RC7 build? i.e. such as the daily build in the link I posted earlier.

That is the most recent mainline build, in which the bug from the RC7 it is supposedly fixed.

If that works OK, then when the kernel team rebase to the next RC8 and upload ubuntu kernel based on that the problem should resolve itself without anyone having to do anything more.

[johannes (di)]

yeah got the wrong one before you posted that, now trying the daily build and will report back.

[Almanildo (audunskaugen)]

I had the same problem (using the 3.5.0-5 kernel from xorg-edgers on a ux31a), and the daily kernel seems to resolve the issue.

[johannes (di)]

yes the (yester) daily works for me too
 http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/linux-image-3.5.0-999-generic_3.5.0-999.201207210420_amd64.deb