I also have this error, I think it comes every time I boot, first time I see it in the log is October 11 but that was also the last time I reflashed it, it may have happened earlier also, I don’t know.
Since it is the kernel failing to do something, I would first suspect a kernel update.
If you are sure there was a time when that error did not occur, then it might be worthwhile to try previous kernel versions to see if the error appears for a specific kernel version.
before when I connected my usb-c hub, it will light up, so the librem5 was powering it. This does not happen anymore.
I left it charging overnight and when I turned it on in the morning, there was one process using one core 100% (irq/79+) and a bunch of: tps6598x 0-003f: tps6598x_interrupt: failed toread events in the kernel log.
I have to investigate on how to roll back packages. I thought a simple apt install package=version would work but old packages are not available.
Finally I didn’t have to compile the kernel image because Purism is saving the linux-image-*.deb for each tagged version. Confusingly (for me) the are packed in something called “artifacts”.
Anyway, I rolled back the kernel first to 5.13.14pureos1+gitlabci1 and also to 5.13.16pureos1+gitlabci1. None of them helped.
As now it is easy to roll back versions I also tried with my first suspect (librem5-devkit-base) but that didn’t help either.
For now, the only way to charge the phone at a reasonable speed is to boot with it already plugged to the charger. Otherwise, although the red LED is on, it will barely charge.
I have just sent you 2 different dmesg. Hopefully there is something helpful there.
The following output is what get when booting uplugged:
purism@pureos:~$ sudo cat /sys/kernel/debug/tps6598x/0-003f/customer_use
cat: /sys/kernel/debug/tps6598x/0-003f/customer_use: No such file or directory
In fact, there is no /sys/kernel/debug/tps6598x.
If the phone is plugged from the beginning then I get 0x4c35445000000200. I flashed that version when I was on amber to fix charging with my usb-c hub (it worked great until this issue appeared).