dmesg flooded w/ errors (mostly i2c)

OS: Klipper Kernel 5.16 07/12/23 image
Device: CB1 in BTT Pad7

I haven't seen this posted else where, but I've noticed a TON of errors in dmesg while trouble shooting other issues.

The biggest error I found and continues from boot onward is the following

`i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0`

some other errors in dmesg Ive noticed AT BOOT

```
sun50i-h616-pinctrl 300b000.pinctrl: pin PH0 already requested by 5000000.serial; cannot claim for soc:pwm3@0300a000
sun50i-h616-pinctrl 300b000.pinctrl: pin-224 (soc:pwm3@0300a000) status -22
sun50i-h616-pinctrl 300b000.pinctrl: could not request pin 224 (PH0) from group PH0 on device 300b000.pinctrl
platform soc:pwm3@0300a000: Error applying setting, reverse things back
platform soc:pwm3@0300a000: pinctrl_select_state(default) failed!
```

and a few
`sunxi-hdmi soc:hdmi-audio@1: snd_soc_register_card failed`

Not sure if these are of any relevance but the i2c error makes it extremely hard to troubleshoot other problems when using dmesg

Edit: These persist regardless of settings in BoardEnv.txt and system.cfg

Review BoardEnv.txt and system.cfg, then reproduce the boot-time messages and capture dmesg on the CB1 running the Klipper Kernel 5.16 image. Trace the I2C lock and pinctrl/PWM and HDMI-audio errors to their reported devices. Done means the messages are explained and a concrete configuration or image change is identified.

Written by the indexing model from the issue text.