Sunxi mmc 1c10000 mmc data error sending stop command

2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,996,16878692493,-;mmc0: Card stuck in programming state! mmc_do_erase
2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,997,16878692530,-;blk_update_request: I/O error, dev mmcblk0, sector 10335392 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,998,16878692736,-;mmc_erase: group start error -110, status 0x0
2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,999,16878692755,-;blk_update_request: I/O error, dev mmcblk0, sector 10466560 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,1000,16878692885,-;sunxi-mmc 1c0f000.mmc: data error, sending stop command
2020-03-07T12:59:50+01:00 srv-orangepir1-140-service/srv-orangepir1-140-service SUBSYSTEM=platform
2020-03-07T12:59:50+01:00 srv-orangepir1-140-service/srv-orangepir1-140-service DEVICE=+platform:1c0f000.mmc
2020-03-07T12:59:50+01:00 s_dev_kernel_kmsg@srv-orangepir1-140-user kernel: 3,1001,16878692905,-;sunxi-mmc 1c0f000.mmc: send stop command failed
2020-03-07T12:59:50+01:00 srv-orangepir1-140-service/srv-orangepir1-140-service SUBSYSTEM=platform
2020-03-07T12:59:50+01:00 srv-orangepir1-140-service/srv-orangepir1-140-service DEVICE=+platform:1c0f000.mmc

After this  error, not possible  to connect via  ssh  on target ..

When trying to connect on local tty, then following error in loop…

Port /dev/tty-target-srv-orangepir1-140-position-1.2.4.4.3

Press CTRL-A Z for help on special keys

êRead-error on swap-device (179:0:918360)
[18207.712698] Kernel panic — not syncing: Attempted to kill init! exitcode=0x00000007
[18207.720401] CPU: 1 PID: 1 Comm: init Not tainted 5.5.0-sunxi #trunk.034
[18207.727030] Hardware name: Allwinner sun8i Family
[18207.731774] [<c010db0d>] (unwind_backtrace) from [<c010a139>] (show_stack+0x11/0x14)
[18207.739997] [<c010a139>] (show_stack) from [<c0962e6b>] (dump_stack+0x6f/0x7c)
[18207.747329] [<c0962e6b>] (dump_stack) from [<c011b99d>] (panic+0xcd/0x24c)
[18207.754210] [<c011b99d>] (panic) from [<c011fc39>] (do_exit+0x86d/0x884)
[18207.760914] [<c011fc39>] (do_exit) from [<c011fcab>] (do_group_exit+0x2f/0x84)
[18207.768142] [<c011fcab>] (do_group_exit) from [<c01288e7>] (get_signal+0x127/0x740)
[18207.775804] [<c01288e7>] (get_signal) from [<c0109a5f>] (do_work_pending+0xc3/0x42c)
[18207.783552] [<c0109a5f>] (do_work_pending) from [<c0101077>] (slow_work_pending+0x9/0x16)
[18207.791729] Exception stack(0xcf8f9fb0 to 0xcf8f9ff8)
[18207.796783] 9fa0:                00d3f8a4 004d833c b6e94000 0000015c
[18207.804964] 9fc0: 00d3f8a4 bec257ec 004d8324 004e921c 00d3f880 004e9000 00d3f8a4 0000004e
[18207.813143] 9fe0: 004e918c bec256b0 b6df990d b6df91f6 00010030 ffffffff
[18207.819766] CPU3: stopping
[18207.822484] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.5.0-sunxi #trunk.034
[18207.829530] Hardware name: Allwinner sun8i Family
[18207.834243] [<c010db0d>] (unwind_backtrace) from [<c010a139>] (show_stack+0x11/0x14)
[18207.841992] [<c010a139>] (show_stack) from [<c0962e6b>] (dump_stack+0x6f/0x7c)
[18207.849221] [<c0962e6b>] (dump_stack) from [<c010ca33>] (handle_IPI+0x293/0x2bc)
[18207.856626] [<c010ca33>] (handle_IPI) from [<c05e3345>] (gic_handle_irq+0x69/0x6c)
[18207.864203] [<c05e3345>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0x94)
[18207.871685] Exception stack(0xcf923f58 to 0xcf923fa0)
[18207.876737] 3f40:                      00000000 00a95dd8
[18207.884918] 3f60: cfd71fb4 c0116341 ffffe000 c0f04f68 c0f04fb0 00000008 c0f04f48 00000000
[18207.893099] 3f80: c0ec88f0 00000000 c0f03d00 cf923fa8 c01079bf c01079c0 400f0033 ffffffff
[18207.901282] [<c0101ae5>] (__irq_svc) from [<c01079c0>] (arch_cpu_idle+0x28/0x2c)
[18207.908687] [<c01079c0>] (arch_cpu_idle) from [<c014033f>] (do_idle+0x16b/0x1e8)

