From report #760131
Comment #1 - chromium-browser, PS/2 keyboard/mouse/touchpad interrupt, thunderbird-bin, gwibber-service, ubuntuone-syncd, desktopcouch - The system is not idle, non-idle systems cannot have sub 200 wakeups, as they system is busy being used.
Comment #10 - chrome, iwlagn - System is busy being used, and not idle.
Comment #12 - 91 wakeups, looks pretty idle
Comment #13 - firefox, gtk-gnash, mc, wget, grep - Not an idle system
Comment #51 - First result, fairly idle and < 100 wakeups. Second result - gwibber, nautilus, etc - Not idle
Comment #54 - The entire process list isn't included, invalid.
Comment #53 - Sub 100 wakeups
Comment #65 - The entire process list isn't included, invalid.
Comment #66 - Chromium, Docky - System not idle
Comment #67 - 21 wakeups
Comment #82 - USB OPTICAL MOUSE .. USB input devices drain batteries and cause wakeups. There are other external devices connected.
Comment #85 - PS/2 keyboard/mouse/touchpad interrupt - Not idle, and incomplete process list.
All of the reports are using Powertop 1.13, but kernels newer than 2.6.36 (that some people were using) need 1.97.
This report seems to be filled with comments by people that don't know how to test for issues like the one being reported. That's not a problem with the reporters, as they just don't know how to test it which isn't their fault.
To properly test it, the system should be completely idle with all applications closed, and all external keyboards, mice, hard drives, flash drives, or whatever disconnected. You can't have a busy system and expect the processor to stay sleep, that is simply illogical.