I am running a 64-bit PiOS Bookworm on Raspberry Pi 5 and am eventually seeing in all consoles:
after my robot drives around a bit. The robot commands flow from the Pi5 to the robot control board via SPI.
The only fix is to reboot by jerking the power out from under the system.
It seems like I can (eventually) cause the problem reliably.
I have tried two different 32GB Sandisk Ultra A1 Class 10 U1 micro SDcards.
The file system always passes fsck, (tune2fs initiated at boot)
The general guidance is this error means the system disk is about to fail.
I have confirmed that the robot can drive the Pi5 at 100% four core banging with no voltage or temperature throttling, although in these test cases the CPU is very lightly loaded so I am not suspecting a power limitation.
Any tips on how to debug this ?
Code:
$ ls-bash: /usr/bin/ls: Input/output errorThe only fix is to reboot by jerking the power out from under the system.
It seems like I can (eventually) cause the problem reliably.
I have tried two different 32GB Sandisk Ultra A1 Class 10 U1 micro SDcards.
The file system always passes fsck, (tune2fs initiated at boot)
The general guidance is this error means the system disk is about to fail.
I have confirmed that the robot can drive the Pi5 at 100% four core banging with no voltage or temperature throttling, although in these test cases the CPU is very lightly loaded so I am not suspecting a power limitation.
Any tips on how to debug this ?
Statistics: Posted by amcdonley — Thu Mar 28, 2024 2:57 am
