[AT&T Samsung Galaxy S 4 Android Development] AlaskaLinuxUser:
Logcat errors

Logcat issues and as much of a breakdown as I can discern:

<6>[ 314.568237] MDP: unknown ioctl (cmd=40146da2) received!

According to https://code.google.com/p/android/issues/detail?id=63823 this is a problem with the graphical interface. Probably related to why we need to check Disable HW overlays, and why it imporves performance to check force GPU rendering.

<3>[ 314.969726] hsicctl hsicctl0: rmnet_ctl_open: Timeout opening hsicctl0

As far as I can tell, this reference is for rmnet, or the cellular interface. It requires opening /dev/hsicctl0. Which, I have verified does exist in our /dev tree on CM11. However, it obviously has an issue opening it and eventually gives up. It later will attempt to open it several more times, as seen in the logcat, and subsequently fails.

Relevant files:

/dev/hsicctl3
/dev/hsicctl2
/dev/hsicctl1
/dev/hsicctl0

/sys/devices/virtual/hsicctl
/sys/devices/virtual/hsicctl/hsicctl0
/sys/devices/virtual/hsicctl/hsicctl0/dev
/sys/devices/virtual/hsicctl/hsicctl0/power
/sys/devices/virtual/hsicctl/hsicctl0/power/control
/sys/devices/virtual/hsicctl/hsicctl0/power/runtime_active_time
/sys/devices/virtual/hsicctl/hsicctl0/power/autosuspend_delay_ms
/sys/devices/virtual/hsicctl/hsicctl0/power/runtime_status
/sys/devices/virtual/hsicctl/hsicctl0/power/runtime_suspended_time
/sys/devices/virtual/hsicctl/hsicctl0/subsystem
/sys/devices/virtual/hsicctl/hsicctl0/uevent
/sys/devices/virtual/hsicctl/hsicctl0/modem_wait
/sys/devices/virtual/hsicctl/hsicctl1
/sys/devices/virtual/hsicctl/hsicctl1/dev
/sys/devices/virtual/hsicctl/hsicctl1/power
/sys/devices/virtual/hsicctl/hsicctl1/power/control
/sys/devices/virtual/hsicctl/hsicctl1/power/runtime_active_time
/sys/devices/virtual/hsicctl/hsicctl1/power/autosuspend_delay_ms
/sys/devices/virtual/hsicctl/hsicctl1/power/runtime_status
/sys/devices/virtual/hsicctl/hsicctl1/power/runtime_suspended_time
/sys/devices/virtual/hsicctl/hsicctl1/subsystem
/sys/devices/virtual/hsicctl/hsicctl1/uevent
/sys/devices/virtual/hsicctl/hsicctl1/modem_wait
/sys/devices/virtual/hsicctl/hsicctl2
/sys/devices/virtual/hsicctl/hsicctl2/dev
/sys/devices/virtual/hsicctl/hsicctl2/power
/sys/devices/virtual/hsicctl/hsicctl2/power/control
/sys/devices/virtual/hsicctl/hsicctl2/power/runtime_active_time
/sys/devices/virtual/hsicctl/hsicctl2/power/autosuspend_delay_ms
/sys/devices/virtual/hsicctl/hsicctl2/power/runtime_status
/sys/devices/virtual/hsicctl/hsicctl2/power/runtime_suspended_time
/sys/devices/virtual/hsicctl/hsicctl2/subsystem
/sys/devices/virtual/hsicctl/hsicctl2/uevent
/sys/devices/virtual/hsicctl/hsicctl2/modem_wait
/sys/devices/virtual/hsicctl/hsicctl3
/sys/devices/virtual/hsicctl/hsicctl3/dev
/sys/devices/virtual/hsicctl/hsicctl3/power
/sys/devices/virtual/hsicctl/hsicctl3/power/control
/sys/devices/virtual/hsicctl/hsicctl3/power/runtime_active_time
/sys/devices/virtual/hsicctl/hsicctl3/power/autosuspend_delay_ms
/sys/devices/virtual/hsicctl/hsicctl3/power/runtime_status
/sys/devices/virtual/hsicctl/hsicctl3/power/runtime_suspended_time
/sys/devices/virtual/hsicctl/hsicctl3/subsystem
/sys/devices/virtual/hsicctl/hsicctl3/uevent
/sys/devices/virtual/hsicctl/hsicctl3/modem_wait

<3>[ 341.679626] mmc1: CMD52: Command CRC error

