I've flashed my Intel Edison (with breakout board) with the latest Yocto release grabbed from Downloads for Intel® Edison Module | IoT | Intel® Software but I see the following error in the serial console as soon as the board starts (the error is non-blocking, the board reaches the login prompt):

Are you having the same issue with previous images? I would like to know if this hardware or software related, so if you could load a previous image onto your Edison and try again I would appreciate it.It would also be a good idea to try with I2C6 and see if the Edison crashes too, have you tried that?

I receive the exact same error on the previous version. Additionally, if I run i2cdetect -y -r 6 the board doesn't crashes but I don't see any device connected after I try to plug-in a sensor (the sensor itself is working without problems on other boards).

At this point I'm starting to believe that I'm facing an hardware problem.

Thank you for your answers.I’ve been running some tests myself and haven’t been able to reproduce your issue. So that makes me think that this is hardware related, as you also mentioned. Right now, just to discard any other issue, I would like to know how you’re powering the Breakout board, could you please show/explaining us your configuration? Do you have something connected to the board when booting or just wait for the board to end the booting process and then connect the sensor?I would like you to try changing USB cables and computer ports in case you’re connecting it this way.

I've madte my tests without anything connected to the board, just the power adapter and the USB cable for the serial connection. I plugged in the sensor only after the boot-up phase. Moreover, I have used the same USB cable and power adapter for different Intel Edison boards without any problems.

Thank you very much for the information.Please go ahead and open a ticket using this link https://customercare.intel.com/?lang=en-US, explain in the Description field of the ticket your issue and paste the link to this thread, this seems to be a warranty issue.