Hi Wolfram and Andrew, On Thu, Dec 7, 2017 at 4:19 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: > >> > I attach a patch of the changes to the i2c driver showing my debug in >> > this driver. >> > As I said I am happy to send more verbose bug output - I have about 36 >> > odd runs with 9 occurences of the bug. >> > Once it happen twice in the one run >> > >> > I include the crashing line from the runs where the bug occured (I >> > added more diagnostics as the runs progressed): >> >> I'll check with out HW team as well and check your flow to >> see if we can reproduce it; will also check if the existing errata >> has larger scope. >> I'll let you know if we require further assistance with debug >> next week. > > Any news here? Sorry for the delay. I've checked the known errata and confirmed that it wont affect this use case. And we haven't been able to hit this issue on our HW (with eeprom slave devices). I will add my colleague looking into this further to debug. Regards, Harini
