Debian on Synology RS816 (Armada 385)

Richard,

> Very happy to test anything you ask me to in the
> interest of achieving your goal and generally
> helping others get this box up and running.

Thanks :)

> I will see how "close to the wire" I am with my
> attempts to reduce size if too close I will drop
> my preferred option.

You could use Arch Linux approach. They compile everything in the kernel. And start with an empty initrd. But even that, it will get you to very close to 7MB (seen it first hand) so there will be no room for the initrd to grow..

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
I think I mentioned I am running my own fork of Arch Linux. The "Arch Way" is to compile anything that can be as a loadable module then on initrd creation they use hooks to probe only for the modules required to boot thereafter udev / kmod deal with the rest as the system comes up. The Arch mkinitcpio utility allows the user to add modules they might want during boot via a config file, an example being a video driver to bring up kms early in the boot process.

I am nearly at the end of the first build so we will see what we get but I may well need to research how Debian do things but my idea is initrd only contains enough to boot the filesystem but all modules are there as loadable after that point.

Richard,

> I think I mentioned I am running my own fork of
> Arch Linux. The "Arch Way" is to compile anything
> that can be as a loadable module then on initrd
> creation they use hooks to probe only for the
> modules required to boot thereafter udev / kmod
> deal with the rest as the system comes up. The
> Arch mkinitcpio utility allows the user to add
> modules they might want during boot via a config
> file, an example being a video driver to bring up
> kms early in the boot process.

Yes I do remember that. And I have not been up-to-date in Arch rootfs organization since many years so don't know much.

