I2c-msm-v2 error in log file

mangOH Yellow
1

Hi,
I was checking log file from my mangOH Yellow. I found error messages related to i2c-msm-v2:

root@swi-mdm9x28-wp:~# logread | grep i2c-msm-v2
Jan 1 09:42:33 swi-mdm9x28-wp user.info kernel: [ 0.370188] i2c-msm-v2 78b8000.i2c: probing driver i2c-msm-v2
Jan 1 09:42:33 swi-mdm9x28-wp user.info kernel: [ 0.370335] i2c-msm-v2 78b8000.i2c: msm_bus_scale_register_client(mstr-id:86):0 (not a problem)
Jan 1 09:42:33 swi-mdm9x28-wp user.err kernel: [ 0.372380] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x091343c8 OPER:0x00000090
Jan 1 09:42:33 swi-mdm9x28-wp user.err kernel: [ 0.372440] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x091343c8 OPER:0x00000090
Jan 1 09:42:33 swi-mdm9x28-wp user.err kernel: [ 0.374291] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Jan 1 09:42:33 swi-mdm9x28-wp user.err kernel: [ 0.374337] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Oct 27 16:30:21 swi-mdm9x28-wp user.err kernel: [ 15.648342] i2c-msm-v2 78b8000.i2c: msm_bus_scale_register_client(mstr-id:86):0xc (ok)
Oct 27 16:30:21 swi-mdm9x28-wp user.err kernel: [ 15.712562] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Oct 27 16:30:21 swi-mdm9x28-wp user.err kernel: [ 15.727764] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Oct 27 16:30:42 swi-mdm9x28-wp user.err kernel: [ 36.573989] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv_addr:0x55 MSTR_STS:0x001363c8 OPER:0x00000010
Oct 27 16:30:42 swi-mdm9x28-wp user.err kernel: [ 36.588835] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv_addr:0x55 MSTR_STS:0x001363c8 OPER:0x00000010
Oct 27 16:30:42 swi-mdm9x28-wp user.err kernel: [ 36.611591] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:18) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Oct 27 16:30:42 swi-mdm9x28-wp user.err kernel: [ 36.626545] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:18) mode:FIFO slv_addr:0x3a MSTR_STS:0x001363c8 OPER:0x00000090
Oct 27 16:31:05 swi-mdm9x28-wp user.err kernel: [ 60.028942] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv_addr:0x55 MSTR_STS:0x001363c8 OPER:0x00000010
Oct 27 16:31:05 swi-mdm9x28-wp user.err kernel: [ 60.043818] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv_addr:0x55 MSTR_STS:0x001363c8 OPER:0x00000010

Is it something important? The answer seems to be no, as the board sends/receives data to/from cloud side without visible trouble :slightly_smiling_face: But just being curious: is there a way to make this error disappear?

2

Hi,

This is not important as the device being probed is not awake at that moment. We will ask module team if it can be taken out but wouldn’t happen anytime soon.

Regards,
Ashish

3

Thanks for your answer, Ashish. Just being more curious :slightly_smiling_face: : what’s the device being probed?

Regards,
Pascal

PS: I really enjoyed the SWIS two days!

4

Thanks for coming to the summit.
Would be great to hear in details about your experience as well as the mangoh yellow and octave

5

Address is 0x3a which is the built in microcontroller on WP77 module

1 Like
6

Yes, I’ll try to write a few lines about my experiments over the coming period.

7

I just spent some time playing with a first edge action. I described my experiments here: https://gitlab.systev.com/pascalb/mangohyellow/wikis/home.

8

How can I stop these messages appearing at the console port. It is almost unusable because of them. I have tried various forms of the “log” command without success. What is the correct form of “trace keyword” mentioned in “log --help”?

Edit: it appears the console messages are coming direct from the kernel not the logging system.