From the looks of things, when v3.13.11-ckt14 was applied which also contains the fix for the original issue, somehow the fix got applied reversed and undid the fix!
From the looks of things, when v3.13.11-ckt14 was applied which also contains the fix for the original issue, somehow the fix got applied reversed and undid the fix!