by summers » Sun Feb 18, 2018 2:00 pm
OK its definitly the mainline kernel.
Reinstalled completely clean ArchLinuxARM-odroid-c2-latest.tar.gz.
The odroid-c2 was running fine on the 3.14 kernel, I updated to mainline:
$this->bbcode_second_pass_code('', 'pacman -R uboot-odroid-c2
pacman -S uboot-odroid-c2-mainline linux-aarch64
systemctl reboot')
Hardware wasn't touched physically during this - so can't have created a bad connection.
On reboot started getting the CRC errors again.
Lets see whats useful in dmesg:
$this->bbcode_second_pass_code('', '
[ 1.774051] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
[ 2.163204] meson-gx-mmc d0072000.mmc: Got CD GPIO
[ 2.707512] mmc0: new HS200 MMC card at address 0001
[ 2.707953] mmcblk0: mmc0:0001 8GME4R 7.28 GiB
[ 2.711495] mmcblk0boot0: mmc0:0001 8GME4R partition 1 4.00 MiB
[ 2.717359] mmcblk0boot1: mmc0:0001 8GME4R partition 2 4.00 MiB
[ 2.723176] mmcblk0rpmb: mmc0:0001 8GME4R partition 3 512 KiB, chardev (239:0)
[ 2.730904] mmcblk0: p1
[ 3.086087] mmcblk0: response CRC error sending r/w cmd command, card status 0xd00
[ 8.548473] print_req_error: I/O error, dev mmcblk0, sector 4458496
[ 13.194033] print_req_error: I/O error, dev mmcblk0, sector 2048
[ 13.199970] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write
')
Can't find anything useful in /sys.
I'll leave the odroid up for a bit in case people have questions - but can't do much on it as the root file system is mounted read only. So the *only* way forward is for me to reimage the OS on my desktop ...
Last edited by
summers on Sun Feb 18, 2018 2:58 pm, edited 1 time in total.