During log analysis, we found a potential glitch in the MMC5883 driver. This needs further investigation: