Comment 19 for bug 1475166

 1) I would definitely recommend booting up/checking the logs multiple times on every leg of the test to ensure that it gets a consistent result.
2) I don't understand how this would have happened. It does occur to me that if we're dealing with possible IO corruption there could be other issues too, I'd suggest:
If you can reproduce without having the OS or Kernel code on the Avago controller that would be the best option. (like I described in C#17)
If not, reboot back to the stable v3.16 kernel before doing any git or build commands.