Comment 159 for bug 1470250

I tested 3.13.0-34 for 24 hours and it did not exhibit the bug. This would indicate the bug was introduce between -34 and -35. There are only three commits between these two versions:

c8c38b3 Drivers: hv: vmbus: Fix a bug in the channel callback dispatch code
7af024a hv: use correct order when freeing monitor_pages
6ad4874 Drivers: hv: balloon: Ensure pressure reports are posted regularly

None are storage specific and stick out as the cause. It could have possible been caused by either of the connection commits. I think the only way to be sure is to bisect between -34 and -35 specifically against the drivers/hv directory. This would only require two bisect tests, then a final test with the suspect commit reverted. I'll do this next and post the results.