EdgeV no hdmi output

Hi guys,
So i just recieved my EdgeV last weekend, replaced the android sitting in the EMMC with this
official image Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V2019011.
So far so good.
But then i noticed the image started installing updates in the background…
Can 't remember the exact process name, but i noticed because i was trying to install some packages and that process grabbed the lock on apt…
I was quite surprised, as i have been playing with all flavors of linux distributions for 20years and never a system auto updated itself without at least prompting.

Well the real issue started after the next reboot. I lost video output on my 4k screen.
Also tried a 1080p tv, same result.
The system is well running, i can ssh in.
Also tried to apt update && apt upgrade, did not helped.

Any idea or hint from there ?

Hello, a shot in the dark…
After the system is booted, have you tried Ctrl+F5, Ctrl+F6, or Ctrl+F7 to see if the display will come up?

Yeap, i tried.
I can provide all the log you need to put some more light on the issue.

EDIT:
It seams something went wrong with the EMMC block device.
I was trying things, and the root partition just got corrupted, remounted itself RO,
tried to fix but it reached a point of no return… dmesg is full of IO errors.
Tomorrow, gonna clear the emmc, and reburn the image

Can you try this command to disable the update?

$ sudo rm -rf /etc/apt/apt.conf.d/50unattended-upgrades
$ sudo reboot

Thanks.

Ok, i might have find the issue, it looks like i got an issue with the EMMC.
As soon as i do some quite heaving writes on the filesystem the kernel keep reporting I/O errors

[21472.871831] mmcblk1: error -84 transferring data, sector 11919360, nr 760, cmd response 0x900, card status 0xd00
[21472.872967] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writing to inode 516193 (offset 0 size 389120 starting block 1490015)
[21481.287005] mmcblk1: error -84 transferring data, sector 12055552, nr 1024, cmd response 0x900, card status 0xd00
[21481.287951] blk_update_request: 173 callbacks suppressed
[21481.287956] blk_update_request: I/O error, dev mmcblk1, sector 12055552
[21481.288549] blk_update_request: I/O error, dev mmcblk1, sector 12055560
[21481.289130] blk_update_request: I/O error, dev mmcblk1, sector 12055568
[21481.289722] blk_update_request: I/O error, dev mmcblk1, sector 12055576
[21481.290313] blk_update_request: I/O error, dev mmcblk1, sector 12055584
[21481.290905] blk_update_request: I/O error, dev mmcblk1, sector 12055592
[21481.291531] blk_update_request: I/O error, dev mmcblk1, sector 12055600
[21481.292126] blk_update_request: I/O error, dev mmcblk1, sector 12055608
[21481.292718] blk_update_request: I/O error, dev mmcblk1, sector 12055616
[21481.293299] blk_update_request: I/O error, dev mmcblk1, sector 12055624
[21481.294202] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writing to inode 516722 (offset 0 size 8388608 starting block 1507072)
[21481.294211] buffer_io_error: 173 callbacks suppressed
[21481.294218] Buffer I/O error on device mmcblk1p7, logical block 1474048
[21481.294813] Buffer I/O error on device mmcblk1p7, logical block 1474049
[21481.295433] Buffer I/O error on device mmcblk1p7, logical block 1474050
[21481.296015] Buffer I/O error on device mmcblk1p7, logical block 1474051
[21481.296605] Buffer I/O error on device mmcblk1p7, logical block 1474052
[21481.297193] Buffer I/O error on device mmcblk1p7, logical block 1474053
[21481.297782] Buffer I/O error on device mmcblk1p7, logical block 1474054
[21481.298360] Buffer I/O error on device mmcblk1p7, logical block 1474055
[21481.298950] Buffer I/O error on device mmcblk1p7, logical block 1474056
[21481.299563] Buffer I/O error on device mmcblk1p7, logical block 1474057
[21510.614675] mmcblk1: error -84 transferring data, sector 3770896, nr 168, cmd response 0x900, card status 0xd00
[21510.615582] blk_update_request: 118 callbacks suppressed
[21510.615587] blk_update_request: I/O error, dev mmcblk1, sector 3770896
[21510.616169] blk_update_request: I/O error, dev mmcblk1, sector 3770904
[21510.616782] blk_update_request: I/O error, dev mmcblk1, sector 3770912
[21510.617364] blk_update_request: I/O error, dev mmcblk1, sector 3770920
[21510.617943] blk_update_request: I/O error, dev mmcblk1, sector 3770928
[21510.618522] blk_update_request: I/O error, dev mmcblk1, sector 3770936
[21510.619100] blk_update_request: I/O error, dev mmcblk1, sector 3770944
[21510.619678] blk_update_request: I/O error, dev mmcblk1, sector 3770952
[21510.620256] blk_update_request: I/O error, dev mmcblk1, sector 3770960
[21510.620858] blk_update_request: I/O error, dev mmcblk1, sector 3770968
[21510.621507] Aborting journal on device mmcblk1p7-8.
[21510.623382] EXT4-fs error (device mmcblk1p7): ext4_journal_check_start:56: Detected aborted journal
[21510.624203] EXT4-fs (mmcblk1p7): Remounting filesystem read-only
[21510.625222] EXT4-fs error (device mmcblk1p7): ext4_journal_check_start:56: Detected aborted journal

