Could you please verify this bug still exists in our latest kernel -> 2.6.35-22.32? We are about to rollout a newer kernel (see https://bugs.launchpad.net/bugs/641618), but I don't believe the fixes there address this.
Could you please verify this bug still exists in our latest kernel -> 2.6.35-22.32? We are about to rollout a newer kernel (see https:/ /bugs.launchpad .net/bugs/ 641618), but I don't believe the fixes there address this.