ARM64 – Pi3 Still Very Unstable..

I have tried the latest 4.7-next patched kernel, from https://github.com/anholt/linux/tree/bcm2837-64-next

After some trials, I did manage to – just – get it to boot – after falling to an ’emergency console’, but the system is very unstable, with multiple recurring MMC errors..

.....
 Give root password for maintenance
 (or press Control-D to continue):
 Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
 [ 714.545569] mmc0: Timeout waiting for hardware interrupt.
 [ 715.484762] mmcblk0: error -110 transferring data, sector 1026056, nr 16, cmd response 0x900, card status 0xc00
 .........
 Fedora 24 (Twenty Four)
 Kernel 4.7.0-rc3-next-20160615 on an aarch64 (ttyS0)
 ..................

There appear to be two mmc drivers for the PI3 in the selection..

SDHCI platform support for the BCM2835 SD/MMC Controller
and
SDHCI support for the BCM2835 & iProc SD/MMC Controller

Selecting _both_ results in kernel boot with multiple mmc errors, and completes eventually, but is not stable..

Selecting just ‘SDHCI platform support for the BCM2835 SD/MMC Controller‘ gives boot fail with multiple repeating MMC errors..

........
 [ 21.995425] Waiting for root device /dev/mmcblk0p2...
 [ 22.787918] mmc0: problem reading SD Status register
 [ 22.923726] mmc0: error -84 whilst initialising SD card
 [ 27.649114] mmc0: error -84 whilst initialising SD card
 [ 32.397154] mmc0: error -84 whilst initialising SD card
 [ 37.129422] mmc0: error -84 whilst initialising SD card
 [ 41.861163] mmc0: error -84 whilst initialising SD card
 [ 46.581532] mmc0: error -84 whilst initialising SD card
 [ 51.313549] mmc0: error -84 whilst initialising SD card
 << repeated...>>

Selecting just ‘SDHCI support for the BCM2835 & iProc SD/MMC Controller‘ gives partial boot after an emergency console, but then repeated write failures…

 [ 2314.922231] systemd-journald[925]: Failed to write entry (27 items, 745 bytes), ignoring: Read-only file system
 [ 2315.139570] systemd-journald[925]: Failed to write entry (27 items, 749 bytes), ignoring: Read-only file system
 [ 2315.359321] systemd-journald[925]: Failed to write entry (27 items, 750 bytes), ignoring: Read-only file system
 [ 2315.577424] systemd-journald[925]: Failed to write entry (20 items, 618 bytes), ignoring: Read-only file system
 << repeated...>>

I returned to the relatively-stable 4.5.0+ kernel, but even this tombstones every so often, and usually has to be booted via the emergency console..

So – for the time being – I will wait until a more stable patched kernel is available..

Robert Gadsdon.   June 20, 2016.


Leave a Reply

Your email address will not be published. Required fields are marked *