[RESUME 15.076s] slow resume after suspend to ram

Bug #484183 reported by Heiko Scheit
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

From the dmesg output it seems that there might be a problem with device MAT0019:00.
It failed to resume and it also seems to take a long time.

[ 315.780104] sdhci-pci 0000:06:00.1: restoring config space at offset 0x3 (was 0x800000, writing 0x802010)
[ 315.780122] sdhci-pci 0000:06:00.1: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
[ 329.008420] PM: Device MAT0019:00 failed to resume: error -22

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3106 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc604000 irq 22'
   Mixer name : 'Analog Devices AD1884'
   Components : 'HDA:11d41884,10f70000,00100100 HDA:14f12c06,10f70000,00100000'
   Controls : 30
   Simple ctrls : 18
Date: Tue Nov 17 13:31:20 2009
DistroRelease: Ubuntu 9.10
Failure: oops
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-W7BWYAJC
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/28/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V1.00L10
dmi.board.name: CFW7-1
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.00L10:bd09/28/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-W7BWYAJC:pvr001:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCFW7-1:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-W7BWYAJC
dmi.product.version: 001
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

Revision history for this message
Heiko Scheit (h-scheit) wrote :
Revision history for this message
Heiko Scheit (h-scheit) wrote :

I should add the computer was booted directly from a Karmic CD.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Heiko,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Based on your dmesg output I see PM: resume devices took 15.076 seconds. I'm setting this to traiged for further investigation. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

tags: added: suspend-test-finish
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Andy Whitcroft (apw)
tags: added: kernel-karmic
Revision history for this message
Heiko Scheit (h-scheit) wrote :

There is another problem, but only when the laptop runs on battery. There seems to be some time limit for entering the password after suspend. After that limit the laptop goes to sleep again.

So, due to the long time it takes to resume, I sometimes just see the login screen for 1-2 seconds before the laptop goes to sleep again. This is quite annoying, actually almost unacceptable. Imaging you have to give a presentation and all people see is that you laptop wakes up and goes to sleep again... So, maybe the importance of this bug should be increased.

I can also try to find out what the problem is, if you give me some hints where to start. It seems the problem is caused by ' Device MAT0019:00'. Do you know what this is? Maybe it is not needed and this can be skipped?

[ 315.780122] sdhci-pci 0000:06:00.1: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100006)
[ 329.008420] PM: Device MAT0019:00 failed to resume: error -22

Revision history for this message
Alexey Spiridonov (snarkmaster) wrote :

I may have reported a duplicate of this bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/490742

At any rate, the overall form of the bug seems similar, even though the dmesg lines look different.

I should say that I previously had other lines surrounding my 20-second gap. I removed those modules, but that did not help at all. The gap remained, even though the adjacent lines were all different.

Andy Whitcroft (apw)
summary: - slow resume after suspend to ram
+ [RESUME 15.076s] slow resume after suspend to ram
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.