How will a log help you when you can read my description of the problem?
I think it's pretty serious all in itself when one would do this for the community to have such a bug fixed by using my time to write such detaled descriptions and testing all firmware version etc. It's called gathering empirical data - log or no log.
All you will see is in a log is the RPM latched to crankingrpm/2 and the error counter stepping up when the error occurs - you won't learn s*** from it!
So you my friend friend should not get sucked into the trend of feeling the need to see a d*** log for every issue out there when words are plenty full, and sometimes better, for describing the issue!
Oh, and by the way, you did not attached an MSQ with your log file, so i have no "proof" that you had noise filtering enabled on the crank channel. Talking about seriousness...
I gets pretty tedious when you don't get believed by people in a community when all you try to do is help out by doing new discoveries that can lead to improvement of the source code.
I'm done with this. I have gotten the response the community needed through facebook; the error is scheduled to be fixed.
Have a nice day