From ac522297f7f684c7fabc5b72bed0829c668cadbe Mon Sep 17 00:00:00 2001 From: John Stultz Date: Thu, 5 Mar 2020 22:59:20 +0100 Subject: [PATCH] msm8976-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. Signed-off-by: John Stultz --- rootdir/etc/init.qcom.usb.rc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rootdir/etc/init.qcom.usb.rc b/rootdir/etc/init.qcom.usb.rc index 5034166..34727dc 100644 --- a/rootdir/etc/init.qcom.usb.rc +++ b/rootdir/etc/init.qcom.usb.rc @@ -36,6 +36,8 @@ on boot write /sys/class/android_usb/android0/f_rndis/manufacturer ${ro.product.manufacturer} setprop persist.sys.usb.config.extra none setprop sys.usb.ffs.aio_compat 1 + setprop persist.adb.nonblocking_ffs 0 + setprop ro.adb.nonblocking_ffs 0 on charger setprop sys.usb.config mtp