We really appreciate all the information and testing you've provided already. However, according to SRU Policy we need to verify this issue is first resolved in the current development release before a backport for Hardy can be considered - https://wiki.ubuntu.com/StableReleaseUpdates . If this is not resolved for Intrepid a fix will need to be applied to Intrepid first and then backported to Hardy. Or, it could be that this is already resolved for Intrepid which can then help narrow down the possible patch to backport for Hardy.
There has also been some discussion of providing a newer kernel for Hardy so any feedback you can give us will help with making that assessment.
Also I'm curious if rather than rebooting in order to reconnect, what if you just unload and reload the module? Thanks.
Hi Stuart,
We really appreciate all the information and testing you've provided already. However, according to SRU Policy we need to verify this issue is first resolved in the current development release before a backport for Hardy can be considered - https:/ /wiki.ubuntu. com/StableRelea seUpdates . If this is not resolved for Intrepid a fix will need to be applied to Intrepid first and then backported to Hardy. Or, it could be that this is already resolved for Intrepid which can then help narrow down the possible patch to backport for Hardy.
There has also been some discussion of providing a newer kernel for Hardy so any feedback you can give us will help with making that assessment.
Also I'm curious if rather than rebooting in order to reconnect, what if you just unload and reload the module? Thanks.