Ubuntu
linux package

WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()

Bug #553750 reported by Roger Binns
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Red splat appeared in system tray saying that a serious problem had been detected and gave no further information other than asking to report it.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-18-generic 2.6.32-18.27
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rogerb 1619 F.... pulseaudio
 /dev/snd/controlC0: rogerb 1619 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf3120000 irq 22'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,80860033,00100004'
   Controls : 41
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'DVC90'/'Pinnacle Systems GmbH DVC90 at usb-0000:00:1a.0-1.3, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB2304:0207'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Line',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 16
   Mono: Capture 0 [0%] [0.00dB] [on]
Date: Thu Apr 1 19:53:02 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=e563b9f6-c665-4905-bd8f-0f325ba9273c
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-18-generic root=/dev/mapper/hostname-root ro ipv6.disable=1
RelatedPackageVersions: linux-firmware 1.33
RfKill:

SourcePackage: linux
Title: [18446744058.468016] ------------[ cut here ]------------
dmi.bios.date: 03/17/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KGIBX10J.86A.4816.2010.0317.1519
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55WG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE57269-404
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.4816.2010.0317.1519:bd03/17/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr:

Revision history for this message
Roger Binns (ubuntu-rogerbinns) wrote :
Revision history for this message
Roger Binns (ubuntu-rogerbinns) wrote :

This appears to happen every time I suspend to RAM. There are no visible symptoms other than the red splat in the system tray desperate for me to report a problem without giving any details.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Re: [RESUME 10.140] WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53 suspend_test_finish+0x88/0x90()

Hi Roger,

The warning reported here (see OopsText.txt) 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 10.140 seconds. I'm setting this to traiged for further investigation. Thanks!

summary: - I have no idea what it is complaining about
+ [RESUME 10.140] WARNING: at
+ /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
+ suspend_test_finish+0x88/0x90()
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
tags: added: suspend-test-finish
Jeremy Foshee (jeremyfoshee)
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Roger Binns, thank you for reporting this and helping make Ubuntu better. Lucid reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, as per https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+5+Series+Chipset+Boards&ProductProduct=Intel%C2%AE+Desktop+Board+DP55WG an update is available for your BIOS (5936). If you update to this, does it change anything?

As well, once complete, please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Also, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could 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. 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.10-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.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

tags: added: bios-outdated-5936
Changed in linux (Ubuntu):
status: Triaged → Incomplete
summary: - [RESUME 10.140] WARNING: at
- /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
+ WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
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.
Subscribing...

Other bug subscribers

Remote bug watches

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