U-Boot SPL 2019.04-armbian (Jul 06 2019 — 00:26:54 +0200)

As a result, the only solution to this issue is the physical on/off on
target (remove then insert power cable (!))

Configuration is … (after reboot)

root@srv-orangepir1-140:~# uname -a                                                 
Linux srv-orangepir1-140 5.5.0-sunxi #trunk.034 SMP Mon Feb 3 08:38:40 CET 2020 armv7l GNU/Linux                        
root@srv-orangepir1-140:~# cat /etc/debian_version                                           
10.3                                                              
root@srv-orangepir1-140:~# grep -iR ^Deb /etc/apt                                            
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free        
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free              
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free         
/etc/apt/sources.list.d/armbian_apt_v_10_buster.list:deb http://apt.armbian.com buster main buster-utils buster-desktop                
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free             
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free         

root@srv-orangepir1-140:~# grep -iR ^P /etc/apt/preferences.d/
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster/updates
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 920
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-update
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 910
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 900
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-backports
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=stretch
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 400
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=testing
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: *
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=unstable
/etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Package: elogind
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin: release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Package: dhcpcd5
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin: release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Package: systemd
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin: release *
/etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_armbian_buster.pref:Package: hostapd
/etc/apt/preferences.d/preferences_armbian_buster.pref:Pin: origin «apt.armbian.com»
/etc/apt/preferences.d/preferences_armbian_buster.pref:Pin-Priority: -1
/etc/apt/preferences.d/preferences_armbian_buster.pref:Package: *
/etc/apt/preferences.d/preferences_armbian_buster.pref:Pin: origin «apt.armbian.com»
/etc/apt/preferences.d/preferences_armbian_buster.pref:Pin-Priority: 500
root@srv-orangepir1-140:~#

root@srv-orangepir1-140:~# dpkg -l |grep linux-image
ii  linux-image-dev-sunxi        20.05.0-trunk.034 armhf     Linux kernel, version 5.5.0-sunxi
ii  linux-image-next-sunxi       5.92              armhf     Linux kernel, version 4.19.62-sunxi
root@srv-orangepir1-140:~#

• • #1

  Jernej,

  I have a problem with odroid emmc on the pineH64. It gives this message during boot: sunxi-mmc 4022000.mmc: data error, sending stop command

  I see you fixed it for the Tanix T6 with this patch:

  Content embedded from external sources will not be displayed without your consent.

  Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

  But I don’t find this patch in your LibreElec patches for Allwinner H6, only this one: LibreELEC.tv/13-Tanix-TX6.patch at master · LibreELEC/LibreELEC.tv · GitHub

  The LE patches are only patches for the dts of the Tanix TX6, does this mean if I apply these patches in the pineH64 dts, the board will boot from emmc? Probably it’s a better fix that enables the HS DDR mode?

• • Official Post

  • #2

  I see you fixed it for the Tanix T6 with this patch:

  This is not a fix but workaround. Consequently, it was later removed when I found a proper solution for Tanix TX6.

  The LE patches are only patches for the dts of the Tanix TX6, does this mean if I apply these patches in the pineH64 dts, the board will boot from emmc? Probably it’s a better fix that enables the HS DDR mode?

  Yes, same approach should work for PineH64 too, just make sure that you properly specify regulators. This was main issue with Tanix TX6.

• • #3

  Can I find somewhere some documentation how to properly specify regulators? Is it related to the type of eemc or the size or the board?

• • Official Post

  • #4

  Documentation for device tree files is in Documentation/devicetree/bindings/regulator/ in Linux source. You should also consult PneH64 schematic.