I start thinking i ain’t got no luck with my board…
Gonna try to boot from a sdcard and detect the bad sectors on the EMMC…
And from there probably request a replacement of the board

EDIT: thanks for the tips about the auto upgrade

So, i have contacted Khadas support, and they suggested to try with an android image.
And indeed the EMMC did not reported any error during a copy of a 5.5G file.
I double checked the chksum of the file i copied and it matched.
The rate of the copy was far from exceptional as it was at around 2MB/s.
i still got to do the same over ethernet.

But still, this bring the question why the linux kernel is reporting those writes errors ?

I also noticed that cfdisk with in the ubuntu image reported a weard partition table
The first partition start sector was after the end sector, and thus ended up with a partition size in the Exabyte range
But partition table reported by fdisk was correct, just no fsType set on the partition.
So i m not sure what to do with that information.

Any help to try figuring this one out is welcome .

Hello @BGillissen

So the image you used to test is Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V2019011?

Can you provide your operations to us? So that we can try to reproduce this issue?

So the Android image works well when copy files? Which android version you use to test?

@Frank Please follow up this issue.

Hi, so the Android i tested is Edge_Nougat_V190624.

To burn the images i use the USB-C cable technique.
3 fast push on the function button whezn i power it on.
Load the firmware in to AndroidTool (RKDevTool v2.65), Erase Flash, and finally Upgrade.
Once done, i unplug it from the data port, and then power it up using the power usb-c port (the one conflicting with the case).

