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

Bug #749673 reported by Ian Lancaster
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Kernel error message upon resume. Keyboard/mouse input did not resume the computer, had to press power button.

ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-7-generic 2.6.38-7.39
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ian 1389 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6320000 irq 47'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,80860031,00100004'
   Controls : 41
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf6000000 irq 17'
   Mixer name : 'Nvidia GPU 12 HDMI/DP'
   Components : 'HDA:10de0012,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Sun Apr 3 15:51:58 2011
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=b624d441-014c-4442-8032-659ce7e10726
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=d821ef0a-c755-44f6-a524-0c0e459be7b5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-7-generic N/A
 linux-backports-modules-2.6.38-7-generic N/A
 linux-firmware 1.49
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KGIBX10J.86A.4905.2010.0402.1639
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP55KG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE47218-405
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.4905.2010.0402.1639:bd04/02/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55KG:rvrAAE47218-405:cvn:ct2:cvr:

Revision history for this message
Ian Lancaster (ianml) wrote :
Alexander Sidko (mortiy)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
mu3en (mu3en) wrote :
Revision history for this message
Alexander Sidko (mortiy) wrote :

Can somebody confirm this solution given by mu3en?

Solution:
"manually disconnecting wifi via network manager seems to prevent this happenning.
since this system is running Broadcom STA driver via jockey, probably a similar suspend/resume issue as in previous releases related to Broadcom drivers.

and therefore changing the following line in /etc/default/acpi-support
STOP_SERVICES=""
to
STOP_SERVICES="networking"
has solved the crash on suspend resume.

changing the following line in /etc/default/acpi-support
MODULES=""
to
MODULES="wl"
also solves the crash.

no obvious difference in speed or stability between this and the above.

Revision history for this message
Ingo Busse (ingo-busse-web) wrote :

Tried the first solution (STOP_SERVICES="networking") in my environment. It does not change anything.

Revision history for this message
apopovas (apopovas) wrote : Re: [Bug 749673] Re: WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish 0x86/0x90()

Same for me

On Wed, 2011-04-06 at 10:29 +0000, Ingo Busse wrote:
> Tried the first solution (STOP_SERVICES="networking") in my environment.
> It does not change anything.
>

Revision history for this message
Toby Smithe (tsmithe) wrote :

2011/4/6 Ingo Busse <email address hidden>:
> Tried the first solution (STOP_SERVICES="networking") in my environment.
> It does not change anything.

I have tried both, and neither has any effect. Maybe it is to do with
the deprecation of those options?

Revision history for this message
mu3en (mu3en) wrote :

using MODULES="wl" no longer solves here (since kernel updates in the last two days).

using STOP_SERVICES="networking" seems to prevent the error so far though.

Revision history for this message
mu3en (mu3en) wrote :

after re enabling KDM, this crash reappeared.

resetting acpi-defaults to original values (both modules and stop_services empty) has fixed so far.

Revision history for this message
mu3en (mu3en) wrote :

crash reappeared. above changes make no difference. suspend/resume is therefore currently non-functional.

Revision history for this message
Steve Murphy (stevemurphy) wrote :

Noticed that you are seeing the exact same error message in OopsText.txt that I am seeing in bug #764788 on different hardware. Does adding GRUB_CMDLINE_LINUX="nomodeset" to /etc/default/grub help?

Revision history for this message
mu3en (mu3en) wrote :

macbook 3.1 (santa rosa - intel graphics) doesn't play nice with nomodeset. somehow looks like the usual screen image is rendered very small and split out across the screen 4 times - not usable. maybe interestingly, the archlinux live cd won't boot UNLESS the nomodeset parameter is added to the grub boot line...

Revision history for this message
Steve Murphy (stevemurphy) wrote :

Another workaround for bug #764788 iis using the proprietary driver for the video card, which resumed from suspend much faster to avoid the oops (which occurs if it takes longer than 10 seconds to resume).

In this bug, the error is:

WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()
Hardware name:
Component: resume devices, time: 60980

And it looks like it is the nouveau module's fault:

[ 6392.671712] PM: resume of drv:nouveau dev:0000:01:00.0 complete after 60983.950 msecs
[ 6392.671801] PM: resume of drv:drm dev:controlD64 complete after 60576.872 msecs

Revision history for this message
mu3en (mu3en) wrote :

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03)

guessing the driver issue doesn't apply here?

not seeing the suspend/resume issue yet since the series of updates in the last 48h though.

Revision history for this message
Toby Smithe (tsmithe) wrote :

The last set of updates disabled kernel oops reporting, so that's probably why you're no longer getting notifications.

Revision history for this message
mu3en (mu3en) wrote :

right, the whole apport update from the other day. that said, even before turning that off i think i hadn't seen it for a couple of suspends. will re enable and see what's going on at this point. the resume cycle does appear to vary fairly significantly in length each time though.

Revision history for this message
penalvch (penalvch) wrote :

Ian Lancaster, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, 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 (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc3

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.

tags: added: bios-outdated-5936
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
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.

Other bug subscribers

Remote bug watches

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