@kaihengfeng So v5.7 was fine and after many reboots it has been found that this commit below introduced the issue. Do I also need to find when the issue was resolved ? (between v5.8-rc1 and v5.9.10) or is this information enough ? 54b2fcee1db041a83b52b51752dade6090cf952f is the first bad commit commit 54b2fcee1db041a83b52b51752dade6090cf952f Author: Keith Busch