I start thinking maybe the emmc is getting mutch more hoter when using ubuntu/debian because i can reach mutch more faster write speed, than with in android (maxed at 7MB/s with the ssh server i installed, I should have create another copy of that file locally
You are correct about the Ubuntu image.
The emmc errors appears if i :
scp a file in,
try to upgarde,
DD if=/dev/urandom of=~/test.rnd bs=1M count=3000 iflag=fullblock oflag=fullblock

EDIT: i also noticed the HDMI port is really picky, it only catch my display once every 5 boots i would say
Also to prevent the auto update i disabled the unattended-upgrade service and lightdm aswell.

@BGillissen Can you tell me which Ubuntu firmware you used ,then I can try to test with scp .

Sure, i used the Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V2019011

@BGillissen
I try it with you command line

root@Khadas:~# dd if=/dev/urandom of=~/test.rnd bs=1M count=3000 iflag=fullblock

3000+0 records in
3000+0 records out
3145728000 bytes (3.1 GB, 2.9 GiB) copied, 324.186 s, 9.7 MB/s
root@Khadas:~# 
root@Khadas:~# ls
test.rnd
root@Khadas:~#

It looks all right. So can you try again.If the problem arises again, provide us with the corresponding log information to facilitate our analysis of the problem.

@BGillissen . Can you tell me that What does try to upgrade mean? I’m not just going to get to this point. What do I do?

apt update && apt upgrade.

khadas@Khadas:~$ dd if=/dev/urandom of=~/test.rnd bs=1M count=3000 iflag=fullblock
3000+0 records in
3000+0 records out
3145728000 bytes (3.1 GB, 2.9 GiB) copied, 313.225 s, 10.0 MB/s
khadas@Khadas:~$ ls -lah test.rnd
-rw-rw-r-- 1 khadas khadas 3.0G Aug 16 04:08 test.rnd

it finished ok but those appeared in dmesg while doing it

[125709.400217] mmcblk1: error -84 transferring data, sector 6641664, nr 1024, cmd response 0x900, card status 0xd00
[125709.401157] blk_update_request: 118 callbacks suppressed
[125709.401169] blk_update_request: I/O error, dev mmcblk1, sector 6641664
[125709.401770] blk_update_request: I/O error, dev mmcblk1, sector 6641672
[125709.402370] blk_update_request: I/O error, dev mmcblk1, sector 6641680
[125709.402969] blk_update_request: I/O error, dev mmcblk1, sector 6641688
[125709.403569] blk_update_request: I/O error, dev mmcblk1, sector 6641696
[125709.404252] blk_update_request: I/O error, dev mmcblk1, sector 6641704
[125709.404854] blk_update_request: I/O error, dev mmcblk1, sector 6641712
[125709.405453] blk_update_request: I/O error, dev mmcblk1, sector 6641720
[125709.406052] blk_update_request: I/O error, dev mmcblk1, sector 6641728
[125709.406651] blk_update_request: I/O error, dev mmcblk1, sector 6641736
[125709.412013] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writing to inode 64973 (offset 58720256 size 8388608 starting block 830464)
[125709.412037] buffer_io_error: 246 callbacks suppressed
[125709.412051] Buffer I/O error on device mmcblk1p7, logical block 797440
[125709.412748] Buffer I/O error on device mmcblk1p7, logical block 797441
[125709.413342] Buffer I/O error on device mmcblk1p7, logical block 797442
[125709.413934] Buffer I/O error on device mmcblk1p7, logical block 797443
[125709.414525] Buffer I/O error on device mmcblk1p7, logical block 797444
[125709.415116] Buffer I/O error on device mmcblk1p7, logical block 797445
[125709.415707] Buffer I/O error on device mmcblk1p7, logical block 797446
[125709.416336] Buffer I/O error on device mmcblk1p7, logical block 797447
[125709.416929] Buffer I/O error on device mmcblk1p7, logical block 797448
[125709.417521] Buffer I/O error on device mmcblk1p7, logical block 797449
[125711.299697] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125715.275935] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125721.986756] wl_run_escan: LEGACY_SCAN sync ID: 1998, bssidx: 0
[125745.620032] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125750.630690] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125780.972329] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125785.017503] wl_run_escan: LEGACY_SCAN sync ID: 1999, bssidx: 0
[125787.012389] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125790.939186] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125821.281944] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125826.282027] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125847.989651] wl_run_escan: LEGACY_SCAN sync ID: 2000, bssidx: 0
[125847.992211] EVENT_LOG_HDR[0xbe]: Set: 0x00000000 length = 1028
[125856.618764] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125861.649464] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125893.662018] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125897.516117] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
[125911.051753] wl_run_escan: LEGACY_SCAN sync ID: 2001, bssidx: 0

With scp

> khadas@Khadas:~$ logger START && scp root@10.76.1.15:/stuff/news/test.rnd ~/test2.rnd && logger STOP
> The authenticity of host '10.76.1.15 (10.76.1.15)' can't be established.
> ECDSA key fingerprint is SHA256:0VZUfBd+c36ql6tAFGab2sKBIZ6dga3gH7QoFQuB4uM.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added '10.76.1.15' (ECDSA) to the list of known hosts.
> Password:
> test.rnd                                                                                                                                   100% 3000MB  60.1MB/s   00:49
> khadas@Khadas:~$

