On Sat, Sep 23, 2006 at 09:16:58AM +0100, José Matos wrote:
On Friday 22 September 2006 22:30, Dave Jones wrote:
>
> Not really. If we held up the release for every machine that didn't
> suspend/resume, we'd never ship anything.
>
> The only real blocker items wrt to the kernel are
>
> "doesn't install"
> "doesn't boot"
> "can't download updates"
> "corrupts data"
That is fair. I am curious though, I have the same experience here, several
of our laptops stopped suspending/hibernating properly after 2.6.16. Just for
curiosity, what changed in this area and what needs to be done to fix it?
Not entirely sure, though there has been some positive feedback
that 2.6.18 fixes the issues a lot of people saw in 2.6.17.
There still remain some that are not working though :-/
Dave