Trying to use the emmc on a Pine A64 LTS (V 1.2) or Sopine Rev C in a Baseboard Model A Rev B fails. The same problem exists when either creating a bootable emmc and inserting it, or when booting from SD and then trying to write the emmc: [ 1513.241425] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 1514.244971] sunxi-mmc 1c11000.mmc: send stop command failed Kernel is 5.2.9-200.fc30.aarch64 I have never seen this work. This issue below may be related and has a proposed fix: https://forum.armbian.com/topic/10140-pine-h64-model-a-emmc-boot-stuck-sunxi-mmc-4022000mmc-data-error-sending-stop-command/
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
(In reply to Justin M. Forbes from comment #1) > *********** MASS BUG UPDATE ************** > > We apologize for the inconvenience. There are a large number of bugs to go > through and several of them have gone stale. Due to this, we are doing a > mass bug update across all of the Fedora 30 kernel bugs. > > Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel > update (or newer) and let us know if you issue has been resolved or if it is > still present with the newer kernel. > > If you have moved on to Fedora 31, and are still experiencing this issue, > please change the version to Fedora 31. > > If you experience different issues, please open a new bug report for those. This still happens in F31 today: [ 923.254753] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.261885] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.268879] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.275921] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.283090] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.290110] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.296634] blk_update_request: I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 923.308214] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.315309] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.322441] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.329443] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.336463] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.343603] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.350100] blk_update_request: I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 923.360570] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 923.368686] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.375774] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.382903] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.389902] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.396947] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.404195] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 923.410699] blk_update_request: I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 923.421171] Buffer I/O error on dev mmcblk1, logical block 0, async page read [ 928.517563] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 928.525443] sunxi-mmc 1c11000.mmc: data error, sending stop command [ 929.531289] sunxi-mmc 1c11000.mmc: send stop command failed # uname -a Linux hendrix 5.5.5-200.fc31.aarch64 #1 SMP Wed Feb 19 23:14:55 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.