Aug 16 04:17:21 localhost khadas: START
Aug 16 04:17:35 localhost kernel: [126522.271871] mmcblk1: error -84 transferring data, sector 13318144, nr 1024, cmd resp                                                   onse 0x900, card status 0xd00
Aug 16 04:17:35 localhost kernel: [126522.273368] blk_update_request: 246 callbacks suppressed
Aug 16 04:17:35 localhost kernel: [126522.273374] blk_update_request: I/O error, dev mmcblk1, sector 13318144
Aug 16 04:17:35 localhost kernel: [126522.274301] blk_update_request: I/O error, dev mmcblk1, sector 13318152
Aug 16 04:17:35 localhost kernel: [126522.275241] blk_update_request: I/O error, dev mmcblk1, sector 13318160
Aug 16 04:17:35 localhost kernel: [126522.276123] blk_update_request: I/O error, dev mmcblk1, sector 13318168
Aug 16 04:17:35 localhost kernel: [126522.277167] blk_update_request: I/O error, dev mmcblk1, sector 13318176
Aug 16 04:17:35 localhost kernel: [126522.278244] blk_update_request: I/O error, dev mmcblk1, sector 13318184
Aug 16 04:17:35 localhost kernel: [126522.279200] blk_update_request: I/O error, dev mmcblk1, sector 13318192
Aug 16 04:17:35 localhost kernel: [126522.280351] blk_update_request: I/O error, dev mmcblk1, sector 13318200
Aug 16 04:17:35 localhost kernel: [126522.281777] blk_update_request: I/O error, dev mmcblk1, sector 13318208
Aug 16 04:17:35 localhost kernel: [126522.282953] blk_update_request: I/O error, dev mmcblk1, sector 13318216
Aug 16 04:17:35 localhost kernel: [126522.289198] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writi                                                   ng to inode 64974 (offset 0 size 0 starting block 1665024)
Aug 16 04:17:35 localhost kernel: [126522.289215] buffer_io_error: 502 callbacks suppressed
Aug 16 04:17:35 localhost kernel: [126522.289223] Buffer I/O error on device mmcblk1p7, logical block 1632000
Aug 16 04:17:35 localhost kernel: [126522.290242] Buffer I/O error on device mmcblk1p7, logical block 1632001
Aug 16 04:17:35 localhost kernel: [126522.291171] Buffer I/O error on device mmcblk1p7, logical block 1632002
Aug 16 04:17:35 localhost kernel: [126522.292063] Buffer I/O error on device mmcblk1p7, logical block 1632003
Aug 16 04:17:35 localhost kernel: [126522.293734] Buffer I/O error on device mmcblk1p7, logical block 1632004
Aug 16 04:17:35 localhost kernel: [126522.294878] Buffer I/O error on device mmcblk1p7, logical block 1632005
Aug 16 04:17:35 localhost kernel: [126522.295755] Buffer I/O error on device mmcblk1p7, logical block 1632006
Aug 16 04:17:35 localhost kernel: [126522.296739] Buffer I/O error on device mmcblk1p7, logical block 1632007
Aug 16 04:17:35 localhost kernel: [126522.297809] Buffer I/O error on device mmcblk1p7, logical block 1632008
Aug 16 04:17:35 localhost kernel: [126522.299122] Buffer I/O error on device mmcblk1p7, logical block 1632009
Aug 16 04:17:51 localhost kernel: [126538.664772] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:17:54 localhost kernel: [126541.067770] wl_run_escan: LEGACY_SCAN sync ID: 2011, bssidx: 0
Aug 16 04:17:55 localhost kernel: [126542.615116] mmcblk1: error -84 transferring data, sector 15840256, nr 1024, cmd resp                                                   onse 0x900, card status 0xd00
Aug 16 04:17:55 localhost kernel: [126542.616060] blk_update_request: 118 callbacks suppressed
Aug 16 04:17:55 localhost kernel: [126542.616066] blk_update_request: I/O error, dev mmcblk1, sector 15840256
Aug 16 04:17:55 localhost kernel: [126542.616660] blk_update_request: I/O error, dev mmcblk1, sector 15840264
Aug 16 04:17:55 localhost kernel: [126542.617315] blk_update_request: I/O error, dev mmcblk1, sector 15840272
Aug 16 04:17:55 localhost kernel: [126542.617915] blk_update_request: I/O error, dev mmcblk1, sector 15840280
Aug 16 04:17:55 localhost kernel: [126542.618510] blk_update_request: I/O error, dev mmcblk1, sector 15840288
Aug 16 04:17:55 localhost kernel: [126542.619106] blk_update_request: I/O error, dev mmcblk1, sector 15840296
Aug 16 04:17:55 localhost kernel: [126542.619700] blk_update_request: I/O error, dev mmcblk1, sector 15840304
Aug 16 04:17:55 localhost kernel: [126542.620292] blk_update_request: I/O error, dev mmcblk1, sector 15840312
Aug 16 04:17:55 localhost kernel: [126542.620885] blk_update_request: I/O error, dev mmcblk1, sector 15840320
Aug 16 04:17:55 localhost kernel: [126542.621524] blk_update_request: I/O error, dev mmcblk1, sector 15840328
Aug 16 04:17:55 localhost kernel: [126542.622455] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writi                                                   ng to inode 64974 (offset 1291845632 size 8388608 starting block 1980160)
Aug 16 04:17:55 localhost kernel: [126542.622464] buffer_io_error: 246 callbacks suppressed
Aug 16 04:17:55 localhost kernel: [126542.622471] Buffer I/O error on device mmcblk1p7, logical block 1947136
Aug 16 04:17:55 localhost kernel: [126542.623071] Buffer I/O error on device mmcblk1p7, logical block 1947137
Aug 16 04:17:55 localhost kernel: [126542.623663] Buffer I/O error on device mmcblk1p7, logical block 1947138
Aug 16 04:17:55 localhost kernel: [126542.624254] Buffer I/O error on device mmcblk1p7, logical block 1947139
Aug 16 04:17:55 localhost kernel: [126542.624845] Buffer I/O error on device mmcblk1p7, logical block 1947140
Aug 16 04:17:55 localhost kernel: [126542.625476] Buffer I/O error on device mmcblk1p7, logical block 1947141
Aug 16 04:17:55 localhost kernel: [126542.626075] Buffer I/O error on device mmcblk1p7, logical block 1947142
Aug 16 04:17:55 localhost kernel: [126542.626667] Buffer I/O error on device mmcblk1p7, logical block 1947143
Aug 16 04:17:55 localhost kernel: [126542.627259] Buffer I/O error on device mmcblk1p7, logical block 1947144
Aug 16 04:17:55 localhost kernel: [126542.627851] Buffer I/O error on device mmcblk1p7, logical block 1947145
Aug 16 04:17:57 localhost kernel: [126543.763779] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:17:58 localhost kernel: [126545.325783] mmcblk1: error -84 transferring data, sector 16187392, nr 1024, cmd resp                                                   onse 0x900, card status 0xd00
Aug 16 04:17:58 localhost kernel: [126545.331198] EXT4-fs warning (device mmcblk1p7): ext4_end_bio:330: I/O error -5 writi                                                   ng to inode 64974 (offset 1476395008 size 8388608 starting block 2023680)
Aug 16 04:18:02 localhost kernel: [126549.118909] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:07 localhost kernel: [126554.033279] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:12 localhost kernel: [126558.801396] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:16 localhost kernel: [126563.668703] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:21 localhost khadas: STOP
Aug 16 04:18:22 localhost kernel: [126568.958377] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:28 localhost kernel: [126574.986047] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8
Aug 16 04:18:33 localhost kernel: [126579.786822] JBD2: Detected IO errors while flushing file data on mmcblk1p7-8

