Ubuntu
linux package

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

Bug #566344 reported by Joel Gabor on 2010-04-19

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned
Nominated for Lucid by Joel Gabor

Bug Description

I suspended an up2date Lucid. When I waked up the system, I saw the crash report.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic-pae 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
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: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: george 2337 F.... pulseaudio
/dev/snd/pcmC0D0p: george 2337 F...m pulseaudio
/dev/snd/seq: timidity 2242 F.... timidity
CRDA: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe9300000 irq 22'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 43
   Simple ctrls : 24
Date: Mon Apr 19 01:56:15 2010
Failure: oops
HibernationDevice: RESUME=UUID=9e0a8e23-b879-4699-a956-5fe3b3d2a8e6
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
ProcCmdLine: root=UUID=0a2c56b9-1bf5-410a-9d8e-1156ae522e73 ro quiet splash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

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

dmi.bios.date: 09/06/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/06/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Tags:

Revision history for this message

Joel Gabor (joelgabor) wrote on 2010-04-19:

AlsaDevices.txt Edit (587 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (277 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (421 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (50.3 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.2.txt Edit (11.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (45.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (278 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (28.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (705 bytes, text/plain; charset="utf-8")
OopsText.txt Edit (1.8 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.0 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (134.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (262.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (163.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-04-21:

Hi Joel,

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 12.956 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

Revision history for this message

Joel Gabor (joelgabor) wrote on 2010-04-23:

Hello Jeremy,
as I've written, I saw the automatic crash-report after suspend. So I reported it, but I didn't notice no any serious problem, only this crash-report.

Revision history for this message

penalvch (penalvch) wrote on 2013-05-26:

Joel Gabor, 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 http://www.gigabyte.com/products/product-page.aspx?pid=2627#bios an update is available for your BIOS (F14). 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

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

apport-collect -p linux <replace-with-bug-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

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-07-26:

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

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

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

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package