Hi Benjamin The results are as follows. Please see the attached log file tracking the fetch, checkout, build, etc.. The quick test worked after a replug. After a full install into the 3.2.0-38-generic kernel, I performed the usual power cycle test, and it passed 20/20 times. For comparison, the out-of-the box version for the 3.2.0-38-generic kernel passed 6/20 times. Checking these results via Fisher's Exact Test leads to a 1-tailed p-value less than 0.0001, 'extremely significant' (1-tailed statistics is valid here because we are only interested in improvements). In short, it works at least as well as the workaround I tested earlier. Here is the 2*2 contingency table: Outcome Pass Fail No Fix 6 14 'for-bob' 20 0 One fly in the ointment which I noticed is this seems to have introduced a new bug with regard to Logitech keyboard behaviour. See below. _Short Description:_ The first character typed on a Logitech keyboard using the Logitech Unifying Receiver after power-up is frequently lost. _Long Description:_ When using a Logitech keyboard linked via a Logitech Unifying Receiver, the first character typed after power-up is often not registered. This does not happen every time, but at least 75% of trials during a power cycle test. The practical consequences are that after power-on, when you enter your password, without checking the number of characters recorded in the password box, you are likely to have to re-enter your password if you have not touched the mouse first. _Steps to reproduce:_ Power cycle the computer, booting in the appropriate kernel. At the login screen, hit the Logitech keyboard spacebar 3 times. _Expected behaviour:_ There should be 3 dots in the password box. _Observed behaviour:_ On at least 75% of trials there are only 2 dots in the password box. _Workaround (2 options):_ 1) Always move the (Logitech) mouse first. 2) Pay particular attention to the appearance of the first-typed character in the password box and re-type it if it does not immediately appear. I hope this helps. Your solution seems to be very close now. Best Wishes Bob On 04/03/13 17:07, Benjamin Tissoires wrote: > On Mon, Mar 4, 2013 at 6:06 PM, Benjamin Tissoires >