And md5Sum does not match

stuff /stuff/news # md5sum test.rnd
83c163040b13d8f28449202d7873313a test.rnd

khadas@Khadas:~$ md5sum test2.rnd
dcc0fc084069cd40199c488a9c291a42 test2.rnd

@BGillissen My test results are different from yours.

  1. This is my dd test and log info.
khadas# dd if=/dev/urandom of=~/test.rnd bs=1M count=3000 iflag=fullblock
3000+0 records in
3000+0 records out
3145728000 bytes (3.1 GB, 2.9 GiB) copied, 305.14 s, 10.3 MB/s

And there is the log info wth dmesg

[    8.384963] ttyS0 - failed to request DMA, use interrupt mode
[   10.636773] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   11.084113] wl_run_escan: LEGACY_SCAN sync ID: 1, bssidx: 0
[   11.214196] tty_port_close_start: tty->count = 1 port count = 2.
[   34.118573] wl_run_escan: LEGACY_SCAN sync ID: 2, bssidx: 0
[   67.136443] wl_run_escan: LEGACY_SCAN sync ID: 3, bssidx: 0
[  110.147744] wl_run_escan: LEGACY_SCAN sync ID: 4, bssidx: 0
[  111.381737] EVENT_LOG_HDR[0x0]: Set: 0x00000000 length = 1028
[  163.158855] wl_run_escan: LEGACY_SCAN sync ID: 5, bssidx: 0
[  226.055738] wl_run_escan: LEGACY_SCAN sync ID: 6, bssidx: 0
[  289.095917] wl_run_escan: LEGACY_SCAN sync ID: 7, bssidx: 0
[  352.064220] wl_run_escan: LEGACY_SCAN sync ID: 8, bssidx: 0
  1. Then I test with scp
    This is my test command
