according to several user reports, this issue was fixed in kernel 2.6.27-8. marking as such. thanks go out to everyone for helping triage and confirm the fix of this bug.
according to several user reports, this issue was fixed in kernel 2.6.27-8. marking as such. thanks go out to everyone for helping triage and confirm the fix of this bug.