Thanks Adam. It would also be helpful if you could test the latest kernel and just verify the issue still exists and reattach an updated dmesg output after a failed suspend/resume cycle as you did previously. I'm reassigning to the kernel team. Also please note that we'll keep this open against the actively kernel but will be closed against 2.6.22. Thanks.
Thanks Adam. It would also be helpful if you could test the latest kernel and just verify the issue still exists and reattach an updated dmesg output after a failed suspend/resume cycle as you did previously. I'm reassigning to the kernel team. Also please note that we'll keep this open against the actively kernel but will be closed against 2.6.22. Thanks.