khadas#scp frank@192.168.1.117:/home/frank/work/firmware/EDGE/Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V20190116.img ./img1
frank@192.168.1.117's password: 
Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_ 100% 3646MB  52.9MB/s   01:08
khadas#scp frank@192.168.1.117:/home/frank/work/firmware/EDGE/Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V20190116.img ./img2
frank@192.168.1.117's password: 
Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_ 100% 3646MB  54.0MB/s   01:u6307 
khadas# ls
img1  img2

And then the md5 info is :

khadas# md5sum img1
abd82d24ee9c24627431d8228aeedd67  img1
khadas# md5sum img2
abd82d24ee9c24627431d8228aeedd67  img2

The dmesg info :

    7.979873] P2P interface registered
[    7.979893] wl_cfgp2p_add_p2p_disc_if: wdev: ffffffc0ed076000, wdev->net:           (null)
[    8.002826] WLC_E_IF: NO_IF set, event Ignored
[    8.004711] P2P interface started
[    8.029420] wl_run_escan: LEGACY_SCAN sync ID: 0, bssidx: 0
[    8.230146] [BT_RFKILL]: rfkill_rk_set_power: set bt wake_host pin output high!
[    8.276377] [BT_RFKILL]: ENABLE UART_RTS
[    8.380233] [BT_RFKILL]: DISABLE UART_RTS
[    8.380294] [BT_RFKILL]: bt turn on power
[    8.384963] ttyS0 - failed to request DMA, use interrupt mode
[   10.636773] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   11.084113] wl_run_escan: LEGACY_SCAN sync ID: 1, bssidx: 0
[   11.214196] tty_port_close_start: tty->count = 1 port count = 2.
[   34.118573] wl_run_escan: LEGACY_SCAN sync ID: 2, bssidx: 0
[   67.136443] wl_run_escan: LEGACY_SCAN sync ID: 3, bssidx: 0
[  110.147744] wl_run_escan: LEGACY_SCAN sync ID: 4, bssidx: 0
[  111.381737] EVENT_LOG_HDR[0x0]: Set: 0x00000000 length = 1028
[  163.158855] wl_run_escan: LEGACY_SCAN sync ID: 5, bssidx: 0
[  226.055738] wl_run_escan: LEGACY_SCAN sync ID: 6, bssidx: 0
[  289.095917] wl_run_escan: LEGACY_SCAN sync ID: 7, bssidx: 0
[  352.064220] wl_run_escan: LEGACY_SCAN sync ID: 8, bssidx: 0
[  415.076015] wl_run_escan: LEGACY_SCAN sync ID: 9, bssidx: 0
[  478.059126] wl_run_escan: LEGACY_SCAN sync ID: 10, bssidx: 0
[  541.044213] wl_run_escan: LEGACY_SCAN sync ID: 11, bssidx: 0
[  604.025813] wl_run_escan: LEGACY_SCAN sync ID: 12, bssidx: 0
[  667.025507] wl_run_escan: LEGACY_SCAN sync ID: 13, bssidx: 0
[  730.014917] wl_run_escan: LEGACY_SCAN sync ID: 14, bssidx: 0
[  730.016522] EVENT_LOG_HDR[0x1]: Set: 0x00000000 length = 1028
[  793.143083] wl_run_escan: LEGACY_SCAN sync ID: 15, bssidx: 0
[  856.206867] wl_run_escan: LEGACY_SCAN sync ID: 16, bssidx: 0
[  919.171901] wl_run_escan: LEGACY_SCAN sync ID: 17, bssidx: 0
[  982.232297] wl_run_escan: LEGACY_SCAN sync ID: 18, bssidx: 0
[ 1045.226850] wl_run_escan: LEGACY_SCAN sync ID: 19, bssidx: 0
[ 1108.233212] wl_run_escan: LEGACY_SCAN sync ID: 20, bssidx: 0
[ 1171.197003] wl_run_escan: LEGACY_SCAN sync ID: 21, bssidx: 0
[ 1234.222535] wl_run_escan: LEGACY_SCAN sync ID: 22, bssidx: 0
[ 1297.198511] wl_run_escan: LEGACY_SCAN sync ID: 23, bssidx: 0
[ 1360.219755] EVENT_LOG_HDR[0x2]: Set: 0x00000000 length = 1028
[ 1360.219771] wl_run_escan: LEGACY_SCAN sync ID: 24, bssidx: 0

