On Mon, 22 Feb 2010, Rafael J. Wysocki wrote: > > Here's what I got: > > > > [ 3.349334] PM: Resume from disk failed. > > [ 3.350060] Magic number: 0:141:321 > > [ 3.352583] hash matches drivers/base/power/main.c:477 > > [ 3.355144] tty tty46: hash matches > > [ 3.357742] i915 0000:00:02.0: hash matches > > > > So it appears that the video driver is indeed the culprit. Is there > > any way to narrow it down further? > > Not without adding some debug code to the driver. > > Which version of the kernel is this? 2.6.33-rc8. The same problem occurs with earlier versions, such as Fedora 12's 2.6.31.9 (which is what I'm running now). > > Here's my /proc/acpi/wakeup: > > > > Device S-state Status Sysfs node > > P0P4 S4 disabled pci:0000:00:1e.0 > > MC97 S4 disabled > > USB1 S4 disabled pci:0000:00:1d.0 > > USB2 S4 disabled pci:0000:00:1d.1 > > USB3 S4 disabled pci:0000:00:1d.2 > > USB4 S4 disabled pci:0000:00:1d.3 > > EUSB S4 disabled pci:0000:00:1d.7 > > PS2K S4 disabled pnp:00:09 > > PS2M S4 disabled pnp:00:0a > > GBEN S4 disabled > > > > It appears that PS2K is the keyboard. If I write "PS2K" to > > /proc/acpi/wakeup, I get: > > > > ACPI: 'PS2M' and 'PS2K' have the same GPE, can't disable/enable one seperately > > > > Apart from the misspelling, this doesn't bode well for making the > > keyboard a wakeup device. > > This only means both will be enabled at the same time. > > > Furthermore, these values are not properly tied to the values in sysfs. > > They are independent and the sysfs values probably don't matter for these > devices. What are the contents of /proc/acpi/wakeup after writing PS2K to it? Unchanged -- both PS2K and PS2M continue to be disabled. Why are the values independent from the wakeup settings in sysfs? Aren't they supposed to mean the same thing? Alan Stern _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
