Comment 29 for bug 63967

Could not find that particular error but did find these errors in kern.log:
(log attached)
Mar 7 19:31:15 wil-desktop kernel: [ 917.900170] ACPI handle has no context!
Mar 7 19:31:15 wil-desktop kernel: [ 919.192908] ohci_hcd 0000:00:02.0: wake-up capability disabled by ACPI
Mar 7 19:31:15 wil-desktop kernel: [ 986.505392] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
19:31:15 wil-desktop kernel: [ 986.505392] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() state_store+0x0/0xd0
Mar 7 19:33:04 wil-desktop kernel: [ 0.000000] ACPI Warning (tbfadt-0442): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000000/1 [20080609]

-----Original Message-----
From: "TJ" [<email address hidden>]
Date: 02/27/2009 04:58 PM
To: <email address hidden>
Subject: Re: [Bug 63967] Re: machine does not wake up after suspend

Note: Original message sent as attachment

------------------------------------------------------------
Learn digital and video photography techniques, lighting and printing. Click now.
Photography School
http://tagline.excite.com/fc/FgElN1g44JfaVnAdM8BpgO3oxkjYV13Kio6dTfbXf1ksfU6OQkU64Z5z8qM/

The key to this issue may be given by the following clue from
/var/log/kern.log:

ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20080609]
ACPI: RTC can wake from S4

Which, if it is indicating the root cause, indicates a 'bad' ACPI DSDT.

If you're experiencing this issue with Hardy, Intrepid or Jaunty could
you please search the logs after recovering from this issue and report
the results:

grep '\(ACPI Error\|RealTimeClock\|RTC can wake\)'
/var/log/kern.log{,.0} | tee /tmp/lp63967.log

If that shows results attach /tmp/lp63967.log to this bug report.

--
machine does not wake up after suspend
https://bugs.launchpad.net/bugs/63967
You received this bug notification because you are a direct subscriber
of a duplicate bug.

YnVud!