Ok, so do you agree with me something is probably wrong with the emmc on my board ?

We are using the same software, and end up with different results.

I understand well that with android those IO errors did not appeared, but the wirte rate was not the same either.
When i come back from work this evening, i will try a local copy with in android.

@BGillissen . I’m not sure if your EMMC is damaged. I suggest you that re-burn the firamware and try it again.I will continue testing .

Ok, will do.
It will only be for 8th time since i recieved it :wink:

1 Like

I reburned it with android, retried the copy of the test.rnd file; no errors detected and md5sum matched, max rate i could achieve was 30MB/s.

Then i reburned the Edge_Ubuntu-lxde-bionic_Linux-4.4_arm64_EMMC_V20190116 image.
And the I/O errors are still present, and md5sum does not match.

here is some infos about the system

khadas@Khadas:~$ sudo fdisk /dev/mmcblk1

Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/mmcblk1: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3E350000-0000-434A-8000-565200006D0B

Device          Start      End  Sectors Size Type
/dev/mmcblk1p1     64     8127     8064   4M unknown
/dev/mmcblk1p2  16384    24575     8192   4M unknown
/dev/mmcblk1p3  24576    32767     8192   4M unknown
/dev/mmcblk1p4  32768    40959     8192   4M unknown
/dev/mmcblk1p5  40960    73727    32768  16M unknown
/dev/mmcblk1p6  73728   262143   188416  92M unknown
/dev/mmcblk1p7 262144 61071326 60809183  29G unknown

Command (m for help):

khadas@Khadas:~$ uname -a
Linux Khadas 4.4.154 #1 SMP Wed Jan 16 16:03:58 CST 2019 aarch64 aarch64 aarch64 GNU/Linux
khadas@Khadas:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic
khadas@Khadas:~$

the full syslog of the last attempt: https://pastebin.com/Fd7h5Xz9

Any news on your end ?
Without solution from your part i ll have to request a refound.