nothing visible to me, returned from hibernation

Bug #502843 reported by Kjell B.
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was under the impression that all information was already sent automatically so therefore will not re-send the result of "ubuntu-bug -p linux" (which claimed that -p is a deprecated option, please update the instructions).

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801BAICH2 [Intel 82801BA-ICH2], device 0: Intel ICH [Intel 82801BA-ICH2]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kjell 1461 F.... pulseaudio
CRDA: Error: [Errno 2] Filen eller katalogen finns inte
Card0.Amixer.info:
 Card hw:0 'I82801BAICH2'/'Intel 82801BA-ICH2 with AD1885 at irq 17'
   Mixer name : 'Analog Devices AD1885'
   Components : 'AC97a:41445360'
   Controls : 38
   Simple ctrls : 27
Date: Mon Jan 4 00:37:07 2010
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=7c817786-9697-49bf-89b3-13709368b959
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Dimension 4300
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=51b870af-295c-49c5-98f3-19324e06cf34 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
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/10/2001
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A02
dmi.board.name: Dimension 4300
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA02:bd09/10/2001:svnDellComputerCorporation:pnDimension4300:pvr:rvnDellComputerCorporation:rnDimension4300:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 4300
dmi.sys.vendor: Dell Computer Corporation

Revision history for this message
Kjell B. (bellhead) wrote :
Revision history for this message
Yosef Karo (yos) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

-Yos

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Kjell B. (bellhead) wrote :

If the below information is not sufficient, then I might just let it be.

What I did was to wake the machine from hibernation. It then started to initiate some sort of bug reporting automatically. There was an option to do some additional reporting. That might have been to launchpad, it wasn't all clear to me.

I tried to follow some instructions on the reporting page and created a number of files to attach. However, they were not visible in the Firefox file chooser, so I could not attach them.

As to your questions:
1. Last night, I hibernated the machine. This morning I woke it up from hibernation. It then insisted on me reporting some error.
2. I did not expect that error.
3. See 1, that is all apart from the information automatically attached to the report.

It seems I can only add one attachment below. There were four requested, so I will add three extra comments for those that I cannot attach below.

Revision history for this message
Kjell B. (bellhead) wrote :

Second attachment. It doesn't make much sense to me when uname -a is already provided.

Revision history for this message
Kjell B. (bellhead) wrote :

Third attachment.

Revision history for this message
Kjell B. (bellhead) wrote :

Fourth attachment.

Yosef Karo (yos)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Yosef Karo (yos) wrote :

Ok, thank you. Please keep us informed if this happens again or continues to happen on a regular basis. For now I am keeping this bug marked as new since it doesn't seem to appear clear to you or to me what exactly the bug is. Please keep us posted.

-Yos

Revision history for this message
Kjell B. (bellhead) wrote :

I didn't experience any visible (to me) problem apart from that the system itself wanted to report something. Looking at the attached files, the only thing I could think of is the warning that is in OopsText.txt cut out from CurrentDmesg. If that is sufficient for the system to automatically create some report I wouldn't know. I'm not at all that experienced in Ubuntu (or Linux for that matter), just somewhat more experienced in FreeBSD where I've never seen the system issue reports by itself.

Andy Whitcroft (apw)
tags: added: karmic
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Kjell,

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

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

tags: added: suspend-test-finish
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.