From 802f5e740f7dba89b212816aed7b415d8b7692fa Mon Sep 17 00:00:00 2001 From: John Stultz Date: Sun, 3 Nov 2019 12:11:57 +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: I81ac10edf5ddf9040852a4cb1f0f07c4ca16ef67 --- 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 898069a..fad0581 100644 --- a/rootdir/etc/init.qcom.usb.rc +++ b/rootdir/etc/init.qcom.usb.rc @@ -44,6 +44,8 @@ on fs write /sys/class/android_usb/android0/f_ffs/aliases adb setprop sys.usb.ffs.aio_compat 1 + setprop persist.adb.nonblocking_ffs 0 + setprop ro.adb.nonblocking_ffs 0 # Following are the parameters required for usb functionality. They provide configurable options like # product_id/vendor id and allows specifying required functions: