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

[James Deibele]

I was asked to report this

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-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/controlC0: jamesd 1660 F.... pulseaudio
 /dev/snd/pcmC0D0p: jamesd 1660 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdffdc000 irq 16'
   Mixer name : 'SigmaTel STAC9227'
   Components : 'HDA:83847618,102801db,00100201'
   Controls : 36
   Simple ctrls : 23
Date: Mon Apr 19 06:51:03 2010
Failure: oops
HibernationDevice: RESUME=UUID=7f3ce0a1-a4ac-4268-9675-d98caac3e19c
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Dell DXP061
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=a5cbbb28-7a2e-4636-9087-e1bf03c1e035 ro quiet splash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
Title: [195980.117021] ------------[ cut here ]------------
dmi.bios.date: 05/24/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 0CT017
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd05/24/2007:svnDellInc.:pnDellDXP061:pvr:rvnDellInc.:rn0CT017:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXP061
dmi.sys.vendor: Dell Inc.

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi,
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. Typically you'll see something similar to "PM: resume devices took 17.420 seconds" in your dmesg output when this happens. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi,

Looking at your Dmesg log, we can find several errors like this:

...
[ 6.551462] end_request: I/O error, dev sr0, sector 0
[ 6.551502] Buffer I/O error on device sr0, logical block 0
...

Some reporters say that this could be due to two IDE devices (HDD and CD-ROM, for example) IDE based, conected with same IDE cable, and both with "cable selection" switch.

Please, can you check this? If, so, please put one as master and other as slave, and report back again.

[.salo (dwsalo)]

On 06.05.2010 18:08, ^_Pepe_^ wrote:
> *** This bug is a duplicate of bug 464552 ***
> https://bugs.launchpad.net/bugs/464552
>
> Hi,
>
> Looking at your Dmesg log, we can find several errors like this:
>
> ...
> [ 6.551462] end_request: I/O error, dev sr0, sector 0
> [ 6.551502] Buffer I/O error on device sr0, logical block 0
> ...
>
> Some reporters say that this could be due to two IDE devices (HDD and
> CD-ROM, for example) IDE based, conected with same IDE cable, and both
> with "cable selection" switch.
>
> Please, can you check this? If, so, please put one as master and other
> as slave, and report back again.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

Hi,

I have CD-ROM and HDD connected via SATA interface. So I haven't two
devices on one cable.

--

    Віталій Дмитрук

[^_Pepe_^ (jose-angel-fernandez-freire)]

So, it's not a IDE problem

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi again,

Your dmesg (original reporter) also includes a warning regarding HDD

"warning: maximal mount count reached, running e2fsck is recommended"

Please, consider to run

sudo e2fsck -pcfv /dev/xxxx where xxxx is the / partition with a LiveCD version.

Thanks

[Jeremy Foshee (jeremyfoshee)]

Hi James,

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 17.420 seconds. I'm setting this to traiged for further investigation. Thanks!

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

[penalvch (penalvch)]

James Deibele, 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.dell.com/support/drivers/us/en/19/DriverDetails?driverId=R172927 an update is available for your BIOS (2.5.3). 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

[Launchpad Janitor (janitor)]

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