LPC errors flooding the kernel log [FIXED]

MNT Reform
1

One of my USB port isn’t functioning properly anymore. Just in case, I upgraded the system and now this fills up in the kernel log at high speed:

root@reform:~# journalctl -kf
Mar 27 17:50:34 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: c/0 checksum mismatch: af expected, 0 received.
Mar 27 17:50:34 reform kernel: power_supply BAT0: driver failed to report `charge_now' property: -16
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 7b expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 66 expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 62 expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 62 expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 65 expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 66 expected, 0 received.
Mar 27 17:50:34 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 78 expected, 0 received.
Mar 27 17:50:38 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 66 expected, 0 received.
Mar 27 17:50:38 reform kernel: power_supply_format_property: 7 callbacks suppressed
Mar 27 17:50:38 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 6c expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `current_now' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 64 expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 60 expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `voltage_now' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 62 expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: c/0 checksum mismatch: af expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `charge_full' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 64 expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: c/0 checksum mismatch: af expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `charge_full_design' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: q/0 checksum mismatch: 6c expected, 0 received.
Mar 27 17:50:39 reform kernel: power_supply BAT0: driver failed to report `status' property: -16
Mar 27 17:50:39 reform kernel: reform2_lpc spi1.0: lpc_command: c/0 checksum mismatch: af expected, 0 received.

Any idea?

2

Yes, this is the recent change in reform2_lpc kernel module resulting from this commit:

@minute can probably comment on this but maybe is a bit busy right now (at least they were not replying to my pings on IRC regarding this change). If they are busy right now, I’m just going to revert that commit and do a hot-fix upload soon.

3

I’m just going to revert that commit and do a hot-fix upload soon.

Thanks!

I’m a bit confused though: I quickly perused that diff and it seems to check the API version (by date apparently) before trying to communicate with the right flavor. Shouldn’t it stick to - what I presume my machine uses - the old API? Why is it apparently trying v3 on my machine?

4

After reading Battery indicator after update && upgrade and shutdown I have decided to not wait for minute and take the initiative and revert the change in question. The package with the apiv3 change reverted should be in the MNT Debian repositories in 45 minutes. Sorry for the mess.

1 Like
5

Seems fixed now. Thanks!