On Wed, Feb 17, 2021 at 11:07:17AM -0800, Ronald Tschalär wrote: > For some reason, when the system is under heavy CPU load, the read > following the write sometimes occurs unusually quickly, resulting in > the read data not being quite ready and hence a bad packet getting read. > Adding another delay after reading the status message appears to fix > this. > > Signed-off-by: Ronald Tschalär <ronald@xxxxxxxxxxxxx> Applied, thank you. -- Dmitry
