Perhaps if someone has time they could compile the latest stock kernel from kernel.org and see if this bug is still present? Then at least we could narrow it down to either something which has been fixed since 2.6.15 or an ubuntu specific patch.
Just a thought.
Robert
Perhaps if someone has time they could compile the latest stock kernel from kernel.org and see if this bug is still present? Then at least we could narrow it down to either something which has been fixed since 2.6.15 or an ubuntu specific patch.
Just a thought.
Robert