I2c floods syslog. Kernel 4.2.2

[maruprez]

Hi,

 

My Armbian Vanilla  for Cubieboard1 is working las 2 months...

 

Theres is an iissue with I2c, that I don't know how  to avoid or stop

 

 

Dmesg and syslog are flooded with this message

 

Feb  7 11:09:05 localhost kernel: [172015.158063] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:06 localhost kernel: [172015.688415] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:06 localhost kernel: [172016.158440] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:18 localhost kernel: [172027.837841] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:18 localhost kernel: [172028.087760] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:20 localhost kernel: [172029.458174] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:52 localhost kernel: [172062.127458] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:53 localhost kernel: [172062.787721] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:09:53 localhost kernel: [172063.117689] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:10:06 localhost kernel: [172075.877089] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:10:07 localhost kernel: [172076.827514] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:10:07 localhost kernel: [172077.117481] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
Feb  7 11:10:56 localhost kernel: [172125.626336] i2c i2c-0: master_xfer[0] W, addr=0x34, len=2
 

 

And as result it is very difficult to read any warning  message on log.

 

Is there any way to stop this?

 

My Cubieboard 1  works as file and print server.

uname -a
Linux xxxxxx 4.2.2-sunxi #3 SMP Wed Sep 30 21:20:20 CEST 2015 armv7l GNU/Linux

 

Thanks

 

 

 

[tkaiser]

If you don't want to filter /var/log/messages why not discarding the I2C messages (they originate from the AXP209 PMU in your case)? See http://www.rsyslog.com/discarding-unwanted-messages/  for example.

 

Something like 

:msg, contains, "i2c-0: master_xfer[0] W, addr=0x34, len=2" ~

should work.

[zador.blood.stained]

This was an issue with kernel 4.2.2 (i2c debug messages were enabled in configuration), I would strongly suggest to make a backup and upgrade to a latest mainline kernel.