According to http://xdaforums.com/showthread.php?t=2579229&page=223 these errors appear to relate to the mmcblk storage and/or filesystems. There are some differences seen in this comparison between a regular SS rom and the CM11SS rom:

OmegaRom
Filesystem Size Used Free Blksize
/dev 908.7M 72.0K 908.6M 4096
/dev 908.7M 72.0K 908.6M 4096
/sys/fs/cgroup 908.7M 12.0K 908.7M 4096
/sys/fs/cgroup 908.7M 12.0K 908.7M 4096
/mnt/secure 908.7M 0.0K 908.7M 4096
/mnt/secure/asec 59.7G 23.2G 36.5G 131072
/mnt/secure 908.7M 0.0K 908.7M 4096
/mnt/secure/asec 59.7G 23.2G 36.5G 131072
/mnt/secure/asec 59.7G 23.2G 36.5G 131072
/mnt/asec 908.7M 0.0K 908.7M 4096
/mnt/asec 908.7M 0.0K 908.7M 4096
/mnt/asec/com.quoord.tapatalkxda.activity-1 5.0M 3.8M 1.2M 4096
/mnt/obb 908.7M 0.0K 908.7M 4096
/mnt/obb 908.7M 0.0K 908.7M 4096
/datamedia 9.7G 5.2G 4.5G 4096
/ss 9.7G 5.2G 4.5G 4096
/system 2.7G 1.7G 938.4M 4096
/data 2.4G 1.4G 1.0G 4096
/cache 298.6M 3.5M 295.1M 4096
/efs 13.4M 4.3M 9.2M 4096
/persdata/absolute 8.9M 4.1M 4.8M 4096
/firmware 86.0M 11.5M 74.4M 16384
/firmware-mdm 86.0M 49.6M 36.3M 16384
/mnt/shell/container 2.4G 1.4G 1.0G 4096
/mnt/shell/emulated 2.4G 1.5G 911.7M 4096
/storage/emulated 908.7M 0.0K 908.7M 4096
/mnt/media_rw/extSdCard 59.7G 23.2G 36.5G 131072
/storage/extSdCard 59.7G 23.2G 36.5G 131072
/storage/emulated/0 2.4G 1.5G 911.7M 4096

CM11SS
Filesystem Size Used Free Blksize
/dev 908.7M 136.0K 908.6M 4096
/sys/fs/cgroup 908.7M 12.0K 908.7M 4096
/mnt/secure 908.7M 0.0K 908.7M 4096
/mnt/secure/asec 908.7M 0.0K 908.7M 4096
/mnt/asec 908.7M 0.0K 908.7M 4096
/mnt/obb 908.7M 0.0K 908.7M 4096
/system 2.7G 454.4M 2.2G 4096
/data 9.7G 5.2G 4.5G 4096
/cache 2.0G 39.0M 2.0G 4096
/efs 13.4M 4.3M 9.2M 4096
/persdata/absolute 8.9M 4.1M 4.8M 4096
/firmware 86.0M 11.5M 74.4M 16384
/firmware-mdm 86.0M 49.6M 36.3M 16384
/storage/extSdCard 59.7G 23.2G 36.5G 131072
/mnt/shell/container 9.7G 5.2G 4.5G 4096
/mnt/shell/emulated 9.7G 5.2G 4.5G 4096
/storage/emulated 908.7M 0.0K 908.7M 4096
/storage/emulated/0 9.7G 5.2G 4.5G 4096
/storage/emulated/legacy 9.7G 5.2G 4.5G 4096
/storage/emulated 908.7M 0.0K 908.7M 4096
/storage/emulated/0 9.7G 5.2G 4.5G 4096
/storage/emulated/0/Android/obb 9.7G 5.2G 4.5G 4096
/storage/emulated/legacy 9.7G 5.2G 4.5G 4096
/storage/emulated/legacy/Android/obb 9.7G 5.2G 4.5G 4096

<4>[ 341.688049] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=01, Err: -84

http://talk.radxa.com/topic/1073/bcmsdh_sdmmc-read-write-errors-in-dmesg/3 Shows this error as being related to the WiFi or Bluetooth driver. The WiFi and Bluetooth both work, so I don't know if this is a valid concern.

<6>[ 367.801483] binder: 1031:1447 transaction failed 29189, size 4-0

<6>[ 367.801544] binder: send failed reply for transaction 9357, target dead

These are binder issues http://elinux.org/Android_Binder that cause a breakdown in the IPC, or inter process communication. This may be a problem, but it is sporatic in the logcat.

So my goal is to focus on the hsicctl0 error, as I feel this is the most relavent for our inability to use the cellular.