Is this happening on a sensor that is making heavy use of resets? I have looked at the code and this warning can happen when specific timing of events occur within the driver. I think they can be safely ignored, but, if possible, I would like a little more information on when they are happening.
