Sleep then log back in then kernel error

[Hello3171]

Ubuntu 9.10 (Just a couple of days after upgrade from 9.04).
I accidentally pressed the "sleep" button on my keyboard which caused it to suspend. (More accurately, I was whacking it to remove dust, etc. from inside the keyboard and the computer slept by itself.)
Then I turned it back on and was allowed to log back in (ie. my account was locked and the computer did not have to boot from the beginning).
Then the Report a Bug applet/icon appeared saying that there was a kernel error or something along those lines and it said that I should report the problem and I just followed the instructions to here.

However, I am still using the computer and nothing appears to be wrong.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: qasim 1956 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfb100000 irq 22'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1458e601,00100001'
   Controls : 40
   Simple ctrls : 22
Date: Fri Oct 30 20:01:48 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=82249c58-8492-480e-8fd8-f1561024dfa7
MachineType: Gigabyte Technology Co., Ltd. P35-DS3L
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=1c70a24a-d0ee-4af1-b2f1-ccb8475f7251 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:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
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
WpaSupplicantLog:

dmi.bios.date: 07/10/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: P35-DS3L
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.:bvrF8:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Hello3171 (hello3171)]

I just tried playing several different videos and the colour is off on all of them (however the sound seems okay).

(Note: I tried editing the bug report but I wouldn't update even after several several seconds and two attempts.)

[Hello3171 (hello3171)]

Sorry, the previous comment appears to be wrong. I'm not sure whether Totem changed the Hue setting by itself or what, but it was the Hue that was wrong. Once I reset it, the colour was fine.

[Leann Ogasawara (leannogasawara)]

Hi Hello3171,

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 9.072 seconds. 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.]