From b74d19649105a412e84a5419e63f40020127218c Mon Sep 17 00:00:00 2001 From: John Stultz Date: Sun, 3 Nov 2019 12:11:01 +0200 Subject: [PATCH] msm8226-common: Disable nonblocking_ffs to avoid recent crashes with adbd Recent changes to adbd have enabled nonblocking_ffs by default. These have seeminly uncovered some bad memory corruption in the kernel ffs gadget driver on every kernel I've tried so far. Unfortunately I've not been able to diagnose what is going wrong, so for now, lets disable the nonblocking_ffs. We still need to root cause the issue as its a problem even with the mainline kernel on HiKey, so its likely a generic kernel issue. Change-Id: I68a94f8f26b65ab383c37274e4f631227a3c7d5f Signed-off-by: John Stultz --- recovery/root/init.recovery.qcom.rc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recovery/root/init.recovery.qcom.rc b/recovery/root/init.recovery.qcom.rc index a404173..c14c612 100644 --- a/recovery/root/init.recovery.qcom.rc +++ b/recovery/root/init.recovery.qcom.rc @@ -1,2 +1,4 @@ on fs setprop sys.usb.ffs.aio_compat 1 + setprop persist.adb.nonblocking_ffs 0 + setprop ro.adb.nonblocking_ffs 0