# MP9250 9-axis sensor using I2C stops working after sometime

**URL:** <https://mangoh.discourse.group/t/mp9250-9-axis-sensor-using-i2c-stops-working-after-sometime/2092>\
**Category:** mangOH Red\
**Created:** [November 12, 2018, 3:37am UTC](https://mangoh.discourse.group/t/mp9250-9-axis-sensor-using-i2c-stops-working-after-sometime/2092 "2018-11-12T03:37:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![nick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/nick/32/1380_2.png) [@nick](https://mangoh.discourse.group/u/nick)\
**Post date:** [November 13, 2018, 6:09am UTC](https://mangoh.discourse.group/t/mp9250-9-axis-sensor-using-i2c-stops-working-after-sometime/2092/6 "2018-11-13T06:09:07Z")

</div>

Hey @epsragh,

Would it be possible to see the output from `dmesg | grep i2c`? We faced issues regarding the i2c data line getting stuck low (see [GPIO stops working after several hours](https://mangoh.discourse.group/t/gpio-stops-working-after-several-hours/1273/24?u=nick)) resulting in a “bus busy” error from the Qualcomm i2c driver in the kernel log. We never really found a conclusive answer either. In general, cutting down on i2c traffic seemed to do the trick (i.e no polling).

Also, which module are you using? We’ve been testing with a WP85 on release 15 firmware and a fork of Legato 18.04.0. I have yet to test release 16 of the WP85 firmware but I’m optimistic that it could improve i2c performance.

---

_[View the full topic](https://mangoh.discourse.group/t/mp9250-9-axis-sensor-using-i2c-stops-working-after-sometime/2092)._