The Raring kernel has been rebased to upstream 3.8.4 in the 3.8.0-14.24 kernel. Can folks affected by this bug in Raring upgrade to the latest 3,8 kernel and confirm it has been fixed?
The Raring kernel has been rebased to upstream 3.8.4 in the 3.8.0-14.24 kernel. Can folks affected by this bug in Raring upgrade to the latest 3,8 kernel and confirm it has been fixed?