U disk not mounted correctly on Android 5.1 with ES FileManager

ifzhao — Thu, 07 Sep 2017 01:21:44 GMT

hi all,

Here is an interesting issue. U disk is not mounted correctly if ES FileManager is opened.

This is a normal printing:

[ 501.859987] usb usb1: usb wakeup-resume
[ 501.863915] hub 1-0:1.0: hub_resume
[ 501.867649] hub 1-0:1.0: port 1: status 0101 change 0001
[ 501.976402] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000,rev= 0000,busy 0000
[ 501.985099] i=1
[ 501.986933] after test_busy_bit
[ 501.990093] after test wakeup bits
[ 501.993507] after test all bits
[ 501.996905] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
[ 502.156572] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[ 502.276464] usb 1-1: new high-speed USB device number 21 using ci_hdrc
[ 502.426733] hub_port_connect_change
[ 502.432979] usb 1-1: usb_enumerate_device_otg err=0
[ 502.438289] usb 1-1: usb_detect_interface_quirks 0
[ 502.443692] usb 1-1: read descriptor err =0
[ 502.448030] usb 1-1: udev 21, busnum 1, minor = 20
[ 502.452925] usb 1-1: New USB device found, idVendor=0781, idProduct=5567
[ 502.452936] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 502.452941] usb 1-1: Product: USB DISK
[ 502.452945] usb 1-1: Manufacturer: Sandisk Corporation
[ 502.452950] usb 1-1: SerialNumber: VC0470150728162171000103
[ 502.452987] device: '1-1': device_add
[ 502.454035] device: '1-1:1.0': device_add
[ 502.454858] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 502.455689] scsi8 : usb-storage 1-1:1.0
[ 502.455767] device: 'host8': device_add
[ 502.456861] device: 'host8': device_add
[ 502.458059] device: 'ep_81': device_add
[ 502.458142] device: 'ep_02': device_add
[ 502.458364] device: 'ep_00': device_add
[ 502.458442] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000,rev= 0000,busy 0000
[ 502.458451] i=1
[ 502.458453] after test_busy_bit
[ 502.458455] after test wakeup bits
[ 502.458457] continue
[ 503.791044] scsi 8:0:0:0: Direct-Access Sandisk USB Ultra 1100 PQ: 0 ANSI: 4
[ 503.799501] device: 'target8:0:0': device_add
[ 503.804249] device: '8:0:0:0': device_add
[ 503.808819] device: '8:0:0:0': device_add
[ 503.813238] device: '8:0:0:0': device_add
[ 503.818626] sd 8:0:0:0: [sda] 15730688 512-byte logical blocks: (8.05 GB/7.50 GiB)
[ 503.826958] sd 8:0:0:0: [sda] Write Protect is off
[ 503.832581] sd 8:0:0:0: [sda] No Caching mode page found
[ 503.837949] sd 8:0:0:0: [sda] Assuming drive cache: write through
[ 503.844067] device: '8:0': device_add
[ 503.848368] device: 'sda': device_add
[ 503.855454] sd 8:0:0:0: [sda] No Caching mode page found
[ 503.860822] sd 8:0:0:0: [sda] Assuming drive cache: write through
[ 503.868116] sda: sda1
[ 503.870531] device: 'sda1': device_add
[ 503.889240] sd 8:0:0:0: [sda] No Caching mode page found
[ 503.894976] sd 8:0:0:0: [sda] Assuming drive cache: write through
[ 503.902025] sd 8:0:0:0: [sda] Attached SCSI removable disk
[ 504.086279] device: '8:1-fuseblk': device_add
[ 504.126964] init: no such service 'fuse_udisk1'

This is defective one:

[ 870.092502] usb usb1: usb wakeup-resume
[ 870.096403] hub 1-0:1.0: hub_resume
[ 870.099943] hub 1-0:1.0: port 1: status 0101 change 0001
[ 870.208323] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000,rev= 0000,busy 0000
[ 870.215561] i=1
[ 870.217362] after test_busy_bit
[ 870.220511] after test wakeup bits
[ 870.223916] after test all bits
[ 870.227132] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
[ 870.386270] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[ 870.506259] usb 1-1: new full-speed USB device number 82 using ci_hdrc
[ 870.666328] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002,rev= 0000,busy 0000
[ 870.673566] i=1
[ 870.675322] after test_busy_bit
[ 870.678485] after test wakeup bits
[ 870.681893] after test all bits
[ 870.685103] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[ 870.846328] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[ 870.966256] usb 1-1: new full-speed USB device number 83 using ci_hdrc
[ 871.126328] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002,rev= 0000,busy 0000
[ 871.133560] i=1
[ 871.135317] after test_busy_bit
[ 871.138487] after test wakeup bits
[ 871.141894] after test all bits
[ 871.145110] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[ 871.306256] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[ 871.426292] usb 1-1: new full-speed USB device number 84 using ci_hdrc
[ 871.586340] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002,rev= 0000,busy 0000
[ 871.593574] i=1
[ 871.595352] after test_busy_bit
[ 871.598535] after test wakeup bits
[ 871.601962] after test all bits
[ 871.605194] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[ 871.766256] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[ 871.886335] usb 1-1: new high-speed USB device number 85 using ci_hdrc
[ 872.036779] hub_port_connect_change
[ 872.043860] usb 1-1: usb_enumerate_device_otg err=0
[ 872.049252] usb 1-1: usb_detect_interface_quirks 0
[ 872.054140] usb 1-1: read descriptor err =0
[ 872.058397] usb 1-1: udev 85, busnum 1, minor = 84
[ 872.063254] usb 1-1: New USB device found, idVendor=0781, idProduct=5567
[ 872.071546] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 872.078960] usb 1-1: Product: USB DISK
[ 872.082767] usb 1-1: Manufacturer: Sandisk Corporation
[ 872.088043] usb 1-1: SerialNumber: VC0470150728162171000103
[ 872.094128] device: '1-1': device_add
[ 872.096293] device: '1-1:1.0': device_add
[ 872.106490] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 872.116180] scsi36 : usb-storage 1-1:1.0
[ 872.121623] device: 'host36': device_add
[ 872.126427] device: 'host36': device_add
[ 872.131187] device: 'ep_81': device_add
[ 872.135199] device: 'ep_02': device_add
[ 872.143810] device: 'ep_00': device_add

Normal: U disk->USB device add-> USB Block device add

Defect: U disk->USB device add

It's weird, if I close ESFilemanager, then it continue to add USB Block device.

I don't think the AP could interact with kernel, and even to change the mount flow.

Could any one tell me why ? Thanks!

Re: U disk not mounted correctly on Android 5.1 with ES FileManager

b36401 — Fri, 08 Sep 2017 03:34:16 GMT

Please make sure that you have g_mass_storage module in your system.

Have a great day,
Victor

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: U disk not mounted correctly on Android 5.1 with ES FileManager

ifzhao — Fri, 08 Sep 2017 07:52:22 GMT

Of course I do have g_mass_storage. My problem happens quite often if I open ESFilemanager. It's likely ESFilemanager has invoked some kind of mechanism to access or even interrupt the USB mounting flow. But still until now, I have no idea why this happens.

topic U disk not mounted correctly on Android 5.1 with ES FileManager in i.MX Processors

U disk not mounted correctly on Android 5.1 with ES FileManager

Re: U disk not mounted correctly on Android 5.1 with ES FileManager

Re: U disk not mounted correctly on Android 5.1 with ES FileManager