Anyone else have a problem with USB host mode and copying big files?
If so, can we fix this?
I have tried formatting my drive in FAT32,NTFS, and ext2. But the result is always the same, the drive dies if I copy a file bigger than 30 or 40 MB. I have tried stock, Faux123, and francoKernel as well.
The drive doesn't die at a specific MB each time, but it is generally around 30 MB but sometimes makes it to 80 or even 140 MB one time. I am trying to off-load some 700MB movies.
Here is the kernel message error:
<6>[ 1920.842529] max17040 4-0036: online = 1 vcell = 3547500 soc = 22 status = 3 health = 1 temp = 370 charger status = 0
<3>[ 1926.574005] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.594299] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.649810] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1927.740753] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
<6>[ 1927.773895] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
<6>[ 1927.938781] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
<3>[ 1968.389251] L3 CUSTOM SRESP error with SOURCEMM2 info=0x84
<4>[ 1968.389434] ------------[ cut here ]------------
<4>[ 1968.389739] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 l3_interrupt_handler+0x31c/0x360()
<4>[ 1968.390045] L3 custom sresp error
<4>[ 1968.390197] Modules linked in:
<4>[ 1968.390686] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1968.390991] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 1968.391326] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0074898>] (l3_interrupt_handler+0x31c/0x360)
<4>[ 1968.391632] [<c0074898>] (l3_interrupt_handler+0x31c/0x360) from [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178)
<4>[ 1968.391967] [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178) from [<c00d4760>] (handle_irq_event+0x3c/0x5c)
<4>[ 1968.392150] [<c00d4760>] (handle_irq_event+0x3c/0x5c) from [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164)
<4>[ 1968.392456] [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164) from [<c00d3f50>] (generic_handle_irq+0x2c/0x40)
<4>[ 1968.392791] [<c00d3f50>] (generic_handle_irq+0x2c/0x40) from [<c004904c>] (asm_do_IRQ+0x4c/0xac)
<4>[ 1968.393096] [<c004904c>] (asm_do_IRQ+0x4c/0xac) from [<c004eb08>] (__irq_svc+0x48/0xe4)
<4>[ 1968.393402] Exception stack(0xc0799f28 to 0xc0799f70)
<4>[ 1968.393554] 9f20: c0799f70 3b9aca00 4c534d85 000001ca 4c4bda2c 000001ca
<4>[ 1968.393859] 9f40: 000003ff c1192210 8000406a 412fc09a 00000000 00000000 00000000 c0799f70
<4>[ 1968.394042] 9f60: c007c690 c0068380 00000013 ffffffff
<4>[ 1968.394348] [<c004eb08>] (__irq_svc+0x48/0xe4) from [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4)
<4>[ 1968.394683] [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4) from [<c03af838>] (cpuidle_idle_call+0x94/0x118)
<4>[ 1968.394989] [<c03af838>] (cpuidle_idle_call+0x94/0x118) from [<c0050538>] (cpu_idle+0xbc/0xfc)
<4>[ 1968.395172] [<c0050538>] (cpu_idle+0xbc/0xfc) from [<c00088ac>] (start_kernel+0x298/0x2e8)
<4>[ 1968.395477] [<c00088ac>] (start_kernel+0x298/0x2e8) from [<80008040>] (0x80008040)
<4>[ 1968.395782] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 1968.396087] ---[ end trace 33de6ebe35ad56b6 ]---
<6>[ 1970.874023] max17040 4-0036: online = 1 vcell = 3532500 soc = 22 status = 3 health = 1 temp = 380 charger status = 0
<6>[ 1993.138793] usb 1-1: reset high speed USB device number 2 using musb-hdrc
<6>[ 2000.347503] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<6>[ 2000.347717] usb 1-1: USB disconnect, device number 2
<4>[ 2000.350708] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2000.351989] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2001.361236] max17040 4-0036: online = 1 vcell = 3585000 soc = 21 status = 2 health = 1 temp = 380 charger status = 0
<6>[ 2003.287322] sd 0:0:0:0: Device offlined - not ready after error recovery
<6>[ 2003.287597] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287628] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287658] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.287689] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
<3>[ 2003.287719] end_request: I/O error, dev sda, sector 63
<3>[ 2003.287750] Buffer I/O error on device sda1, logical block 0
<4>[ 2003.287780] lost page write due to I/O error on sda1
<6>[ 2003.289154] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.289459] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 21 e7 00 00 08 00
<3>[ 2003.291625] end_request: I/O error, dev sda, sector 8679
<3>[ 2003.291778] Buffer I/O error on device sda1, logical block 1077
<4>[ 2003.292114] EXT4-fs warning (device sda1): ext4_end_bio:258: I/O error writing to inode 13 (offset 217088 size 4096 starting block 1085)
<3>[ 2003.297576] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.297851] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.299560] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.299743] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.300415] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.300720] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301116] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.301391] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301727] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.302032] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.302398] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.302703] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.303802] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.304168] EXT4-fs error (device sda1): ext4_free_branches:4377: inode #13: block 536: comm libestool.so: Read failure
<3>[ 2003.305358] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.305755] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.306365] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.306518] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.336242] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.336364] EXT4-fs error (device sda1): ext4_find_entry:934: inode #2: comm libestool.so: reading directory lblock 0
<3>[ 2003.411834] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.412017] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm ngs.android.pop: unable to read itable block
<2>[ 2003.412414] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.412567] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2008.311859] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.312194] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm bdi-default: unable to read itable block
<3>[ 2008.313110] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.313415] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm bdi-default: unable to read itable block
<6>[ 2025.582702] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2026.233337] usb 1-1: new high speed USB device number 3 using musb-hdrc
<3>[ 2026.388244] usb 1-1: device v090c p6200 is not supported
<6>[ 2026.388427] usb 1-1: New USB device found, idVendor=090c, idProduct=6200
<6>[ 2026.388763] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2026.389068] usb 1-1: Product: Generic USB2.0 card
<6>[ 2026.389221] usb 1-1: Manufacturer: Silicon Motion, Inc.
<6>[ 2026.389373] usb 1-1: SerialNumber: 12345678901234567890
<6>[ 2026.392089] scsi1 : usb-storage 1-1:1.0
<6>[ 2030.177124] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2030.180053] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2030.181335] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2031.197509] max17040 4-0036: online = 1 vcell = 3600000 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<6>[ 2034.948303] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2035.182495] usb 1-1: USB disconnect, device number 3
<6>[ 2045.606109] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2045.609100] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2045.610321] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2046.627288] max17040 4-0036: online = 1 vcell = 3602500 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<4>[ 2048.832824] ------------[ cut here ]------------
<4>[ 2048.832916] WARNING: at drivers/usb/musb/musb_host.c:125 musb_h_tx_flush_fifo+0x78/0x84()
<4>[ 2048.833068] Could not flush host TX2 fifo: csr: 2003
<4>[ 2048.833160] Modules linked in:
<4>[ 2048.833404] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 2048.833526] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 2048.833679] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84)
<4>[ 2048.833862] [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84) from [<c0367724>] (musb_cleanup_urb+0xb0/0xd4)
<4>[ 2048.834014] [<c0367724>] (musb_cleanup_urb+0xb0/0xd4) from [<c0367990>] (musb_urb_dequeue+0xfc/0x13c)
<4>[ 2048.834167] [<c0367990>] (musb_urb_dequeue+0xfc/0x13c) from [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac)
<4>[ 2048.834350] [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac) from [<c035d938>] (usb_stor_stop_transport+0x48/0x60)
<4>[ 2048.834442] [<c035d938>] (usb_stor_stop_transport+0x48/0x60) from [<c035c36c>] (command_abort+0x80/0x84)
<4>[ 2048.834564] [<c035c36c>] (command_abort+0x80/0x84) from [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c)
<4>[ 2048.834716] [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c) from [<c00b227c>] (kthread+0x80/0x88)
<4>[ 2048.834899] [<c00b227c>] (kthread+0x80/0x88) from [<c0050148>] (kernel_thread_exit+0x0/0x8)
<4>[ 2048.835052] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 2048.835144] ---[ end trace 33de6ebe35ad56b7 ]---
<6>[ 2048.837768] scsi 1:0:0:0: Device offlined - not ready after error recovery
I found a thread on TI site for the OMAP4460 that discusses an error like mine but the signature is not the same, seems there they were having a problem with the the TCP/IP stack becoming corrupted because the processor was allocating memory too fast. Something like that is happening here. All I really know is it has to do with the handling of the L3 cache.
I think this may have to do with the cpu trying to idle when it should not.
What kind of drive are you using? If its a portable usb hard drive then this could be a power issue.
It's not a portable HD, just usb sd card reader.
With further investigation I have found that the problem might stem from the x-loader being mismatched to the kernel, which is part of the bootloader.
I tried different bootloaders, but none made a difference.
Finally, I tried a different USB OTG cable, a slightly more expensive one, and it worked.
I have had my refurbished HTC Vision for about three weeks and it hadn't had any problems. Then yesterday, I rebooted it and now the sdcard doesn't work. Not just that it doesn't mount, rather there is not even a /dev/block/mmcblk1 device.
Here is what I tried:
* Boot into ClockworkMod, and run adb shell. Still no /dev/block/mmcblk1.
* Boot into fastboot and run "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig".
* Per some random instructions on the net, I held vol-up and power, then pulled the battery after the phone vibrated. Then I held vol-up, vol-down, power and did the same. Then the fastboot commands again.
* Bent the sdcard port's pins out a bit with tweezers.
* SDcard works in computer (Linux).
* Tried another card that has nothing but a vfat partition.
Nothing works! There are some errors in dmesg:
Code:
$ dmesg |grep mmc
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT09LR200858 androidboot.bootloader=0.76.2000 no_console_suspend=1 console=null
<6>[ 2.532989] vision: vision_init_mmc
<3>[ 3.267822] mmc0: No card detect facilities available
<6>[ 3.268341] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 3.268615] mmc0: Platform slot type: MMC
<6>[ 3.268737] mmc0: 4 bit data mode disabled
<6>[ 3.269012] mmc0: 8 bit data mode enabled
<6>[ 3.269134] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.269378] mmc0: Slot eject status = 0
<6>[ 3.269531] mmc0: Power save feature enable = 1
<6>[ 3.269653] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2b774000
<6>[ 3.269927] mmc0: DM cmd busaddr 0x2b774000, cmdptr busaddr 0x2b774300
<6>[ 3.270751] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 3.270996] mmc1: Platform slot type: N/A
<6>[ 3.271148] mmc1: 4 bit data mode enabled
<6>[ 3.271392] mmc1: 8 bit data mode disabled
<6>[ 3.271514] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.271789] mmc1: Slot eject status = 1
<6>[ 3.271911] mmc1: Power save feature enable = 1
<6>[ 3.272064] mmc1: DM non-cached buffer at ffa0d000, dma_addr 0x2b777000
<6>[ 3.272308] mmc1: DM cmd busaddr 0x2b777000, cmdptr busaddr 0x2b777300
<6>[ 3.273468] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 3.273712] mmc2: Platform slot type: SD
<6>[ 3.273834] mmc2: 4 bit data mode enabled
<6>[ 3.273986] mmc2: 8 bit data mode disabled
<6>[ 3.274230] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.274353] mmc2: Slot eject status = 0
<6>[ 3.274658] mmc2: Power save feature enable = 1
<6>[ 3.274810] mmc2: DM non-cached buffer at ffa0e000, dma_addr 0x2b778000
<6>[ 3.275054] mmc2: DM cmd busaddr 0x2b778000, cmdptr busaddr 0x2b778300
<6>[ 3.275207] mmc2: Polling status mode enabled
<6>[ 3.425598] mmc0: new high speed MMC card at address 0001
<6>[ 3.427093] mmcblk0: mmc0:0001 SEM04G 2.09 GiB
<6>[ 3.428100] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<6>[ 3.569030] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 3.703063] mmc2: high speed mode max_dtr = 50000000
<4>[ 3.703491] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.703643] mmc2: new high speed SDHC card at address 0001
<6>[ 3.704498] mmcblk1: mmc2:0001 00000 7.41 GiB
<6>[ 3.705291] mmcblk1: p1
<4>[ 4.648254] EXT4-fs (mmcblk0p26): warning: maximal mount count reached, running e2fsck is recommended
<7>[ 4.651062] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24790
<7>[ 4.655670] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24741
<6>[ 4.657012] EXT4-fs (mmcblk0p26): 2 orphan inodes deleted
<6>[ 4.657379] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 4.703216] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
<4>[ 4.758331] EXT4-fs (mmcblk0p27): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.760345] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 4.762298] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 4.886474] EXT4-fs (mmcblk0p28): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.888580] EXT4-fs (mmcblk0p28): recovery complete
<6>[ 4.890563] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: barrier=1
<7>[ 20.824981] mmc1: card_present 1
<6>[ 20.825134] mmc1: Slot status change detected (0 -> 1)
<7>[ 23.383300] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 23.383331] mmc1: new high speed SDIO card at address 0001
<3>[ 38.746368] mmc2: Data CRC error
<6>[ 38.746978] mmc2: Controller has been reset
<3>[ 38.747467] mmcblk1: error -84 transferring data, sector 2080, nr 1, card status 0x900
<6>[ 38.747619] mmc2: reinit card
<4>[ 38.747863] mmc2: Starting deferred resume
<3>[ 38.814849] mmc2: Data CRC error
<6>[ 38.815521] mmc2: Controller has been reset
<3>[ 38.815856] mmc2: Re-init card rc = -84 (retries = 5)
<3>[ 38.997650] mmc2: Data CRC error
<6>[ 38.998291] mmc2: Controller has been reset
<3>[ 39.001403] mmc2: Re-init card rc = -84 (retries = 4)
<3>[ 39.200927] mmc2: Data CRC error
<6>[ 39.201507] mmc2: Controller has been reset
<3>[ 39.201721] mmc2: Re-init card rc = -84 (retries = 3)
<3>[ 39.384826] mmc2: Data CRC error
<6>[ 39.385406] mmc2: Controller has been reset
<3>[ 39.385650] mmc2: Re-init card rc = -84 (retries = 2)
<3>[ 39.583618] mmc2: Data CRC error
<6>[ 39.584228] mmc2: Controller has been reset
<3>[ 39.584472] mmc2: Re-init card rc = -84 (retries = 1)
<6>[ 39.666137] mmc2: Deferred resume failed
<6>[ 39.666412] mmc: reinit failed, remove card
<6>[ 39.666625] mmc2: remove card
<3>[ 39.666778] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.667053] Buffer I/O error on device mmcblk1p1, logical block 32
<4>[ 39.667205] lost page write due to I/O error on mmcblk1p1
<3>[ 39.667480] mmc_blk_issue_rq failed!!
<6>[ 39.667633] mmc2: mmc_remove_sd_card
<6>[ 39.667907] mmc2: card 0001 removed
<3>[ 39.670318] mmcblk1: error -123 sending status comand
<3>[ 39.670471] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.670867] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.671783] mmc_blk_issue_rq failed!!
<3>[ 39.671966] mmcblk1: error -123 sending read command, response 0x0
<4>[ 39.672210] mmcblk1: retrying using single block read
<3>[ 39.672332] mmcblk1: error -123 sending status comand
<3>[ 39.672607] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.672882] end_request: I/O error, dev mmcblk1, sector 32378
<3>[ 39.673126] end_request: I/O error, dev mmcblk1, sector 32379
<3>[ 39.673278] end_request: I/O error, dev mmcblk1, sector 32380
<3>[ 39.673522] end_request: I/O error, dev mmcblk1, sector 32381
<3>[ 39.673675] end_request: I/O error, dev mmcblk1, sector 32382
<3>[ 39.673919] end_request: I/O error, dev mmcblk1, sector 32383
<3>[ 39.674072] end_request: I/O error, dev mmcblk1, sector 32384
<3>[ 39.674316] end_request: I/O error, dev mmcblk1, sector 32385
<3>[ 39.674499] mmc_blk_issue_rq failed!!
<3>[ 39.674774] mmcblk1: error -123 sending status comand
<3>[ 39.674926] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.675292] end_request: I/O error, dev mmcblk1, sector 32378
... and so on. In this run, I see that at least briefly the kernel could read the mmcblk1 partition table (although there still was not /dev/block/mmcblk1). However, most of the time it can't and just gives the CRC errors.
Is this a hardware or software problem. Any suggestions? Thanks.
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
worked!
demkantor said:
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Worked, thanks!!! The CRC errors made me suspect hardware, but I wanted someone else to say it before I tore the thing open. I've always had bad luck tearing these things apart (only junk phones in the past), but I bought a cheapo disassembly kit a while back which has helped greatly with popping the case off. And thankfully I only had to get to about step three of the instructions before the ribbon cable was accessible!
I know this is a common problem, and this is the fourth time this happens to my phone, but since last summer I have no warranty left to keep my phone alive.
My phone has too many unexpected random reboots, since four days they are increasing heavily, the three other times this happened HTC replaced the mainboard. I am using Flinnys CM 11 Alpha 3 since its release, I know it is unstable, but these kinds of problems are new and reflashing this rom or CM 10.1 did not helped.
I searched a bit and I found out nothing positive, but are there chances JTag can fix this problem? I haven't detected any mmc error yet, and I want to keep this phone alive, but it isn't worth to buy a new mainboard. My phone is S-Off with Engineering HBoot.
I do not want to buy JTag cables/acessoires without a chance it could fix that, since I would need to import something to Germany and I think my phone is hardware damaged, hoping I am wrong.
In recovery mode I checked MMC: adb shell dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.13.04.19_M androidboot.cid=HTC__102 androidboot.batt_poweron=good_battery androidboot.carrier=HTC-GER androidboot.mid=PC1011000 androidboot.keycaps=qwerty androidboot.mode=recovery androidboot.serialno=[I]*removed*[/I] androidboot.bootloader=0.84.2000 no_console_suspend=1 console=null
<6>[ 7.228332] vision: vision_init_mmc
<3>[ 8.179473] mmc0: No card detect facilities available
<6>[ 8.180084] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.180328] mmc0: Platform slot type: MMC
<6>[ 8.180480] mmc0: 4 bit data mode disabled
<6>[ 8.180603] mmc0: 8 bit data mode enabled
<6>[ 8.180847] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.180999] mmc0: Slot eject status = 0
<6>[ 8.181121] mmc0: Power save feature enable = 1
<6>[ 8.181274] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0f518000
<6>[ 8.181396] mmc0: DM cmd busaddr 0x0f518000, cmdptr busaddr 0x0f518300
<6>[ 8.182434] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 8.182678] mmc1: Platform slot type: N/A
<6>[ 8.182800] mmc1: 4 bit data mode enabled
<6>[ 8.182952] mmc1: 8 bit data mode disabled
<6>[ 8.183197] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.183349] mmc1: Slot eject status = 1
<6>[ 8.183593] mmc1: Power save feature enable = 1
<6>[ 8.183715] mmc1: DM non-cached buffer at ff00e000, dma_addr 0x0f519000
<6>[ 8.183990] mmc1: DM cmd busaddr 0x0f519000, cmdptr busaddr 0x0f519300
<6>[ 8.185363] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 8.185516] mmc2: Platform slot type: SD
<6>[ 8.185760] mmc2: 4 bit data mode enabled
<6>[ 8.185882] mmc2: 8 bit data mode disabled
<6>[ 8.186035] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.186279] mmc2: Slot eject status = 0
<6>[ 8.186401] mmc2: Power save feature enable = 1
<6>[ 8.186676] mmc2: DM non-cached buffer at ff00f000, dma_addr 0x0f51b000
<6>[ 8.186798] mmc2: DM cmd busaddr 0x0f51b000, cmdptr busaddr 0x0f51b300
<6>[ 8.187072] mmc2: Polling status mode enabled
<6>[ 8.345214] mmc0: new high speed MMC card at address 0001
<6>[ 8.347290] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<6>[ 8.348724] mmcblk0: p1 p2 p3 p4 < p5
<4>[ 8.635314] mmc2: high speed mode max_dtr = 50000000
<4>[ 8.635650] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 8.635894] mmc2: new high speed SDHC card at address e624
<6>[ 8.644683] mmcblk1: mmc2:e624 SU08G 7.40 GiB
<6>[ 8.645538] mmcblk1: p1
<6>[ 10.405792] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts:
<3>[ 10.565460] EXT3-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<3>[ 10.567626] EXT2-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<6>[ 10.618499] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 19.993225] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<6>[ 20.125244] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<3>[ 20.269561] EXT4-fs (mmcblk1p1): VFS: Can't find ext4 filesystem
<3>[ 20.274169] EXT4-fs (mmcblk1): VFS: Can't find ext4 filesystem
my phone says goodbye ;(
It now rebooted or made a sudden shutdown in the last hour at least four times.
Do you get the reboots if you leave it in recovery or bootloader? Can you rule out a sticky power button? Have you been able to capture a logcat or last_kmsg when this happens? It may be fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
I haven't got any reboots in bootloader or recovery mode, but my phone is not in recovery for long time, but i do not have a good possibility to test it, since i need the phone powered on. My power button is not sticky, besides it has been replaced last year. No i have not been able to capture it yet, every time my phone has these problems i am not sitting next to my pc, i will try to get these. Thank you for your answer.
Since this morning I am running logcat and kmsg, but no reboots since i started capturing.
Full logs: kmsg.log logcat.log
Edit: Sorry I have seen you wanted last_kmsg, I have attached it now
log is very long so I hope I found all relevant information, don't know but this seems to be relevant:
Code:
E/ConsumerIrService( 1902): Can't open consumer IR HW Module, error: -2
[...]
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
I ran kmsg the first time, so I don't know what is relevant, but I think this could be, since it is returning over and over again:
Code:
<6>[ 745.429565] msm_vidc_enc: Inside vid_enc_open()
<4>[ 745.433837]
<4>[ 745.433837] res_trk_download_firmware(): Request firmware download
<6>[ 745.592529] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 745.598175]
<6>[ 745.598175] msm_vidc_enc: Inside vid_enc_release()
<6>[ 745.598449]
<6>[ 745.598449] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 745.600219]
<6>[ 745.600250] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to client
<6>[ 746.333374] [LS][CM3602] ALS value: 0x1, level: 0 #
<6>[ 747.293975] [LS][CM3602] ALS value: 0x0, level: 0 #
<6>[ 747.451019] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 747.548919] call alarm, type 3, func alarm_triggered+0x0/0xd8, 0 (s 0)
<6>[ 749.616058] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 750.089538] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 750.597900] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 750.627227]
<6>[ 750.627227] msm_vidc_enc: Return from vid_enc_release()
<6>[ 750.672058] [CAM]msm_enqueue: queue event new max is 6
<6>[ 750.893615] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 750.895965] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526264000000 (s 1526264000000)
<6>[ 751.206268] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.206787] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 751.710205] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.710632] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<4>[ 752.062774] send sigkill to 5943 (nt.android.mail), adj 764, size 6342
<6>[ 753.234069] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1529883000000 (s 1529883000000)
<4>[ 753.447265] send sigkill to 5929 (droid.gallery3d), adj 647, size 4243
<4>[ 754.797363] send sigkill to 6155 (.bitspin.timely), adj 647, size 10701
<6>[ 755.095642] microp_led_pwm_brightness_set, data[1] = 45
<6>[ 760.327087] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1536976000000 (s 1536976000000)
<6>[ 760.764038] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537413000000 (s 1537413000000)
<6>[ 760.990051] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537639000000 (s 1537639000000)
<6>[ 761.089080] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537738000000 (s 1537738000000)
<6>[ 762.833496] [CAM] vfe31_proc_general: V31_STOP
<6>[ 762.833587] [CAM]vfe_stop() enter
<6>[ 762.834442] [CAM]vfe_stop() exit
<6>[ 762.834625] [CAM] irq resetAckIrq
<6>[ 762.834747] [CAM] irq resetAckIrq
<6>[ 762.893371] [CAM]msm_release_frame: frame0
<6>[ 762.893463] [CAM]__msm_release:sync->opencnt:3
<6>[ 762.895507] [CAM]release frame atomic_set pmsm->opened as 0
<6>[ 762.895629] [CAM] msm_release_frame: draining queue frame
<6>[ 762.895812] [CAM]msm_release_frame,q->len = 0
<6>[ 762.903411] [CAM] msm_release_frame, completed
<6>[ 763.018707] [CAM] msm_pmem_table_add: type 15, paddr 0x2dd96000, vaddr 0x43b30000
<6>[ 763.031066] [CAM] msm_pmem_table_add: type 15, paddr 0x2dee8000, vaddr 0x43f4a000
<6>[ 763.036804] [CAM] msm_pmem_table_add: type 15, paddr 0x2e03a000, vaddr 0x4426a000
<6>[ 763.047454] [CAM] msm_pmem_table_add: type 15, paddr 0x2e18c000, vaddr 0x446a3000
<6>[ 763.069427] [CAM] msm_pmem_table_add: type 15, paddr 0x2e2de000, vaddr 0x44a4e000
<6>[ 763.085021] [CAM] msm_pmem_table_add: type 15, paddr 0x2e430000, vaddr 0x44de3000
<6>[ 763.094635] [CAM] msm_pmem_table_add: type 15, paddr 0x2e582000, vaddr 0x450a0000
<6>[ 763.103454] [CAM] msm_pmem_table_add: type 14, paddr 0x2e6d4000, vaddr 0x45237000
<6>[ 763.110900] [CAM] msm_pmem_table_add: type 14, paddr 0x2e826000, vaddr 0x45389000
<6>[ 763.116973] [CAM] msm_pmem_table_add: type 14, paddr 0x2e978000, vaddr 0x454db000
<6>[ 763.153625] [CAM] msm_pmem_table_add: type 14, paddr 0x2eaca000, vaddr 0x4562d000
<6>[ 763.171356] [CAM] msm_pmem_table_add: type 14, paddr 0x2ec1c000, vaddr 0x4577f000
<6>[ 763.180114] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1539829000000 (s 1539829000000)
<6>[ 763.186645] [CAM] msm_pmem_table_add: type 14, paddr 0x2ed6e000, vaddr 0x458d1000
<6>[ 763.199859] [CAM] msm_pmem_table_add: type 14, paddr 0x2eec0000, vaddr 0x45a23000
<6>[ 763.225616] [CAM] msm_pmem_table_add: type 14, paddr 0x2f012000, vaddr 0x45b75000
<6>[ 763.241241] [CAM] msm_pmem_table_add: type 16, paddr 0x2f164000, vaddr 0x45cc7000
<4>[ 763.254211] [CAM]msm_pp_release: pp not in progress for 0
<6>[ 763.255645] [CAM] vfe31_proc_general: V31_RESET
<6>[ 763.255859] [CAM] irq resetAckIrq
<6>[ 763.263153] [CAM] vfe31_config_axi: mode = 3, bufnum1 = 3, bufnum2 = 3
<6>[ 763.286712] [CAM] vfe31_proc_general: V31_START
<6>[ 763.288665] [CAM] VFE opertaion mode = 0x2.
<6>[ 763.288848] [CAM] VFE output path out mode = 0x5.
<6>[ 763.344512] [CAM] irq camifSofIrq, count 1
<6>[ 763.354034] [CAM] irq startAckIrq
<6>[ 763.354278] [CAM] msm_camio_disable_csi_log
<6>[ 763.379516] [CAM]>>>>>>>>(2014-04-30 06:17:13.763715307 UTC)<<<<<<<
<6>[ 763.379791] [CAM]msm_open_common: open frame0
<6>[ 763.379882] [CAM] msm_open_common: rc 0
<4>[ 763.969879] send sigkill to 5738 (gle.android.gms), adj 647, size 5183
<6>[ 764.134490]
<6>[ 764.134490] msm_vidc_enc: Inside vid_enc_open()
<6>[ 764.193817] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 764.206939]
<6>[ 764.206939] msm_vidc_enc: Inside vid_enc_release()
<6>[ 764.208923]
<6>[ 764.208953] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 764.209320]
<6>[ 764.209320] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to clientsend sigkill to 6186 (nt.android.mail), adj 529, size 7345
<6>[ 764.723083] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1541372000000 (s 1541372000000)
<4>[ 764.739593] send sigkill to 5086 (ndroid.settings), adj 529, size 5385
<6>[ 768.847198] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 769.207122] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 769.237396]
The logcat would have to be running during reboot to get much out of it, so if its not easily replicable then try to get the kernel log. So right after reboot grab the last_kmsg, this should give the reason for the reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you for your help, I will see what I can do, but my phone is really annoying me. Everytime I am at home, and have the possibility to get logcat during reboot my phone runs perfectly, but when I am outside you can imagine what it does.
If I am not able to get a logcat soon or the problems suddenly stop, I will buy a new phone.
At home are you always on WiFi? Maybe there is an issue with your radio where switching between 3g/2g or whatever causes constant reboots?
Just a thought but maybe try flashing a new radio
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am using latest radio 26.13.04.19_M since last summer and haven't had any problems yet. I will reflash it and if problems aren't gone I will try to downgrade. Perhaps something is messed up.
No I am not constantly on WiFi, besides my WiFi does not reach all rooms/floors so my phone sometimes switches to 3g. Also it is not constantly rebooting, it may work some hours, a day (only yesterday), or only half an hour, I am doing different actions, while getting reboots. Like sending a video with WhatsApp or something else, even if I do nothing, it is just laying around on a table.
Flashing new radio reduced the reboots, but they aren't gone. Now I also have network-connection issues, my phone disconnect itself from carrier (with full signal strength, my friends with same carrier have also full signal strength at the same time), I am missing important phone calls, so I flashed back 26.13.04.19_M, but the problem isn't gone. Force closes with apps which worked fine before (like WhatsApp) are increasing.
Since three days my phone does not recognize my original charger correctly, it needs about 4 hours to get 100%, wiping battery stats didn't helped. Perhaps it is more than three days, normally I plug in charger when I go sleeping. This is happening with two original batteries (one I bought last year).
I do not have any hope left I was wrong with hardware problem. So I will buy LG G2 on Tuesday, if I can't reduce the problems, I need a working phone.
Hi folks!
I purchased an OTG micro-sd reader, but I get the power consumption error when I plug it in my rooted Z1c 5.1.1.
I learned about the /sys/bus/usb/devices/1-1/bConfigurationValue trick, but my /devices/ folder is empty so I can't use it...
Here is the relevant log from dmesg:
<6>[ 1632.217199] xhci-hcd xhci-hcd: xHCI Host Controller
<6>[ 1632.217212] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
<6>[ 1632.217293] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000
<6>[ 1632.218513] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1632.218520] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1632.218525] usb usb1: Product: xHCI Host Controller
<6>[ 1632.218530] usb usb1: Manufacturer: Linux 3.4.0-perf-gd26777b-00851-ga8b7b55 xhci-hcd
<6>[ 1632.218535] usb usb1: SerialNumber: xhci-hcd
<7>[ 1632.219525] xHCI xhci_add_endpoint called for root hub<7>[ 1632.219531] xHCI xhci_check_bandwidth called for root hub
<6>[ 1632.220004] hub 1-0:1.0: USB hub found
<6>[ 1632.220016] hub 1-0:1.0: 1 port detected
<6>[ 1632.220670] xhci-hcd xhci-hcd: xHCI Host Controller
<6>[ 1632.220680] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
<6>[ 1632.220723] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
<6>[ 1632.220729] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1632.220734] usb usb2: Product: xHCI Host Controller
<6>[ 1632.220738] usb usb2: Manufacturer: Linux 3.4.0-perf-gd26777b-00851-ga8b7b55 xhci-hcd
<6>[ 1632.220743] usb usb2: SerialNumber: xhci-hcd
<7>[ 1632.221100] xHCI xhci_add_endpoint called for root hub<7>[ 1632.221105] xHCI xhci_check_bandwidth called for root hub
<6>[ 1632.221811] hub 2-0:1.0: USB hub found
<6>[ 1632.221824] hub 2-0:1.0: 1 port detected
<4>[ 1632.324911] healthd: battery l=71 v=3941 t=41.8 h=2 st=3 c=-358 chg=
<4>[ 1632.379681] healthd: battery l=71 v=3949 t=41.9 h=2 st=3 c=-510 chg=
<6>[ 1632.538218] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1632.559752] usb 1-1: New USB device found, idVendor=14cd, idProduct=1212
<6>[ 1632.559764] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
<6>[ 1632.559775] usb 1-1: Product: Mass Storage Device
<6>[ 1632.559783] usb 1-1: Manufacturer: Generic
<6>[ 1632.559791] usb 1-1: SerialNumber: 121220130416
<4>[ 1632.560162] usb 1-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1632.561670] usb 1-1: ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1632.563063] scsi8 : usb-storage 1-1:1.0
<6>[ 1632.628390] qpnp_chg_check_unpluged_charger: Assume reverse boost issue happens
<5>[ 1633.558981] scsi 8:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS
<3>[ 1633.609919] qpnp_regulator_vs_ocp_isr: 8941_mvs1: OCP triggered 11 times; no further retries
<6>[ 1633.613501] usb 1-1: USB disconnect, device number 2
<6>[ 1633.613717] dwc3_ocp_work: receive ocp notification
<6>[ 1633.613725] dwc3 f9200000.dwc3: XCVR: ID clear
<6>[ 1633.613730] dwc3 f9200000.dwc3: XCVR: BSV clear
<6>[ 1633.613737] dwc3 f9200000.dwc3: a_host state
<6>[ 1633.613873] xhci-hcd xhci-hcd: remove, state 1
<6>[ 1633.613884] usb usb2: USB disconnect, device number 1
<7>[ 1633.614020] xHCI xhci_drop_endpoint called for root hub
<7>[ 1633.614025] xHCI xhci_check_bandwidth called for root hub
<6>[ 1633.614311] xhci-hcd xhci-hcd: USB bus 2 deregistered
<6>[ 1633.614320] xhci-hcd xhci-hcd: remove, state 1
<6>[ 1633.614329] usb usb1: USB disconnect, device number 1
<5>[ 1633.628477] sd 8:0:0:0: [sda] READ CAPACITY failed
<6>[ 1633.628490] sd 8:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<5>[ 1633.628497] sd 8:0:0:0: [sda] Sense not available.
<5>[ 1633.628539] sd 8:0:0:0: [sda] Write Protect is off
<7>[ 1633.628549] sd 8:0:0:0: [sda] Mode Sense: 13 01 00 00
<5>[ 1633.628586] sd 8:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<5>[ 1633.629184] sd 8:0:0:0: [sda] Attached SCSI removable disk
<3>[ 1633.630437] hub 1-0:1.0: hub_port_status failed (err = -19)
<3>[ 1633.630449] hub 1-0:1.0: connect-debounce failed, port 1 disabled
<7>[ 1633.630608] xHCI xhci_drop_endpoint called for root hub
<7>[ 1633.630613] xHCI xhci_check_bandwidth called for root hub
<6>[ 1633.630940] xhci-hcd xhci-hcd: USB bus 1 deregistered
<4>[ 1633.679917] healthd: battery l=71 v=3916 t=42.0 h=2 st=3 c=-776 chg=
<4>[ 1633.719931] healthd: battery l=71 v=3898 t=42.1 h=2 st=3 c=-911 chg=
<6>[ 1633.924292] usb_host_ext_event: sending USB_HOST_VBUS_DROP event
<6>[ 1633.925266] dwc3 f9200000.dwc3: a_idle state
<6>[ 1634.118262] qpnp_chg_rb_work: stopping worker usb/dc disconnected
<4>[ 1634.184094] healthd: battery l=71 v=3906 t=42.0 h=2 st=3 c=-841 chg=
<4>[ 1634.212750] healthd: battery l=71 v=3905 t=42.0 h=2 st=3 c=-774 chg=
Click to expand...
Click to collapse
I tried plugging the reader on the OTG Sony cable I got with the phone, same error message.
Any idea?
People online mention a "USB detection" toggle but I don't seem to have such a thing.
Cheers!
Edit: the reader works fine on my computer, and another USB drive works fine on the phone with my OTG cable.
I think this specific micro-sd reader exceeds the mA threshold set on the phone, and I would like to override that threshold.