Hi bodhi,
on my NSA320 (with your wheezy rootfs) since several weeks there is a 3.10.1 kernel running with
full ARCH patches for quite a while with superior performance,.. the ARCH guys also use
the Marvell Phy !!,.. I tested that because of my problems with the generic PHY documented in this forum,...
a quick comparison of the dmesg output shows, that you have
ata1: SATA link down (SStatus 0 SControl F300)
so maybe the disk is not initialized?? and your initramfs is not found and decompressed?
on my kernel there is
[ 8.544373] sata_mv sata_mv.0: version 1.28
[ 8.544435] sata_mv sata_mv.0: cannot get optional clkdev
[ 8.544529] sata_mv sata_mv.0: slots 32 ports 2
[ 8.546949] scsi0 : sata_mv
[ 8.547245] scsi1 : sata_mv
[ 8.547434] ata1: SATA max UDMA/133 irq 21
[ 8.547444] ata2: SATA max UDMA/133 irq 21
and later
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
my kernel command line is without label!!
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda2
and later
[ 7.961686] Trying to unpack rootfs image as initramfs...
[ 8.645701] 0x000001680000-0x000004640000 : "rootfs1"
[ 8.646306] 0x000005040000-0x000008000000 : "rootfs2"
and everything is fine,.. what is the version of your sata_mv??, on 3.10.1 it is still 1.28,
quite a while ago when I wrote setup routines for older marvel soc's there always was something
wrong with the memory adress of the sata port in the include definitions when the sata link did not come up,
but its hard to imagine that it has changed from 3.10.1 to 3.10.4,.. ??
best wishes pbg4
p.s. oops,.. I just realised that you have an usb attached rootfs and that my rootfs is attached via sata, so my comment is not fitting for your problem,.. but nevertheless the 3.10 mainline kernels are worth to try, my NSA320 has never been
so stable and performant,..
on my NSA320 (with your wheezy rootfs) since several weeks there is a 3.10.1 kernel running with
full ARCH patches for quite a while with superior performance,.. the ARCH guys also use
the Marvell Phy !!,.. I tested that because of my problems with the generic PHY documented in this forum,...
a quick comparison of the dmesg output shows, that you have
ata1: SATA link down (SStatus 0 SControl F300)
so maybe the disk is not initialized?? and your initramfs is not found and decompressed?
on my kernel there is
[ 8.544373] sata_mv sata_mv.0: version 1.28
[ 8.544435] sata_mv sata_mv.0: cannot get optional clkdev
[ 8.544529] sata_mv sata_mv.0: slots 32 ports 2
[ 8.546949] scsi0 : sata_mv
[ 8.547245] scsi1 : sata_mv
[ 8.547434] ata1: SATA max UDMA/133 irq 21
[ 8.547444] ata2: SATA max UDMA/133 irq 21
and later
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
my kernel command line is without label!!
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda2
and later
[ 7.961686] Trying to unpack rootfs image as initramfs...
[ 8.645701] 0x000001680000-0x000004640000 : "rootfs1"
[ 8.646306] 0x000005040000-0x000008000000 : "rootfs2"
and everything is fine,.. what is the version of your sata_mv??, on 3.10.1 it is still 1.28,
quite a while ago when I wrote setup routines for older marvel soc's there always was something
wrong with the memory adress of the sata port in the include definitions when the sata link did not come up,
but its hard to imagine that it has changed from 3.10.1 to 3.10.4,.. ??
best wishes pbg4
p.s. oops,.. I just realised that you have an usb attached rootfs and that my rootfs is attached via sata, so my comment is not fitting for your problem,.. but nevertheless the 3.10 mainline kernels are worth to try, my NSA320 has never been
so stable and performant,..