Sable does not resume from suspend (Intel i7 HD4000)

Bug #1177866 reported by Jason Gerard DeRose
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
System76
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

This is a regression from 3.8.0-18, and is present in both 3.8.0-19 and 3.8.0-20.

Resuming from supsend no longer works on the System76 Sable Complete all in one. When you wake up the system (either with the power button or keyboard), the hardware status will change (power light goes from blinking to solid), but the system does not resume. The backlight stays off, and I'm unable to SSH into the system. By watching our DHCP server logs, I can also confirm that the system never makes a DHCP request. So the issue is something more that just the backlight not being turned on.

Interestingly, if you happen to have a 2nd monitor connected (over HDMI), the system resumes from suspend perfectly. But if you then disconnect the 2nd monitor and try again, it wont resume.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-20-generic 3.8.0-20.31
ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11
Uname: Linux 3.8.0-20-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oem 1708 F.... pulseaudio
 /dev/snd/controlC1: oem 1708 F.... pulseaudio
CurrentDmesg: [ 14.233047] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Wed May 8 10:19:04 2013
HibernationDevice: RESUME=UUID=c6bf9bbb-b4e0-4157-866b-5cdaf9972f0a
MachineType: System76, Inc. Sable Complete
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-20-generic root=UUID=0eb0cba2-7b1c-4988-8b67-6d49d0fec820 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-20-generic N/A
 linux-backports-modules-3.8.0-20-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61AGL
dmi.board.vendor: Intel Corporation
dmi.board.version: G71256-200
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: sabc1
dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-200:cvnSystem76,Inc.:ct3:cvrsabc1:
dmi.product.name: Sable Complete
dmi.product.version: sabc1
dmi.sys.vendor: System76, Inc.

Revision history for this message
Jason Gerard DeRose (jderose) wrote :
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

A bit more digging... this is more than just the backlight not being turned on. I installed openssh-server to see if I could SSH into the system when the screen was black (after attempting to wake up)... no such luck.

And by watching our DHCP server logs, I've confirmed that this system never makes a DHCP request. The the resume process is hanging early on.

summary: - Black screen after resuming from suspend with Intel i7 HD4000
+ Sable does not resume from suspend (Intel i7 HD4000)
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
description: updated
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.9 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'.

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.9-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

We tested with the 3.9 mainline kernels, and this bug exists there as well.

tags: added: kernel-bug-exists-upstream
Brad Figg (brad-figg)
tags: added: kernel-stable-key
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.