This will be quite unusual stabilization request :) Please test and stabilize following versions of sys-kernel/tuxonice-sources: * 2.6.30-r11 * 2.6.31-r11 * 2.6.32-r7 (I'll file separate bug for 2.6.33-r* when gentoo-sources-2.6.33-r* goes stable). All of above versions use exactly the same TuxOnIce code (version 3.1) - the only difference is in base kernel and genpatches. Testing all those kernels probably is not worth time and testing just one of them should be ok, bugs in TOI code should be the same in all those kernels (I hope that there are no such bugs). Base kernel + genpatches are tested as part of gentoo-sources stabilization process so actually only TOI code path should be tested throughly; please suspend, hibernate and wakeup your machine a few times.
I tested on .31 and .32. Seems to work fine
Adding amd64 back :) I've started a discussion on gentoo-kernel mailing list whenever we even want to have non-core kernels (other than {gentoo,vanilla}-sources) stabilized, so don't worry about this bug yet :)
amd64 stable
tested 2.6.32-r7 and had that weird keyboard input bug where keyboard input is delayed to the point of can't even use the keyboard and repeat keys etc. please reference https://bugs.launchpad.net/gentoo/+bug/124406 -lance
created in /etc/portage/package.mask: =sys-kernel/tuxonice-sources-2.6.32-r7 =sys-kernel/tuxonice-sources-2.6.31-r11 due to the keyboard input delay problem. now running 2.6.30-tuxonice-r11 and it seems to be working nicely. i can even hibernate and wireless network is operational upon resume. should i disable iwlagn rfkill option in kernel?
x86: can you stabilize those kernels? About keyboard issue: if it is not tuxonice-specific it should not block this stabilization.
(In reply to comment #7) > x86: can you stabilize those kernels? It is on my list for today.
x86 stable, gentoo-sources 2.6.33 is going stable in bug 325335. Closing
