Bug 19412
| Summary: | no wakeup via PS/2 keyboard on Linux, works on Windows | ||
|---|---|---|---|
| Product: | Power Management | Reporter: | Artem S. Tashkinov (aros) |
| Component: | Hibernation/Suspend | Assignee: | power-management_other |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | lenb, rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.35 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 7216 | ||
| Attachments: |
acpidump (followed by: Wrong checksum for generic table!)
lspci |
||
|
Description
Artem S. Tashkinov
2010-10-01 07:28:36 UTC
Created attachment 32172 [details]
acpidump (followed by: Wrong checksum for generic table!)
This bug is filed against 2.6.35 Has this feature worked on any previous versions of Linux? Please show the output from "cat /proc/acpi/wakeup" BTW. what model is this system? Created attachment 32182 [details] lspci (In reply to comment #2) > This bug is filed against 2.6.35 > Has this feature worked on any previous versions of Linux? > > Please show the output from "cat /proc/acpi/wakeup" > > BTW. what model is this system? lspci output is attached, it's a desktop with Intel H55 chipset based motherboard. cat /proc/acpi/wakeup Device S-state Status Sysfs node P0P1 S4 *disabled P0P3 S4 *disabled P0P4 S4 *disabled P0P5 S4 *disabled P0P6 S4 *disabled BR1E S4 *disabled pci:0000:00:1e.0 PS2K S4 *disabled pnp:00:09 UAR1 S4 *disabled pnp:00:0a EUSB S4 *disabled USB0 S4 *disabled pci:0000:00:1d.0 USB1 S4 *disabled USB2 S4 *disabled USB3 S4 *disabled USBE S4 *disabled USB4 S4 *disabled pci:0000:00:1a.0 USB5 S4 *disabled USB6 S4 *disabled BR20 S4 *disabled pci:0000:00:1c.0 BR21 S4 *disabled BR22 S4 *disabled BR23 S4 *disabled BR24 S4 *disabled pci:0000:00:1c.4 BR25 S4 *disabled pci:0000:00:1c.5 BR26 S4 *disabled BR27 S4 *disabled I've forgotten to mention that no kernel releases ever worked here (in regard to this little bug), I just added Linux 2.6.35 because it's what I'm currently running. Please try to run "echo PS2K > /proc/acpi/wakeup" (as root) and send the contents of this file after that. [root@localhost ~]# echo PS2K > /proc/acpi/wakeup [root@localhost ~]# cat /proc/acpi/wakeup Device S-state Status Sysfs node P0P1 S4 *disabled P0P3 S4 *disabled P0P4 S4 *disabled P0P5 S4 *disabled P0P6 S4 *disabled BR1E S4 *disabled pci:0000:00:1e.0 PS2K S4 *enabled pnp:00:09 UAR1 S4 *disabled pnp:00:0a EUSB S4 *disabled USB0 S4 *disabled pci:0000:00:1d.0 USB1 S4 *disabled USB2 S4 *disabled USB3 S4 *disabled USBE S4 *disabled USB4 S4 *disabled pci:0000:00:1a.0 USB5 S4 *disabled USB6 S4 *disabled BR20 S4 *disabled pci:0000:00:1c.0 BR21 S4 *disabled BR22 S4 *disabled BR23 S4 *disabled BR24 S4 *disabled pci:0000:00:1c.4 BR25 S4 *disabled pci:0000:00:1c.5 BR26 S4 *disabled BR27 S4 *disabled after the change above, does wakeup from PS2 keyboard work? Yes, it now works. So you need to make your init scripts to apply the above workaround. Wakeup devices are not enabled by default by the kernel. (In reply to comment #9) > So you need to make your init scripts to apply the above workaround. > > Wakeup devices are not enabled by default by the kernel. Even if they are explicitly specified in BIOS as devices that are indeed wakeup events? Can you please shed light on why Linux developers decided to ignore all wakeup devices, regardless their wakeup state specified by BIOS? Or Linux cannot yet reliably read this kind of information from BIOS? Basically, there are BIOSes that provide us with wrong information on that. BTW, In 2.6.36 this "bug" is fixed, even though unintentionally. I don't have to alter /proc/acpi/wakeup for my PS/2 keyboard to wake up this PC ;) |