Sandybridge suspend/resume regression on 3.0.0-12-generic/3.0.0-13-generic

Bug #894292 reported by Pascal Hartig
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Herton R. Krzesinski

Bug Description

I'm using a Samsung Series 9 notebook (900X3A). With 3.0.0-11-generic the suspend/resume cycle works flawlessly, but starting with 3.0.0-12-generic the notebook does not wake up anymore. The screen stays unlit and I can't toggle the Caps Lock or Fn Lock keys. There is no flashing caps lock key, either.

pm_trace did not bring up anything interesting. 3:366:726 on a first and 3:22:878 on a second test. The first time it matched the loop6 device, which was probably coincidental.

Manually downgrading to 3.0.0-11-generic works for me.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-13-generic 3.0.0-13.22
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pascal 1794 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0700000 irq 49'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,144dc098,00100100 HDA:80862805,80860101,00100000'
   Controls : 18
   Simple ctrls : 10
Date: Thu Nov 24 10:04:43 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110922)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 90X3A
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=d0588ced-58e6-4c9c-a5d8-f5d4e382de31 ro quiet splash i915.i915_enable_rc6=1 i915.semaphores=1 i915.lvds_downclock=1 i915_enable_fbc=1 pcie_aspm=force vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic N/A
 linux-backports-modules-3.0.0-13-generic N/A
 linux-firmware 1.60
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (52 days ago)
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04HL
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 90X3A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04HL:bd03/08/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn90X3A:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn90X3A:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 90X3A
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Pascal Hartig (passy) wrote :
summary: Sandybridge suspend/resume regression on
- 3.0.0-12-generic/3.0.0-12-generic
+ 3.0.0-12-generic/3.0.0-13-generic
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Revision history for this message
Herton R. Krzesinski (herton) wrote :

@Pascal Hartig: I looked at changes between -11 and -12 kernels, there isn't anything that looks like to be the cause of the issue.

Besides updating the kernel, did you make other changes? I noticed that you are using these extra kernel options at boot: "i915.i915_enable_rc6=1 i915.semaphores=1 i915.lvds_downclock=1 i915_enable_fbc=1 pcie_aspm=force". If you remove them, do you still get the resume issue?

Also to confirm the working and failing kernel versions, please run this command on both the working and failing kernels you boot: "cat /proc/version_signature /proc/cmdline", and paste the result here.

Changed in linux (Ubuntu):
assignee: nobody → Herton R. Krzesinski (herton)
Revision history for this message
Pascal Hartig (passy) wrote :

Thanks for looking into my issue, Herton. I checked once again and I found an unfortunate mistake I made. The -12 kernel does still suspend and resume without problems, it's the -13 version that introduced the resume issue.

I tried to boot with and without my custom kernel options and ran with both

Ubuntu 3.0.0-13.22-generic 3.0.6
BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=d0588ced-58e6-4c9c-a5d8-f5d4e382de31 ro quiet splash i915.i915_enable_rc6=1 i915.semaphores=1 i915.lvds_downclock=1 i915_enable_fbc=1 pcie_aspm=force vt.handoff=7

and

Ubuntu 3.0.0-13.22-generic 3.0.6
BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=d0588ced-58e6-4c9c-a5d8-f5d4e382de31 ro

into the same problems. For -11 and -12 there was no difference between using and not using the extra parameters.

Revision history for this message
Herton R. Krzesinski (herton) wrote :

Ok, looking at changes between working -12 and failing -13 kernels, I didn't found anything outstanding so far which could cause a suspend/resume failure.

When the resume fails, do you know if the machine locks up, or is just the screen which remains black? You may try to install openssh, do the suspend/resume, and try login from another machine into the notebook, to see if it's still alive.

If pm_trace really doesn't help, and really the machine is dead (locked up), probably just a bisect between the working/failing releases to try to determine what is causing the issue.

Revision history for this message
Pascal Hartig (passy) wrote :

I marked this as invalid as it turned out that my results were not fully reproducible. In fact, I had the exact them problems on -11 for no apparent reason and I'm now running on -13 for 5 days without any problems. Until I find a good way to enforce the lock-up, there's no point in looking for the cause.

Thanks for looking into it, though!

Changed in linux (Ubuntu):
status: Triaged → Invalid
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.