The time testing and discussion was beta cycle, not now.  This "one single
regression" is affecting literally thousands of users + dozens of devices and
Google confirms that to my satisfaction.

Use of 2.6.20 is not as arbitrary.  It has known workaround.  That is far more
sensible at this stage than playing with Linus's latest experiments when Google
says they're broken anyway.

One way grml could handle the problem is to put an alternate kernel/module set
in the 1.0 repository.  Then users have a choice.