Why was a kernel-2.6.34 pushed to updates that had un-addressed bugs.

[Jan Wildeboer]

On 09/07/2010 02:32 PM, Adam Williamson wrote:

> It isn't. We can't possibly guarantee suspend/resume will work on all
> laptops in anything like a reasonable timeframe. if we set this as a
> release criterion, we would likely never release. So we don't.

Understood. It is however a royal PITA ;-) In the beginning, F13 was 
unable to use the external VGA at all in a decent manner, this started 
to work after a few kernel updates. So I was a happy camper.

The .34 kernel starts to suspends, switches to the spalsh screen and the 
gets stuck. I didn't notice the first time, so after two hours I had a 
wonderful sauna in my laptop bag and a broken fan.

Now I am back on the previous kernel and can only hope the next update 
will fix it. Will try once again to catch as many inof as possible and 
file a BZ.

Jan

-- 
Jan H Wildeboer                |
EMEA Open Source Affairs       | Office: +49 (0)89 205071-207
Red Hat GmbH                   | Mobile: +49 (0)174 33 23 249
Technopark II, Haus C          | Fax:    +49 (0)89 205071-111
Werner-von-Siemens-Ring 11 -15 |
85630 Grasbrunn                |
_____________________________________________________________________

Reg. Adresse: Red Hat GmbH,
Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15
85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243
Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham,
Charles Cachera
_____________________________________________________________________

GPG Key:     3AC3C8AB
Fingerprint: 3D1E C4E0 DD67 E16D E47A  9564 A72F 5C39 3AC3 C8AB