WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()

Hi Lucas,

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 8.664 seconds" in your dmesg output when this happens. I'm setting this to traiged for further investigation. Thanks!

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

Hi Leann,

Thanks for answering so fast,
about this "kernel issue", you said that it was because my system was
slow to resume from suspend. but this is not my case, my laptop
resumes in about 1 sec. although it takes a lot of time to start, and
log when I start the computer. I really appreciate your work
concerning the improvement of gnu/linux and ubuntu.

Desde ya, muchas gracias

Lucas

2009/10/22 Leann Ogasawara <email address hidden>:
> Hi Lucas,
>
> 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 8.664 seconds" in your
> dmesg output when this happens.  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
>
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => Medium
>
> --
> WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
> https://bugs.launchpad.net/bugs/457278
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> I don't see any error, but a sign appears on my screen telling me that an error occurred, that may be critical to the stability of my computer. It also says its likely a kernel issue
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be restarted.
> AplayDevices:
>  **** List of PLAYBACK Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> Architecture: amd64
> ArecordDevices:
>  **** List of CAPTURE Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> AudioDevicesInUse:
>  USER        PID ACCESS COMMAND
>  /dev/snd/controlC0:  luks       1909 F.... pulseaudio
> CRDA: Error: [Errno 2] No existe el fichero ó directorio
> Card0.Amixer.info:
>  Card hw:0 'Intel'/'HDA Intel at 0x78300000 irq 22'
>   Mixer name   : 'Realtek ALC268'
>   Components   : 'HDA:10ec0268,10250136,00100003 HDA:11c11040,10250136,00100200'
>   Controls      : 11
>   Simple ctrls  : 8
> Date: Wed Oct 21 11:17:57 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=8514ef43-90f6-4cc1-baea-cfad4bb3f507
> MachineType: Acer Aspire 5315
> Package: linux-image-2.6.31-14-generic 2.6.31-14.48
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=01f45638-de86-4291-9eb3-c51eb400d5ea ro 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
> SourcePackage: linux
> Tags: kernel-oops
> Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
> Uname: Li...

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.