Open mgrouch opened 8 months ago
What hardware was attached? Neither I2c1 nor spi0 would normally be enabled and active.
No i2c or spi hardware is attached but kernel modules are enabled
So there should have been nothing accessing the I2C an SPI busses, unless some software is probing them. Any thoughts?
Roughly how long had the Pi 5 been up when this happened? Seconds, minutes or hours?
Software called Pypilot is probing them. https://github.com/pypilot/pypilot
However errors start after hours of probing and running without kernel errors.
So it looks there is some kind of kernel bug in drivers.
Thanks
It's very suspicious that both fail at the same time - either one has failed and taken down the other (perhaps by failing to acknowledge an interrupt etc.), or some common infrastructure has failed and taken both out.
I'll have a look at what pypilot is doing and try to do more of it.
Possibly caused by #5865.
Probably fixed by #6044.
Describe the bug
Steps to reproduce the behaviour
Was simply running and started happening after some time on raspberry pi5 rev 1
Device (s)
Other
System
Logs
Additional context
No response