[Dell Inspiron 1464] Failed to resume from suspend in Raring

Bug #1205270 reported by Deepak
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Today I updated some packages but not linux kernel. I put my laptop to sleep by pressing power button. It failed to resume when I pressed power button again. This is not a new problem, I have been facing this problem for quite some time.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-26-generic 3.8.0-26.38
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: deepak 2248 F.... pulseaudio
 /dev/snd/controlC0: deepak 2248 F.... pulseaudio
Date: Fri Jul 26 15:43:22 2013
HibernationDevice: RESUME=UUID=df385c27-459c-4234-ae18-838535d5edf2
InstallationDate: Installed on 2012-04-15 (466 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
Lsusb:
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam
MachineType: Dell Inc. Inspiron 1464
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=3636c498-a6df-4f78-8265-c997d8ed4364 ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor acpi_osi=Linux vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-26-generic N/A
 linux-backports-modules-3.8.0-26-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-01-24 (182 days ago)
dmi.bios.date: 03/29/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0DXD7H
dmi.board.vendor: Dell Inc.
dmi.board.version: A13
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A13
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1464:pvrA13:rvnDellInc.:rn0DXD7H:rvrA13:cvnDellInc.:ct8:cvrA13:
dmi.product.name: Inspiron 1464
dmi.product.version: A13
dmi.sys.vendor: Dell Inc.

Revision history for this message
Deepak (deepakiitr2015) wrote :
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
Revision history for this message
Deepak (deepakiitr2015) wrote : Re: failed to resume from suspend

I found another bug closely related but in 12.04 LTS
https://bugs.launchpad.net/bugs/990129

Revision history for this message
penalvch (penalvch) wrote :

Deepak, tould you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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.11-rc2

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

tags: added: latest-bios-a13 needs-upstream-testing regression-potential
tags: added: resume suspend
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - failed to resume from suspend
+ [Dell Inspiron 1464] Failed to resume from suspend
summary: - [Dell Inspiron 1464] Failed to resume from suspend
+ [Dell Inspiron 1464] Failed to resume from suspend in Raring
Revision history for this message
Deepak (deepakiitr2015) wrote :

I tested v3.11-rc2-saucy from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

It happens more frequently in latest kernel, almost 100%.
It shows 1inch X 1inch colored grid on screen at random location when trying to resume.

I think CPU resumes but it freezes after that, because LED goes from blinking state to fully on.

Also some of the modules failed when installing latest kernel.

tags: added: kernel-bug-exists-upstream-v3.11-rc2
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Deepak, thank you for testing the newest mainline kernel. Did this problem not occur in a release prior to Raring?

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Deepak (deepakiitr2015) wrote :

As this doesn't occur all the time, I am not sure whether it was present in previous releases or not. I can't remember any crash due to sleep/resume in 12.10. But brightness change crash (https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1007765) started with 12.04.

Revision history for this message
penalvch (penalvch) wrote :

Deepak, thank you for your comments. Remaining focused on suspend/release here in this report, the next step would be to bisect this problem from Quantal to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

tags: added: regression-release
removed: regression-potential
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.