But I recall even the modules in the rootfs are compressed in /lib/modules/* . So seems like the modules are hooked only and initrd don't need to house the module binaries, therefore will not grow much later.

Arch Linux ARM recently added a bareboned initrd to their installation. It's a good move, because it solves many booting problems that we (Debian) don't need to worry about when we use root=LABEL=rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 05/17/2019 10:36PM by bodhi.

@bodhi
OK, so that didn't work! and I think I got myself mixed up in my post above.

Maybe I need a u-boot component terminology guide based on the results I'm seeing.

For u-boot
zImage is the equivalent of vmlinuz ?
uInitrd is the equvilent of initrd is the equivalent of initramfs ?
uImage is ?

EDIT
I meant my "small build" didn't work



Edited 1 time(s). Last edit at 05/17/2019 10:44PM by richjn.

Doh! I've overlooked this bootargs:

initrd=/boot/initrd.img-5.1.2-mvebu-tld-1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Richard,

Quote

zImage is the equivalent of vmlinuz ?
uInitrd is the equvilent of initrd is the equivalent of initramfs ?
uImage is ?

zImage is built in ./arch/arm/boot/
uInitrd is the initramfs with a u-boot header
uImage is vmlinuz with a u-boot header.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Richard,

bodhi Wrote:
-------------------------------------------------------
> Doh! I've overlooked this bootargs:
>
>

> initrd=/boot/initrd.img-5.1.2-mvebu-tld-1
>

So quoting myself above. You can already flash zImage and DTB. Delay the initrd loading until the kernel booted.

I'll change the envs to test that if you are not sure?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 05/17/2019 10:49PM by bodhi.

@bodhi

Quote

zImage is built in ./arch/arm/boot/
uInitrd is the initramfs with a u-boot header
uImage is vmlinuz with a u-boot header.

Thank you

@bodhi
If I am just adding the bootarg I can do that but give me 15 mins I have someone arriving to pick up some gear in a second. If it needs more (for the delay etc) then yes, please can you post an example.

Richard,

OK. Let me revise the envs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi

WIN :)

Guys arrived will post more ina minute

Richard,

Here is the modified envs (changes in bold).

setenv ipaddr 192.168.1.250
setenv serverip 192.168.1.2
setenv load_dtb_addr 0x1000000
setenv load_initrd_addr 0x3000000
setenv load_image_addr 0x02000000
setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage'
setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtb'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs initrd=/boot/initrd.img-5.1.2-mvebu-tld-1 rootdelay=20 $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_dtb; bootz $load_image_addr - $load_dtb_addr'
setenv bootcmd 'mw 0xf10a2620 0x251;mw 0xf10a2e20 0x251;usb xhciinit; run bootcmd_exec; run bootspi'

And of course, replace initrd.img-5.1.2-mvebu-tld-1 name with whatever name you have on your rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 05/17/2019 11:17PM by bodhi.

@bodhi
I'm booted in with the following;

setenv ipaddr 192.168.1.250
setenv serverip 192.168.1.2
setenv load_dtb_addr 0x1000000
setenv load_image_addr 0x02000000
setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage'
setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtb'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=20 initrd=/boot/initrd-img-5.1.3-rj $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; run load_dtb; bootz $load_image_addr $load_initrd_addr $load_dtb_addr'
setenv bootcmd 'run bootcmd_exec; run bootspi'

In addition to your version above I dropped;

setenv load_initrd_addr 0x3000000

Plus I dropped the memory holes and xhciinit so "setenv bootcmd" reads

setenv bootcmd 'run bootcmd_exec; run bootspi'

My initrd name is obviously different to yours too.

I will rerun and saveenv and post back in a minute

@bodhi
saveenv and reset works

Time to try and flash SPI ?
Do you want me to repeat the output you requested previously ?

I'm away for 30 mins but its time to celebrate I reckon!!

Richard,

> saveenv and reset works

> Time to try and flash SPI ?
> Do you want me to repeat the output you requested
> previously ?
>
> I'm away for 30 mins but its time to celebrate I
> reckon!!

Yes! open that shiraz bottle if you got one :)

Please redo the boot process with the new envs (if you have saved them before then do a printenv at u-boot prompt before continue booting ) and then the rest of other commands in Debian.

And post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
Put the shiraz away for a while!

I just got bitten by stock again even though I was super quick to pull the plug.

The issue arose when I aligned the differences in our two boot envs, there was nothing wrong with yours!, it was just I had left $load_initrd_addr and you had a "-" when I did this mine failed to boot because it appears if you don't have $load_initrd_addr then you need load_initrd_addr 0x3000000 which I had deleted from mine.

On one of the failed boots it jumped into stock (part way not full boot)

After correcting both of my errors boot start normally but rootfs is missing. I will boot from usb and see if the speed at which I pulled the plug means I can rescue it.

In the meantime can you send me a command to delete the synology mtd, I honestly don't want / care to run DSM on it again worst case I will have to tftp the files forever.

Rchard,

> Put the shiraz away for a while!
>
> I just got bitten by stock again even though I was
> super quick to pull the plug.
>
> The issue arose when I aligned the differences in
> our two boot envs, there was nothing wrong with
> yours!, it was just I had left $load_initrd_addr
> and you had a "-" when I did this mine failed to
> boot because it appears if you don't have
> $load_initrd_addr then you need load_initrd_addr
> 0x3000000 which I had deleted from mine.

No, we don't need load_initrd_addr, you were right to remove it.

We reply on the kernel bootargs initrd=/boot/initrd-img-5.1.3-rj to find where is initrd-img-5.1.3-rj

Quote

setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=20 initrd=/boot/initrd-img-5.1.3-rj $mtdparts earlyprintk=serial"'

And we reply on setenv initrd_high 0xffffffffto tell the kernel where to load and relocate initrd.

The bootz with - is to tell uboot that we are not booting with initrd.

Quote

setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_dtb; bootz $load_image_addr - $load_dtb_addr'

And if that's not enough, then we need initrd address. But we don't load initrd explicitly.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
I have rescued the system and will now work through your comments above and see if I can get it right this time.

The bit I don't understand was I had it working, must have made a mistake on final edit or something.

Back in a bit with hopefully better news.

Richard,

I think we need more than currently in the envs to make it work.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
I set rootdelay to 60 seconds just to give it loads of time to spin up but we end on a kernel panic

[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

I don't like to admit it but maybe in my rush to try this before my visitor arrived I booted from my previously save tftp settings not from the new ones but I was so sure I had used the new envs.

When I rescued my system the md's had all defaulted to /dev/125 etc rather than /dev/md0 etc I will go back and see if anything else changed which may be affecting things, failing which you may well be correct we need to do more in the envs.

@bodhi
Everything is ok in the rootfs which is good but no answers to be found there.

I tried using /dev/md0 in envs rather than rootfs LABEL but no change, same kernel panic.

Looks like I owe you and everyone else an apology for raising hopes as it appears to be an error on my part and we were still booting uInitrd from tftp.

Unless you have something you want to try now I might take a break from this for a few hours and maybe drink the shiraz even though I don't deserve it.

Richard,

> Looks like I owe you and everyone else an apology
> for raising hopes as it appears to be an error on
> my part and we were still booting uInitrd from
> tftp.

Not at all. I rethought the envs I posted, and it seems lacking, so it won't work. Back to the drawing board!

>
> Unless you have something you want to try now I
> might take a break from this for a few hours and
> maybe drink the shiraz even though I don't deserve
> it.

Hey, you deserve a drink or two :) hacking is to be a slow and learning experience. Whenever it's done, it's done. No deadline ever needed :) I will be back tomorrow.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
My plan of attack for tomorrow is;

1) setup a single disk HDD install with mbr ext3... basically everything old. Partition offset 128MB for 3)

2) Even though you think env's may be lacking for loading initd from HDD I will try it anyway just to see if without the complexity of gpt, raid and ext4 it can fly.

3) Try the boot files embedded in raw disk sector and see if it works with stock u-boot

4) Whatever you would like to try

5) Drink more shiraz

Richard,

OK. Have not slept yet, need more red wine :)) so here is what I think a good solution for now.

We have been trying to do too much (mea culpa).

It's easy to just ignore uInitrd altogether for now. In Debian rootfs, when we install the kernel image that include initrd, everything was falling into place. The initrd used during booting is really not needed to be that big. Once the kernel has booted, the appropriate modules will be loaded anyway.

So we can boot it this way (adjust to your current envs as needed)

setenv ipaddr 192.168.1.250
setenv serverip 192.168.1.2
setenv load_dtb_addr 0x1000000
setenv load_image_addr 0x02000000
setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage'
setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtb'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=20 $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; run load_image; run load_dtb; bootz $load_image_addr - $load_dtb_addr'
setenv bootcmd 'run bootcmd_exec; run bootspi'

The root device here is root=/dev/sda1. So if you know where your rootfs device is (sda1, sdb1, sdc1... etc), that's the device to use. And then we can ignore uInitrd for now. We'll come back and either reduce the size of initrd in building new kernel version, or just create a very barebone initrd (like Arch's), so that we can use root=LABEL=rootfs again.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
This is the first of a series of posts as I try various HDD configurations, I'm posting as I go so I don't confuse myself.

Test 1 (existing currently works with tftp zImage, uInitrd and DTB)
rootfs on 4 drive raid 1, gpt, ext4

Boot command

setenv ipaddr 192.168.1.250
setenv serverip 192.168.1.2
setenv load_dtb_addr 0x1000000
setenv load_image_addr 0x02000000
setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage'
setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtb'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=/dev/md0 rootdelay=20  $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_dtb; bootz $load_image_addr - $load_dtb_addr'
setenv bootcmd 'run bootcmd_exec; run bootspi'

Result

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.1.2-rj (root@debian) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PREEMPT Wed May 15 17:34:48 AWST 2019
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Synology RS116
[    0.000000] printk: bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] random: get_random_bytes called from start_kernel+0x78/0x4dc with crng_init=0
[    0.000000] percpu: Embedded 18 pages/cpu s41932 r8192 d23604 u73728
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260608
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/md0 rootdelay=20 mtdparts=spi0.0:4m(boot),-(spi-rootfs) earlyprintk=serial
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1024872K/1048576K available (9216K kernel code, 827K rwdata, 2384K rodata, 1024K init, 330K bss, 23704K reserved, 0K cma-reserved, 262144K highmem)
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000006] sched_clock: 64 bits at 933MHz, resolution 1ns, wraps every 4398046511103ns
[    0.007975] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x1ae5b571769, max_idle_ns: 881590513431 ns
[    0.019059] Switching to timer-based delay loop, resolution 1ns
[    0.025106] Ignoring duplicate/late registration of read_current_timer delay
[    0.032122] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.043339] Console: colour dummy device 80x30
[    0.047777] Calibrating delay loop (skipped), value calculated using timer frequency.. 1866.00 BogoMIPS (lpj=9330000)
[    0.058340] pid_max: default: 32768 minimum: 301
[    0.063017] LSM: Security Framework initializing
[    0.067656] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.074239] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.081535] *** VALIDATE proc ***
[    0.084910] *** VALIDATE cgroup1 ***
[    0.088473] *** VALIDATE cgroup2 ***
[    0.092054] CPU: Testing write buffer coherency: ok
[    0.096918] CPU0: Spectre v2: using BPIALL workaround
[    0.102043] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.165011] Setting up static identity map for 0x100000 - 0x100060
[    0.171226] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.176427] mvebu-pmsu: Initializing Power Management Service Unit
[    0.194993] rcu: Hierarchical SRCU implementation.
[    0.234993] smp: Bringing up secondary CPUs ...
[    0.295048] Booting CPU 1
[    0.297789] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.297792] CPU1: Spectre v2: using BPIALL workaround
[    0.308510] smp: Brought up 1 node, 2 CPUs
[    0.312585] SMP: Total of 2 processors activated (3732.00 BogoMIPS).
[    0.318925] CPU: All CPU(s) started in SVC mode.
[    0.324001] devtmpfs: initialized
[    0.329016] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.336883] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.346677] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.352838] prandom: seed boundary self test passed
[    0.358826] prandom: 100 self tests passed
[    0.362901] pinctrl core: initialized pinctrl subsystem
[    0.368776] NET: Registered protocol family 16
[    0.373646] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.380819] audit: initializing netlink subsys (disabled)
[    0.386765] audit: type=2000 audit(0.360:1): state=initialized audit_enabled=0 res=1
[    0.394494] cpuidle: using governor ladder
[    0.398593] cpuidle: using governor menu
[    0.402610] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.410583] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.416491] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[    0.424544] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
[    0.445609] vgaarb: loaded
[    0.448437] SCSI subsystem initialized
[    0.452721] usbcore: registered new interface driver usbfs
[    0.458252] usbcore: registered new interface driver hub
[    0.463590] usbcore: registered new device driver usb
[    0.469039] media: Linux media interface: v0.10
[    0.473585] videodev: Linux video capture interface: v2.00
[    0.479213] pps_core: LinuxPPS API ver. 1 registered
[    0.484152] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.493842] PTP clock support registered
[    0.498519] clocksource: Switched to clocksource arm_global_timer
[    0.846812] VFS: Disk quotas dquot_6.6.0
[    0.850770] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.863783] NET: Registered protocol family 2
[    0.868429] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.876073] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.883122] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.889586] TCP: Hash tables configured (established 8192 bind 8192)
[    0.895958] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.901878] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.908325] NET: Registered protocol family 1
[    0.912921] RPC: Registered named UNIX socket transport module.
[    0.918823] RPC: Registered udp transport module.
[    0.923502] RPC: Registered tcp transport module.
[    0.928181] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.934758] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.941393] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.950675] Initialise system trusted keyrings
[    0.955114] Key type blacklist registered
[    0.959204] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    0.965671] zbud: loaded
[    0.968641] NFS: Registering the id_resolver key type
[    0.973674] Key type id_resolver registered
[    0.977834] Key type id_legacy registered
[    0.981836] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.988503] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.994934] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.002225] orangefs_debugfs_init: called with debug mask: :none: :0:
[    1.008710] orangefs_init: module version upstream loaded
[    1.017743] Key type asymmetric registered
[    1.021835] Asymmetric key parser 'x509' registered
[    1.026712] bounce: pool size: 64 pages
[    1.030590] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    1.037988] io scheduler bfq registered
[    1.043315] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl driver
[    1.052060] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    1.057955] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.063431] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[    1.070365] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.077795] PCI: bus0: Fast back to back transfers disabled
[    1.083358] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.091338] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.099313] pci 0000:00:04.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.107637] pci 0000:00:02.0: ASPM: current common clock configuration is broken, reconfiguring
[    1.139227] PCI: bus1: Fast back to back transfers disabled
[    1.145552] PCI: bus2: Fast back to back transfers enabled
[    1.151813] PCI: bus3: Fast back to back transfers enabled
[    1.157301] pci 0000:00:02.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    1.164152] pci 0000:00:02.0: BAR 13: assigned [io  0x10000-0x10fff]
[    1.170481] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[    1.177669] pci 0000:00:03.0: BAR 6: assigned [mem 0xe0200000-0xe02007ff pref]
[    1.184861] pci 0000:00:04.0: BAR 6: assigned [mem 0xe0300000-0xe03007ff pref]
[    1.192056] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[    1.199248] pci 0000:01:00.0: BAR 5: assigned [mem 0xe0010000-0xe00107ff]
[    1.206005] pci 0000:01:00.0: BAR 4: assigned [io  0x10000-0x1001f]
[    1.212247] pci 0000:01:00.0: BAR 0: assigned [io  0x10020-0x10027]
[    1.218485] pci 0000:01:00.0: BAR 2: assigned [io  0x10028-0x1002f]
[    1.224726] pci 0000:01:00.0: BAR 1: assigned [io  0x10030-0x10033]
[    1.230968] pci 0000:01:00.0: BAR 3: assigned [io  0x10034-0x10037]
[    1.237206] pci 0000:00:02.0: PCI bridge to [bus 01]
[    1.242151] pci 0000:00:02.0:   bridge window [io  0x10000-0x10fff]
[    1.248388] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    1.255149] pci 0000:00:03.0: PCI bridge to [bus 02]
[    1.260095] pci 0000:00:04.0: PCI bridge to [bus 03]
[    1.265077] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[    1.271632] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.328857] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    1.336406] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.398854] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[    1.442197] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.451508] printk: console [ttyS0] disabled
[    1.475842] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22, base_baud = 12500000) is a 16550A
[    1.484795] printk: console [ttyS0] enabled
[    1.484795] printk: console [ttyS0] enabled
[    1.493209] printk: bootconsole [earlycon0] disabled
[    1.493209] printk: bootconsole [earlycon0] disabled
[    1.523764] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 23, base_baud = 12500000) is a 16550A
[    1.543772] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 4 ports 6 Gbps 0xf impl SATA mode
[    1.551915] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[    1.561216] scsi host0: ahci
[    1.564392] scsi host1: ahci
[    1.567533] scsi host2: ahci
[    1.570690] scsi host3: ahci
[    1.573759] ata1: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010100 irq 48
[    1.581201] ata2: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010180 irq 48
[    1.588635] ata3: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010200 irq 48
[    1.596063] ata4: SATA max UDMA/133 abar m2048@0xe0010000 port 0xe0010280 irq 48
[    1.604798] m25p80 spi0.0: found n25q064, expected mx25l6405d
[    1.610705] m25p80 spi0.0: n25q064 (8192 Kbytes)
[    1.615348] 2 cmdlinepart partitions found on MTD device spi0.0
[    1.621300] Creating 2 MTD partitions on "spi0.0":
[    1.626113] 0x000000000000-0x000000400000 : "boot"
[    1.631513] 0x000000400000-0x000000800000 : "spi-rootfs"
[    1.637865] libphy: Fixed MDIO Bus: probed
[    1.642369] libphy: orion_mdio_bus: probed
[    1.647161] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    1.655764] mvneta f1070000.ethernet eth0: Using hardware mac address 00:50:43:1c:24:27
[    1.664025] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.670603] ehci-pci: EHCI PCI platform driver
[    1.675096] ehci-orion: EHCI orion driver
[    1.679568] usbcore: registered new interface driver usblp
[    1.685103] usbcore: registered new interface driver usb-storage
[    1.691308] mousedev: PS/2 mouse device common for all mice
[    1.697523] armada38x-rtc f10a3800.rtc: registered as rtc0
[    1.703221] i2c /dev entries driver
[    1.731716] gpio-fan gpio-fan: GPIO fan initialized
[    1.738171] orion_wdt: Initial timeout 171 sec
[    1.744524] marvell-cesa f1090000.crypto: CESA device successfully registered
[    1.751844] hidraw: raw HID events driver (C) Jiri Kosina
[    1.757411] usbcore: registered new interface driver usbhid
[    1.763020] usbhid: USB HID core driver
[    1.767058] drop_monitor: Initializing network drop monitor service
[    1.773585] NET: Registered protocol family 10
[    1.788577] Segment Routing with IPv6
[    1.792290] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    1.798807] NET: Registered protocol family 17
[    1.813350] 8021q: 802.1Q VLAN Support v1.8
[    1.817574] Key type dns_resolver registered
[    1.821954] ThumbEE CPU extension supported.
[    1.826244] Registering SWP/SWPB emulation handler
[    1.831350] registered taskstats version 1
[    1.835464] Loading compiled-in X.509 certificates
[    1.840321] zswap: loaded using pool lzo/zbud
[    1.845519] Key type big_key registered
[    1.849670] Key type encrypted registered
[    1.855237] v5.0-sata0: supplied by pwr_en_sata0
[    1.859929] v12.0-sata0: supplied by pwr_en_sata0
[    1.865055] ahci-mvebu f10a8000.sata: masking port_map 0x3 -> 0x1
[    1.871222] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x1 impl platform mode
[    1.880320] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[    1.889587] scsi host4: ahci-mvebu
[    1.903232] scsi host5: ahci-mvebu
[    1.906774] ata5: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 41
[    1.914768] ata6: DUMMY
[    1.917430] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    1.922786] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 1
[    1.929853] ata1: SATA link down (SStatus 0 SControl 300)
[    1.930388] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    1.935767] ata3: SATA link down (SStatus 0 SControl 300)
[    1.945026] xhci-hcd f10f0000.usb3: irq 42, io mem 0xf10f0000
[    1.950535] ata4: SATA link down (SStatus 0 SControl 300)
[    1.956419] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    1.969959] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.977213] usb usb1: Product: xHCI Host Controller
[    1.982116] usb usb1: Manufacturer: Linux 5.1.2-rj xhci-hcd
[    1.987712] usb usb1: SerialNumber: f10f0000.usb3
[    1.992750] hub 1-0:1.0: USB hub found
[    1.996532] hub 1-0:1.0: 1 port detected
[    2.000682] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    2.006021] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[    2.013563] xhci-hcd f10f0000.usb3: Host supports USB 3.0  SuperSpeed
[    2.020069] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.028249] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    2.036562] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.043830] usb usb2: Product: xHCI Host Controller
[    2.048733] usb usb2: Manufacturer: Linux 5.1.2-rj xhci-hcd
[    2.054329] usb usb2: SerialNumber: f10f0000.usb3
[    2.059311] hub 2-0:1.0: USB hub found
[    2.063093] hub 2-0:1.0: 1 port detected
[    2.067416] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.072773] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[    2.080349] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x0000000000010010
[    2.089639] xhci-hcd f10f8000.usb3: irq 43, io mem 0xf10f8000
[    2.095577] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
[    2.103889] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.111152] usb usb3: Product: xHCI Host Controller
[    2.116051] usb usb3: Manufacturer: Linux 5.1.2-rj xhci-hcd
[    2.121660] usb usb3: SerialNumber: f10f8000.usb3
[    2.126664] hub 3-0:1.0: USB hub found
[    2.128537] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.130453] hub 3-0:1.0: 1 port detected
[    2.140792] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    2.146139] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[    2.153672] ata2.00: NCQ Send/Recv Log not supported
[    2.153680] xhci-hcd f10f8000.usb3: Host supports USB 3.0  SuperSpeed
[    2.158686] ata2.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[    2.165159] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.171363] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[    2.179528] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.01
[    2.194696] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.201960] usb usb4: Product: xHCI Host Controller
[    2.206864] usb usb4: Manufacturer: Linux 5.1.2-rj xhci-hcd
[    2.212470] usb usb4: SerialNumber: f10f8000.usb3
[    2.217384] ata2.00: NCQ Send/Recv Log not supported
[    2.217473] hub 4-0:1.0: USB hub found
[    2.222423] ata2.00: configured for UDMA/133
[    2.226189] hub 4-0:1.0: 1 port detected
[    2.234579] scsi 1:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[    2.243308] armada38x-rtc f10a3800.rtc: setting system clock to 2019-05-18T22:15:24 UTC (1558217724)
[    2.243567] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    2.252743] v5.0-sata1: supplied by pwr_en_sata1
[    2.260486] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    2.265079] v12.0-sata0: supplied by pwr_en_sata1
[    2.270303] sd 1:0:0:0: [sda] Write Protect is off
[    2.274995] v12.0-sata0: disabling
[    2.279773] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.283156] v5.0-sata1: disabling
[    2.295619] v12.0-sata0: disabling
[    2.299351] Waiting 20 sec before mounting root device...
[    2.345232]  sda: sda1 sda2 sda3
[    2.349270] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    2.408531] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.415480] ata5.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[    2.421702] ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32)
[    2.429243] ata5.00: configured for UDMA/133
[    2.443784] scsi 4:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[    2.452276] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    2.460203] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[    2.465480] sd 4:0:0:0: [sdb] Write Protect is off
[    2.470341] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.558010]  sdb: sdb1 sdb2 sdb3
[    2.562009] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[   10.268613] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.324208] ata4.00: NCQ Send/Recv Log not supported
[   10.329204] ata4.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[   10.335413] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   10.342338] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.349793] ata4.00: NCQ Send/Recv Log not supported
[   10.354782] ata4.00: configured for UDMA/133
[   10.359270] scsi 3:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[   10.367839] sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[   10.375833] sd 3:0:0:0: [sdc] 4096-byte physical blocks
[   10.380408] ata3.00: NCQ Send/Recv Log not supported
[   10.381129] sd 3:0:0:0: [sdc] Write Protect is off
[   10.386076] ata3.00: ATA-9: ST2000VN004-2E4164, SC60, max UDMA/133
[   10.390920] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   10.397114] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[   10.414526] ata3.00: NCQ Send/Recv Log not supported
[   10.419524] ata3.00: configured for UDMA/133
[   10.423997] scsi 2:0:0:0: Direct-Access     ATA      ST2000VN004-2E41 SC60 PQ: 0 ANSI: 5
[   10.432511] sd 2:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[   10.440405] sd 2:0:0:0: [sdd] 4096-byte physical blocks
[   10.445716] sd 2:0:0:0: [sdd] Write Protect is off
[   10.450578] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   10.496443]  sdc: sdc1 sdc2 sdc3
[   10.500481] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[   10.510606]  sdd: sdd1 sdd2 sdd3
[   10.514509] sd 2:0:0:0: [sdd] Attached SCSI removable disk
[   22.908611] VFS: Cannot open root device "md0" or unknown-block(0,0): error -6
[   22.915866] Please append a correct "root=" boot option; here are the available partitions:
[   22.924382] 1f00            4096 mtdblock0
[   22.924383]  (driver?)
[   22.930962] 1f01            4096 mtdblock1
[   22.930963]  (driver?)
[   22.937530] 0800      1953514584 sda
[   22.937531]  driver: sd
[   22.943682]   0801        19529728 sda1 dd39bdee-7290-46c3-9ed1-fb7c7409a6eb
[   22.943683]
[   22.952265]   0802         1953792 sda2 efb4d57e-da9e-451a-9cf4-087b2b1d6748
[   22.952265]
[   22.960854]   0803      1932029952 sda3 9da2f424-d140-4604-8ad8-ec41e44248f9
[   22.960855]
[   22.969438] 0810      1953514584 sdb
[   22.969439]  driver: sd
[   22.975569]   0811        19529728 sdb1 97ca5604-bb78-4463-be52-89ce04ada188
[   22.975570]
[   22.984156]   0812         1953792 sdb2 3026ed0a-ec29-4e73-8672-f6c3e303c9c6
[   22.984157]
[   22.992736]   0813      1932029952 sdb3 66055609-9012-4404-b545-bd5f0c7ca709
[   22.992736]
[   23.001314] 0820      1953514584 sdc
[   23.001316]  driver: sd
[   23.007445]   0821        19529728 sdc1 56b48894-3d57-4f51-bfc3-0dd77cbf4e07
[   23.007445]
[   23.016023]   0822         1953792 sdc2 3e59dd1f-dc9e-46cc-a713-948495bf6c22
[   23.016023]
[   23.024600]   0823      1932029952 sdc3 3f693e8f-74c4-47ee-bcd8-91ea9069195b
[   23.024601]
[   23.033178] 0830      1953514584 sdd
[   23.033179]  driver: sd
[   23.039317]   0831        19529728 sdd1 a9eee82d-4036-48b2-92a0-ef26e9bc4f51
[   23.039318]
[   23.047891]   0832         1953792 sdd2 13d91e11-b2f3-42c9-aa4b-14a5d6d33c78
[   23.047891]
[   23.056469]   0833      1932029952 sdd3 d8e50a9e-55e9-4b1f-bf9d-43f27c1fb51e
[   23.056470]
[   23.065049] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   23.073351] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.1.2-rj #1
[   23.079469] Hardware name: Marvell Armada 380/385 (Device Tree)
[   23.085428] [<c0117574>] (unwind_backtrace) from [<c0111d64>] (show_stack+0x10/0x14)
[   23.093209] [<c0111d64>] (show_stack) from [<c098bc00>] (dump_stack+0x70/0x8c)
[   23.100467] [<c098bc00>] (dump_stack) from [<c0126d50>] (panic+0xf0/0x2bc)
[   23.107378] [<c0126d50>] (panic) from [<c0d01700>] (mount_block_root+0x1d4/0x264)
[   23.114896] [<c0d01700>] (mount_block_root) from [<c0d01880>] (mount_root+0xf0/0x12c)
[   23.122762] [<c0d01880>] (mount_root) from [<c0d01a00>] (prepare_namespace+0x144/0x184)
[   23.130805] [<c0d01a00>] (prepare_namespace) from [<c0d0120c>] (kernel_init_freeable+0x2f4/0x3c4)
[   23.139719] [<c0d0120c>] (kernel_init_freeable) from [<c09a0e10>] (kernel_init+0x8/0x10c)
[   23.147934] [<c09a0e10>] (kernel_init) from [<c01010e8>] (ret_from_fork+0x14/0x2c)
[   23.155535] Exception stack(0xef0b3fb0 to 0xef0b3ff8)
[   23.160608] 3fa0:                                     00000000 00000000 00000000 00000000
[   23.168822] 3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   23.177035] 3fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   23.183681] CPU0: stopping
[   23.186401] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.1.2-rj #1
[   23.192519] Hardware name: Marvell Armada 380/385 (Device Tree)
[   23.198469] [<c0117574>] (unwind_backtrace) from [<c0111d64>] (show_stack+0x10/0x14)
[   23.206249] [<c0111d64>] (show_stack) from [<c098bc00>] (dump_stack+0x70/0x8c)
[   23.213506] [<c098bc00>] (dump_stack) from [<c0115260>] (handle_IPI+0x2e8/0x3e0)
[   23.220940] [<c0115260>] (handle_IPI) from [<c058f74c>] (gic_handle_irq+0x84/0x90)
[   23.228545] [<c058f74c>] (gic_handle_irq) from [<c010218c>] (__irq_svc+0x6c/0xa8)
[   23.236060] Exception stack(0xc0e01f10 to 0xc0e01f58)
[   23.241132] 1f00:                                     00000000 00006450 ef7d00a0 c0120380
[   23.249348] 1f20: 00000000 00000000 c0e08d48 c0e08d70 ffffe000 c0e08db8 c0bd2b70 c0d5ca38
[   23.257561] 1f40: 7ffffffa c0e01f60 c010e7b8 c010e7a8 60000013 ffffffff
[   23.264207] [<c010218c>] (__irq_svc) from [<c010e7a8>] (arch_cpu_idle+0x1c/0x38)
[   23.271638] [<c010e7a8>] (arch_cpu_idle) from [<c0153bd8>] (do_idle+0x13c/0x270)
[   23.279068] [<c0153bd8>] (do_idle) from [<c0153fa0>] (cpu_startup_entry+0x18/0x1c)
[   23.286673] [<c0153fa0>] (cpu_startup_entry) from [<c0d00e64>] (start_kernel+0x428/0x4dc)
[   23.294887] [<c0d00e64>] (start_kernel) from [<00000000>] (  (null))
[   23.301273] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
[   37.598514] ------------[ cut here ]------------
[   37.603156] WARNING: CPU: 1 PID: 10 at kernel/irq_work.c:68 irq_work_queue_on+0x58/0xf0
[   37.611193] Modules linked in:
[   37.614262] CPU: 1 PID: 10 Comm: rcu_preempt Not tainted 5.1.2-rj #1
[   37.620642] Hardware name: Marvell Armada 380/385 (Device Tree)
[   37.626590] [<c0117574>] (unwind_backtrace) from [<c0111d64>] (show_stack+0x10/0x14)
[   37.634370] [<c0111d64>] (show_stack) from [<c098bc00>] (dump_stack+0x70/0x8c)
[   37.641626] [<c098bc00>] (dump_stack) from [<c0126b6c>] (__warn+0xd4/0xf0)
[   37.648533] [<c0126b6c>] (__warn) from [<c0126f54>] (warn_slowpath_null+0x38/0x44)
[   37.656137] [<c0126f54>] (warn_slowpath_null) from [<c01f5948>] (irq_work_queue_on+0x58/0xf0)
[   37.664704] [<c01f5948>] (irq_work_queue_on) from [<c018f5a8>] (rcu_implicit_dynticks_qs+0x240/0x278)
[   37.673968] [<c018f5a8>] (rcu_implicit_dynticks_qs) from [<c018c934>] (force_qs_rnp+0x114/0x14c)
[   37.682793] [<c018c934>] (force_qs_rnp) from [<c018d4c0>] (rcu_gp_kthread+0x440/0x96c)
[   37.690747] [<c018d4c0>] (rcu_gp_kthread) from [<c0144cc0>] (kthread+0x130/0x144)
[   37.698264] [<c0144cc0>] (kthread) from [<c01010e8>] (ret_from_fork+0x14/0x2c)
[   37.705517] Exception stack(0xef0cdfb0 to 0xef0cdff8)
[   37.710589] dfa0:                                     00000000 00000000 00000000 00000000
[   37.718803] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   37.727017] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   37.733659] ---[ end trace fd7202045e9e6216 ]---

Comment
Looks to me as if zImage doesn't contain drivers (or mdadm static) to bring raid up
Onto next test.

Quote

Looks to me as if zImage doesn't contain drivers (or mdadm static) to bring raid up

You need uInitrd to do this.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi
I'm getting interrupted a lot this morning testing may be slow!

Test 2
Single HDD, msdos, ext3

Boot command

setenv ipaddr 192.168.1.250
setenv serverip 192.168.1.2
setenv load_dtb_addr 0x1000000
setenv load_image_addr 0x02000000
setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage'
setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtb'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=/dev/sda1 rootdelay=20  $mtdparts earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian . . .; run set_bootargs; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_dtb; bootz $load_image_addr - $load_dtb_addr'
setenv bootcmd 'run bootcmd_exec; run bootspi'

Result

root@debian:~#

Comment
Win :)

Next test as above gtp and ext4

@bodhi
Test 3
Single HDD, gpt, ext4

Boot command
As test 2

Result

root@debian:~#

Next test 4 is to split /boot onto a separate partition so that the main rootfs can sit on raid. For this test I will just do the split, if it works (can't think that it wouldn't) I will move onto setting up / on raid 5 for test 5.

Richard,

> Test 2
> Single HDD, msdos, ext3
>
> Boot command
>

> setenv ipaddr 192.168.1.250
> setenv serverip 192.168.1.2
> setenv load_dtb_addr 0x1000000
> setenv load_image_addr 0x02000000
> setenv load_image 'echo loading zImage from
> tftpserver ...; tftpboot $load_image_addr zImage'
> setenv load_dtb 'echo loading DTB from tftpserver
> ...; tftpboot $load_dtb_addr
> armada-385-synology-rs816-v12.dtb'
> setenv set_bootargs 'setenv bootargs
> "console=ttyS0,115200 root=/dev/sda1 rootdelay=20 
> $mtdparts earlyprintk=serial"'
> setenv bootcmd_exec 'echo Booting Debian . . .;
> run set_bootargs; setenv fdt_skip_update yes;
> setenv initrd_high 0xffffffff; run load_image; run
> load_dtb; bootz $load_image_addr -
> $load_dtb_addr'
> setenv bootcmd 'run bootcmd_exec; run bootspi'
>

>
> Result
>

> root@debian:~#
>

>
> Comment
> Win :)

Cool! That's half way to the zImage-DTB-in-flash solution.

What you would also want to do is to double check the output of lsmod to see if all modules were loaded as expected.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi

Quote

check the output of lsmod

I'm half way through the next test but I will check next time. Most modules needed for this box are built in so the list will be short anyway.

Quote

You need uInitrd to do this

I was just wondering on that, the current kernel config builds all the raid drivers as modules so, yes, it would need uInitrd but if I build the raid modules into the kernel ? On Arch the static version of mdadm gets placed in the initrams image so I'm guessing without it it wouldn't work. The zImage is just built in the kernel and would have no way to do this so I presume it just wouldn't work but thought I'd ask anyway.