Random reboot issue in some 2 gb devices

[Ajaykumar70]

2019-07-29_12.58-Full_logs.zip
2019-07-29_12.39.zip

I'm talking about my 2gb 16 gb version of land Redmi 3s
Actually here are some user are facing such issue in 4.9 kernel. Mine also........
April build is running awesome flawless with 3.18 kernel but june and July months build are not working properly with my device.... I'm facing random reboot after every 15to 20 minutes of usage.
Facing this issue only with 4.9 kernel.
Currently i'm trying latest release and facing same issue but little bit less compare to 7 July build.
Don't know why only some users are facing such issue in 2gb model because there are too many user using this build with kernel 4.9 and not facing any single issue.
Please sir try to understand.... What problem we are facing..... Because nobody is ready to trust us everybody thinks that we are doing something wrong.... But trust me I'm doing anything wrong and always flash the rom after cleaning evening.
My steps....
1.Backup my internal storage data
2.format data
3 clean all partition
4.flash rom
5.flash nano gapps
6.wipe cache and dalvik
7.reboot
Every time i uses these steps to flash a new rom.
Please sir because we don't want to leave this beautiful rom.

[Ajaykumar70]

Please check logs i have attached.
2019-07-29_12.58-Full_logs.zip

[rupansh]

that's kinda cringe bro

[Ajaykumar70]

that's kinda cringe bro

No bro.... Actually i want to prove that we are not wrong..... Because everyone is thinking that that we are doing something wrong that's why we are facing such issue because here are a lot of 2gb users using the 4.9 kernel and not facing any single issue

[rupansh]

that's kinda cringe bro

No bro.... Actually i want to prove that we are not wrong..... Because everyone is thinking that that we are doing something wrong that's why we are facing such issue because here are a lot of 2gb users using the 4.9 kernel and not facing any single issue

That's the cringe part bro

[Ajaykumar70]

that's kinda cringe bro

No bro.... Actually i want to prove that we are not wrong..... Because everyone is thinking that that we are doing something wrong that's why we are facing such issue because here are a lot of 2gb users using the 4.9 kernel and not facing any single issue

That's the cringe part bro

I know you are right from your side but if i will be unable to prove this issue then here are too many people will be pointed as they were wrong.
That why I'm doing this

[Ajaykumar70]

I'm providing you the final logs because right now I was facing major issue. My display was fluctuating that why I'm going change Rom.
These logs definitely help you to understand the problem.
2019-07-29_15.17.zip

[nichcream]

There's nothing cringeworthy with a proper bug report. If you are able to support your findings with the right logs I would be able to 1) Know that you're not making up stories 2) Determine if the issue is indeed valid and not caused by some bad app or mod 3) Narrow down to the root cause of the issue
Which is pretty much what the whole of XDA isn't doing.

Ajaykumar's issue appears to be eMMC related.

[ 1009.207155] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1009.207179] mmc0: tuning execution failed: -5
[ 1009.207235] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1016.644521] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1016.644550] mmc0: tuning execution failed: -5
[ 1016.644624] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1022.157676] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1022.157700] mmc0: tuning execution failed: -5
[ 1022.157790] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1043.907621] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1043.907645] mmc0: tuning execution failed: -5
[ 1043.910454] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
[ 1043.910630] mmcblk0: error -110 sending status command, retrying
[ 1043.910704] mmcblk0: error -110 sending status command, retrying
[ 1043.910777] mmcblk0: error -110 sending status command, aborting
[ 1049.245639] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1049.245668] mmc0: tuning execution failed: -5
[ 1049.245726] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1052.982871] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1052.982896] mmc0: tuning execution failed: -5
[ 1052.982978] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900

He has a Hynix eMMC:

[    2.769973] mmc0: eMMC FW version: 0x58
[    2.769979] mmc0: cache barrier support 0 flush policy 0
[    2.792327] mmc0: new HS400 MMC card at address 0001
[    2.793036] sdhci_msm_pm_qos_cpu_init (): voted for group #0 (mask=0xf) latency=-1
[    2.793047] sdhci_msm_pm_qos_cpu_init (): voted for group #1 (mask=0xf0) latency=-1
[    2.793173] mmcblk0: mmc0:0001 HAG2e� 14.7 GiB 

While mine has a Toshiba eMMC:

