ESPRESSObin non more booting SATA after update Kernel 5.0.11

[mauiwowie42]

Reading more closely through my logs you can see <linux/phy/phy.h> is actually failing to power on the device at all and it occurs right after the Marvell XOR driver is loaded after pcie is initialized after the Block Layer SCSI Generic driver is loaded after the Linux SCSI subsystem is initialized.

[ 0.418797] SCSI subsystem initialized
...
2.802484] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
...
[ 3.101118] mv_xor d0060900.xor: Marvell shared XOR driver
[ 3.161135] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 3.231083] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 3.239264] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 3.247052] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 3.253908] phy phy-d0018300.phy.2: phy poweron failed --> -1
[ 3.259781] ahci-mvebu: probe of d00e0000.sata failed with error -1

This doesn't quite look like a problem with AHCI-MVEBU because it's actually the standard Linux Phy driver that seems to be failing even though it has the right address

https://cateee.net/lkddb/web-lkddb/AHCI_MVEBU.html

ahci-mvebu: https://github.com/torvalds/linux/blob/ ... ci_mvebu.c

Block Layer SCSI Generic driver: https://github.com/spotify/linux/blob/m ... lock/bsg.c

ahci: https://github.com/torvalds/linux/blob/ ... ata/ahci.h

phy.h: https://github.com/torvalds/linux/blob/ ... /phy/phy.h

phy driver core: https://github.com/torvalds/linux/blob/ ... phy-core.c

[mauiwowie42]

After reading

https://lore.kernel.org/linux-arm-kerne ... ner.com/T/

and

https://forum.armbian.com/topic/8447-up ... s-invalid/

it seems this is possibly a problem with the 17.10.x u-boot and a prebuilt armada-18.12.x does not seem to be available. Tomorrow I will try to build my own newest updated version of u-boot from

https://github.com/MarvellEmbeddedProce ... mada-18.12

and we'll see how it goes. This looks like it could it could be the case per the first link as it stated that the latest SMC calls which are responsible for powering on the device are only available for the latest u-boot. I have a v7 and mine shipped with U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800) which is even older than the user who initiated that first thread. This seems to be because Globalscale did not release 18.x.x u-boot for v7 boards until December-ish due to some sort of difference with DDR4 and you can see that those SMC calls being referred to (as well as the entire phy-mvebu-a3700-comphy.c) was committed on Jan. 8

https://github.com/torvalds/linux/commi ... ca1de931ed

what's notable to me though is that commit and driver were added before 5.0.11-1-ARCH was released yet it still works even on my much older u-boot.... So what about the jump to 5.1.16-1-ARCH breaks it when it should include the same calls made to enable and use sata devices?

https://github.com/torvalds/linux/commi ... cc9ce1984a

This is a commit in February to phy-mvebu-sata.c that could possibly be relevant

[Sergeanter]

This has been solved by flashing uboot 18.12 from armbian
https://archlinuxarm.org/forum/viewtopic.php?f=65&t=13659#p62068