Comment 13 for bug 1554635

So, it seems logging the problem and not throwing is an acceptable solution, although IMO, it merits further investigation as to why the driver is generating this error during certain scenarios. Will propose attached branch to lp:mir, and its looking like it'll ride along in 0.20.3 mir release.