Unfortunately, the patch doesn't solve this problem, at least not by itself.
Are there any other options besides bisecting 2.6.30 to 2.6.31? I don't mind doing a bisect, but it's likely to take more time than I have available in the near future. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
