Comment 6 for bug 1437357

I am investigating!

I have a few thoughts:

1. This exception probably should be caught in production (or maybe Mir should just be logging a warning here), this at least
would lead to just quirky behavior with high number of touches (it probably works pretty well...).
2. We should determine whether the kernel driver is outputting a valid stream.

In the case the kernel is outputting an invalid event stream 1 may be the best solution we can get for now. It may be possible to write an event stream validater/transformer (and actually there is more validation in devel than release) but I don't think its possible to get perfect.

If the kernel is outputting a valid event stream then there must be some problem in the Mir InputReader