• • #5

  Can I find somewhere some documentation how to properly specify regulators? Is it related to the type of eemc or the size or the board?

  Dear Roel,

  Could you apply below in your DTS file then convert it to DTB

  [email protected] {

  …….

  mmc-hs200-1_8v;

  mmc-hs400-1_8v;

  mmc-hs400-enhanced-strobe;

  }

  * Ready DTS and DTB in attachments.

• • #6

  genidy.m

  Thanks for the DTS patch. I was invetsigating the pind-H64 regulators, but it seems everything was already implemented in the dts. So the patch of Jernej for the Tanix-tx6 was not necesaary for the pine-h64.

  I implemented your patch in the sun50i-h6.dtsi; but for some reason I get a error message when I try to compile my dtb. It has nothing to do with the patch, probably there are some packages missing in my build environment. This evening I give it another try.

  Edit: Managed to build the dtb and it boots fine now. Thanks a lot for the patch!

• • Official Post

  • #7

  roel can you share diff between mainline and modified DT? You or genidy.m can send patch to upstream Linux for inclusion.

• • #8

  Jernej,

  herewith the diff.

• • Official Post

  • #9

  roel Are you using actual Odroid emmc module or that from Pine64. If it is that from Pine64 (ncembsf9-16g) then mmc-hs200-1_8v; should be enough. Can you test that? If it has some other eMMC chip, can you please post markings here?

• • #10

  jernej,

  it’s orange odroid 64GB emmc for odroid_N2. I just checked the odroid N2 dtb and indeed mmc-hs200-1_8v; should be enough. I can’t read what’s on the chip, the kids took my magnifier and I don’t find it. I will ask them tomorrow because they are already sleeping.

• • Official Post

  • #11

  roel No need to read markings, I got info that I need from Odroid page. In your case mmc-hs400-1_8v; would be more correct.

  Can you make read speed test with hdparm? I forgot exact command but I know you should make non-buffered test, otherwise read speed will be much too high.

• • #12

  jernej,

  No problem, will do it this evening.

• • #13

  jernej

  See attachement,

  I tested a 32GB Pine64 emmc and the 64GB odroid emmc. The result is really disappointing. The pine64 emmc is slightly faster but it’s not even 44MB/sec.

• • Official Post

  • #14

  ha, on Tanix TX6 I get without mmc-hs400-1_8v

  /dev/mmcblk1:
   HDIO_DRIVE_CMD(identify) failed: Invalid argument
   Timing buffered disk reads: 244 MB in  3.01 seconds =  81.15 MB/sec

  and with mmc-hs400-1_8v

  /dev/mmcblk1:
   HDIO_DRIVE_CMD(identify) failed: Invalid argument
   Timing buffered disk reads: 132 MB in  3.01 seconds =  43.92 MB/sec

  so this for some reason halves access read speed…

• • Official Post

  • #15

  I played a bit with various flags in DT but nothing helps to restore speed. I have a feeling that H6 mmc driver is not optimized but I have no idea about it. Since it works for you I won’t spend much time on it for now. Anyway, PR for PineH64 eMMC support would be welcome. If you don’t want to do it, I can take a shoot sometime in future.

  EDIT: So I did same speed on Android where I got ~130 MiB/s so definitely driver issue.
• • #16

  jernej

  I want to do a PR; I only never done it before, so I have to find out how to do it first.

• • #17

  genidy.m

  Thanks for the DTS patch. I was invetsigating the pind-H64 regulators, but it seems everything was already implemented in the dts. So the patch of Jernej for the Tanix-tx6 was not necesaary for the pine-h64.

  I implemented your patch in the sun50i-h6.dtsi; but for some reason I get a error message when I try to compile my dtb. It has nothing to do with the patch, probably there are some packages missing in my build environment. This evening I give it another try.

  Edit: Managed to build the dtb and it boots fine now. Thanks a lot for the patch!

  Display More

  roel

  You are welcome, i faced this issue before and found the solution in armbian forum for your board, worked for me too, for my box «mmc-hs200-1_8v» is enough as «sunvell Q+» had slow emmc, also extracted the DTB from original android OS and found that it use same entries for emmc.

  *posted here:

  How helpful will this be to getting LibreELEC on allwinner android boxes?