On 3/25/25 16:18, neil.armstr...@linaro.org wrote:
On 25/03/2025 14:49, Caleb Connolly wrote:
On 3/25/25 14:33, Neil Armstrong wrote:
On 25/03/2025 14:02, Caleb Connolly wrote:
We don't have a mechanism to safely shutdown block devices prior to a
baord reset or driver removal. Prevent dat
On 25/03/2025 14:49, Caleb Connolly wrote:
On 3/25/25 14:33, Neil Armstrong wrote:
On 25/03/2025 14:02, Caleb Connolly wrote:
We don't have a mechanism to safely shutdown block devices prior to a
baord reset or driver removal. Prevent data loss by synchronizing the
SCSI cache after every writ
On 3/25/25 14:33, Neil Armstrong wrote:
On 25/03/2025 14:02, Caleb Connolly wrote:
We don't have a mechanism to safely shutdown block devices prior to a
baord reset or driver removal. Prevent data loss by synchronizing the
SCSI cache after every write.
In particular this solves the issue of
On 25/03/2025 14:02, Caleb Connolly wrote:
We don't have a mechanism to safely shutdown block devices prior to a
baord reset or driver removal. Prevent data loss by synchronizing the
SCSI cache after every write.
In particular this solves the issue of capsule updates looping on some
devices beca
We don't have a mechanism to safely shutdown block devices prior to a
baord reset or driver removal. Prevent data loss by synchronizing the
SCSI cache after every write.
In particular this solves the issue of capsule updates looping on some
devices because the board resets immediately after deleti
5 matches
Mail list logo