[    2.814525] mmc0: eMMC FW version: 0x02
[    2.814530] mmc0: cache barrier support 1 flush policy 1
[    2.823760] mmc0: new HS400 Enhanced strobe MMC card at address 0001
[    2.824459] sdhci_msm_pm_qos_cpu_init (): voted for group #0 (mask=0xf) latency=-1
[    2.824469] sdhci_msm_pm_qos_cpu_init (): voted for group #1 (mask=0xf0) latency=-1
[    2.824590] mmcblk0: mmc0:0001 016G70 14.7 GiB 

Different eMMCs have historically caused undesired behaviours on some devices. I haven't gone deep enough to know the actual cause yet. Give me till the weekend to look.

@Ajaykumar70 Were those logs taken after a random reboot? And also after the random reboot, was the device booted into recovery mode or system?

[Ajaykumar70]

There's nothing cringeworthy with a proper bug report. If you are able to support your findings with the right logs I would be able to 1) Know that you're not making up stories 2) Determine if the issue is indeed valid and not caused by some bad app or mod 3) Narrow down to the root cause of the issue
Which is pretty much what the whole of XDA isn't doing.

Ajaykumar's issue appears to be eMMC related.

[ 1009.207155] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1009.207179] mmc0: tuning execution failed: -5
[ 1009.207235] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1016.644521] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1016.644550] mmc0: tuning execution failed: -5
[ 1016.644624] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1022.157676] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1022.157700] mmc0: tuning execution failed: -5
[ 1022.157790] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1043.907621] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1043.907645] mmc0: tuning execution failed: -5
[ 1043.910454] mmc0: sdhci_cmd_irq: AUTO CMD err sts 0x00000002
[ 1043.910630] mmcblk0: error -110 sending status command, retrying
[ 1043.910704] mmcblk0: error -110 sending status command, retrying
[ 1043.910777] mmcblk0: error -110 sending status command, aborting
[ 1049.245639] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1049.245668] mmc0: tuning execution failed: -5
[ 1049.245726] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900
[ 1052.982871] mmc0: sdhci_msm_execute_tuning: no tuning point found
[ 1052.982896] mmc0: tuning execution failed: -5
[ 1052.982978] mmcblk0: <private info omitted> error -5 sending read/write command, card status 0x900

He has a Hynix eMMC:

[    2.769973] mmc0: eMMC FW version: 0x58
[    2.769979] mmc0: cache barrier support 0 flush policy 0
[    2.792327] mmc0: new HS400 MMC card at address 0001
[    2.793036] sdhci_msm_pm_qos_cpu_init (): voted for group #0 (mask=0xf) latency=-1
[    2.793047] sdhci_msm_pm_qos_cpu_init (): voted for group #1 (mask=0xf0) latency=-1
[    2.793173] mmcblk0: mmc0:0001 HAG2e� 14.7 GiB 

While mine has a Toshiba eMMC:

[    2.814525] mmc0: eMMC FW version: 0x02
[    2.814530] mmc0: cache barrier support 1 flush policy 1
[    2.823760] mmc0: new HS400 Enhanced strobe MMC card at address 0001
[    2.824459] sdhci_msm_pm_qos_cpu_init (): voted for group #0 (mask=0xf) latency=-1
[    2.824469] sdhci_msm_pm_qos_cpu_init (): voted for group #1 (mask=0xf0) latency=-1
[    2.824590] mmcblk0: mmc0:0001 016G70 14.7 GiB 

Different eMMCs have historically caused undesired behaviours on some devices. I haven't gone deep enough to know the actual cause yet. Give me till the weekend to look.

@Ajaykumar70 Were those logs taken after a random reboot? And also after the random reboot, was the device booted into recovery mode or system?

After every reboot device starts again normally. And some time my display start fluctuate like my device is taking very heavy load. That's why I cant use the rom i just installed the rom to provide you logs so that you could chk and solve the problem.
This is the last log file taken by me. And one more thing i dont use magis or su with this rom only flased today for taking logs
2019-07-29_16.24.zip

[nichcream]

The question was whether the logs were taken after the random reboot where you said your "device starts again normally". It needs to be done that way so that the pstore catches the last bad events before reboot.

[Ajaykumar70]

The question was whether the logs were taken after the random reboot where you said your "device starts again normally". It needs to be done that way so that the pstore catches the last bad events before reboot.

Obviously...... The logs were taken after the random reboot. Because you can't take logs or do anything if the device stuck.
Anyway I captured the 3 logs........ After 1st reboot...... After 2nd ... And after 3rd reboot..... And i have provided you all the log files.
My device is rebooting frequently and sometimes display also fluctuate that's why I can't use the rom anymore.
Now i have changed rom that's why i can't provide you anything to identify the problem.
This is the last log file taken by me. Already attached in last comment.
2019-07-29_16.24.zip