Welcome! Log In Create A New Profile

Advanced

debian on synology ds214 - periphery issues

Posted by lonestar 
debian on synology ds214 - periphery issues
November 18, 2022 09:01AM
Hi all,

I am currently playing around a bit with my Synology DS214 NAS. I have successfully installed debian on it.
If someone wants to do the same here are the steps I took. Afterwards I have a few remaining issues where I would appreciate any help.

Note: DO NOT EVER CALL SAVEENV ON THE STOCK U-BOOT LOADER.
It will overwrite your kernel in the SPI flash and for some reason the stock u-boot will then no longer boot. If this happened to you anyways: overwrite the u-boot env checksum in flash at address 1.000.000 (decimal). Then at least stock u-boot itself will load again. You can then load the kernel via serial and the initrd from the SPI flash.

1.) getting u-boot and debian to work:
- I based my work on the DS414 which is already supported.
- I had to change the board init code to reduce the ram to 512M
in u-boot
change board/Synology/ds414/ds414.c: CS0 size from 0x3FFFFFE1 to 0x1FFFFFE1

- the 5.13.8 kernel was not very stable, but just enough to get install the 6.0.7 kernel, which works very well. Took a few reboots. So if you see problems like a kernel dump about cpu stalls, just try again.

2.) rootfs on the external usb ssd
- I flashed a new u-boot onto the spi flash and can boot debian off an externally connected usb ssd.
- I copied the rootfs from the https://forum.doozan.com/read.php?2,32146 thread to the ssd as an ext2 filesystem (ext4 might work too).
commands for u-boot:
- plug the ssd on the back usb (front one doesn't work). I use the one near the ethernet port.
- pci enum (<-- this is very important, took me quite a while to find out that usb needs this.)
- usb start
- ext2load usb 0:1 0x02000000 /boot/uImage
- ext2load usb 0:1 0x08000000 /boot/uInitrd
- bootm 0x02000000 0x08000000

3.) kwboot
- connect a uart to the PINs as shown in the attached screenshot. The six pins can be reached without opening the device.
- call "kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot/u-boot/u-boot-with-spl.kwb -a" to start your self-built u-boot

4.) my issues
currently at least the following periphery doesn't work:
4.1) ethernet:
ds414 had two ports, ds214 only has one, but it doesn't work. The port is shown as link up, but no data is sent or received. dhcp request times out.
In my experiments I focused on u-boot and tested with "ping myotherhost". I tried to edit the u-boot device tree and changed values.

I tried the following:
ethernet@70000 {
status = "okay";
pinctrl-0 = <&ge1_rgmii_pins>;
pinctrl-names = "default";
phy = <&phy1>;
phy-mode = "rgmii-id";
};

phy0 leads to an error message
pinctrl as ge0... has no effect
ethernet as @74000 has no effect
ethernet as @74000 and pinctrl as ge0 has no effect
ethernet as ge0_gmii_pins has no effect (see ethtool output of original firmware)

4.2) sata enclosure
the hard disk in the enclosure is not detected.

4.3) front usb
not detected
this is not important for me

4.4) fan
pwmconfig of fancontrol shows no pwm found.


To debug these issues I can boot to the original firmware and enter the shell. The original formware is based on kernel 3.2 and has no device tree yet, so no /proc/device-tree entries.

original.txt = stock firmware dmesg + u-boot + ethtool
myboot-nonet.log = my dmesg
Attachments:
open | download - u-boot-serial-small.jpg (928.4 KB)
open | download - myboot-nonet.log (30.7 KB)
open | download - original.txt (33.4 KB)
Re: debian on synology ds214 - periphery issues
November 18, 2022 09:26AM
ethernet@70000 {
status = "okay";
pinctrl-0 = <&ge0_gmii_pins>;
pinctrl-names = "default";
phy = <&phy1>;
phy-mode = "gmii";
};
leads to a change: packet not sent message is repeatedly shown (I had the previous try of gmii mode wrong, didn't change the phy-mode correctly)

just realized that it also shows:
mvneta ethernet@70000: can't power up port



Edited 1 time(s). Last edit at 11/18/2022 09:32AM by lonestar.
Re: debian on synology ds214 - periphery issues
November 18, 2022 09:45AM
the sata problem might be related to the disabled stuff here:

root@debian:~# lspci -v
00:01.0 PCI bridge: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC (rev 02) (prog-if 00 [Normal decode])
Device tree node: /sys/firmware/devicetree/base/soc/pcie@82000000/pcie@1,0
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: f8000000-f80fffff [size=1M]
Prefetchable memory behind bridge: 00000000-000fffff [size=1M]
Capabilities: [40] Subsystem: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC
Capabilities: [48] Express Root Port (Slot+), MSI 00
Capabilities: [100] Advanced Error Reporting

00:05.0 PCI bridge: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC (rev 02) (prog-if 00 [Normal decode])
Device tree node: /sys/firmware/devicetree/base/soc/pcie@82000000/pcie@5,0
Flags: fast devsel
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: 00000000-000fffff [size=1M]
Capabilities: [40] Subsystem: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC
Capabilities: [48] Express Root Port (Slot+), MSI 00
Capabilities: [100] Advanced Error Reporting
Re: debian on synology ds214 - periphery issues
November 18, 2022 03:26PM
lonestar,

> Note: DO NOT EVER CALL SAVEENV ON THE STOCK U-BOOT
> LOADER.
> It will overwrite your kernel in the SPI flash and
> for some reason the stock u-boot will then no
> longer boot. If this happened to you anyways:
> overwrite the u-boot env checksum in flash at
> address 1.000.000 (decimal). Then at least stock
> u-boot itself will load again. You can then load
> the kernel via serial and the initrd from the SPI
> flash.

Yes, for these Synology boxes be very careful with saveenv. Do this only after you have booted to Debian, and don't care to boot back to stock. Synology apparently has a significant bug in that the u-bot envs location is same as the kernel image location on flash!

If you want to preserve stock OS in flash to dual boot, dump the mtd partitions, and then repartition to the correct sizes

> - the 5.13.8 kernel was not very stable, but just
> enough to get install the 6.0.7 kernel, which
> works very well. Took a few reboots. So if you see
> problems like a kernel dump about cpu stalls, just
> try again.

Cool! thanks for the report. I'll need to make a note the release instruction about kernel 5.13.8 is flaky.

> - pci enum (<-- this is very important, took me
> quite a while to find out that usb needs this.)

This is because that port is USB 3.0 on PCIe bus. And the running u-boot was not set up to invoke pci enum automatically.

> 4.1) ethernet:
> ds414 had two ports, ds214 only has one, but it
> doesn't work. The port is shown as link up, but no
> data is sent or received. dhcp request times out.
> In my experiments I focused on u-boot and tested
> with "ping myotherhost". I tried to edit the
> u-boot device tree and changed values.

I think I know what's going on. To get some more info,

At stock u-boot prompt, assuming your network router is 192.168.0.1,

setenv ipaddr 192.168.0.100
printenv
setenv ethact egiga0
ping <router IP address>
setenv ethact egiga1
ping <router IP address>

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 19, 2022 03:31AM
stock firmware insists on egiga0. egiga1 will be automatically switched back. see below.

Quote

Press Ctrl+C to abort autoboot in 3 second
Marvell>> setenv ipaddr 192.168.1.190
Marvell>> setenv ethact egiga0
Marvell>> ping 192.168.1.1
Using egiga0 device
host 192.168.1.1 is alive

---- rebooted here ------

Press Ctrl+C to abort autoboot in 3 second
Marvell>> pri ethact
ethact=egiga0
Marvell>> pri ethprime
ethprime=egiga0
Marvell>> setenv ethact egiga1
Marvell>> setenv ethprime egiga1
Marvell>> pri ethact
ethact=egiga1
Marvell>> pri ethprime
ethprime=egiga1
Marvell>> setenv ipaddr 192.168.1.190
Marvell>> ping 192.168.1.1
Using egiga0 device
host 192.168.1.1 is alive
Marvell>> pri ethact
ethact=egiga0
Marvell>> pri ethprime
ethprime=egiga1
Re: debian on synology ds214 - periphery issues
November 19, 2022 03:24PM
lonestar,

Try this DTS patch.

root@tldDebian:/usr/src/linux-6.0.7-mvebu/arch/arm/boot/dts# diff -Naur armada-xp-synology-ds214.dts.orig armada-xp-synology-ds214.dts 
--- armada-xp-synology-ds214.dts.orig	2022-11-03 08:00:35.000000000 -0700
+++ armada-xp-synology-ds214.dts	2022-11-19 13:18:04.974981611 -0800
@@ -25,8 +25,8 @@
 #include "armada-xp-mv78230.dtsi"
 
 / {
-	model = "Synology DS414";
-	compatible = "synology,ds414", "marvell,armadaxp-mv78230",
+	model = "Synology DS214";
+	compatible = "synology,ds414", "synology,ds214", "marvell,armadaxp-mv78230",
 		     "marvell,armadaxp", "marvell,armada-370-xp";
 
 	chosen {
@@ -95,17 +95,10 @@
 				status = "okay";
 				pinctrl-0 = <&ge0_rgmii_pins>;
 				pinctrl-names = "default";
-				phy = <&phy1>;
-				phy-mode = "rgmii-id";
-			};
-
-			ethernet@74000 {
-				pinctrl-0 = <&ge1_rgmii_pins>;
-				pinctrl-names = "default";
-				status = "okay";
 				phy = <&phy0>;
 				phy-mode = "rgmii-id";
 			};
+
 		};
 	};
 
@@ -196,12 +189,9 @@
 
 &mdio {
 	phy0: ethernet-phy@0 { /* Marvell 88E1512 */
-		reg = <0>;
-	};
-
-	phy1: ethernet-phy@1 { /* Marvell 88E1512 */
 		reg = <1>;
 	};
+
 };
 
 &pinctrl {

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 20, 2022 03:37AM
Hi bodhi,

unfortunately this doesn't work yet:
Quote

U-Boot 2023.01-rc1 (Nov 20 2022 - 09:26:19 +0000)

SoC: MV78230-B0 at 1066 MHz
DRAM: 512 MiB (533 MHz, 32-bit, ECC not enabled)
Core: 23 devices, 17 uclasses, devicetree: separate
Loading Environment from SPIFlash... SF: Detected n25q064 with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
In: serial@12000
Out: serial@12000
Err: serial@12000
Model: Synology DS214
Board: DS414
Net: eth0: ethernet@70000
=> pri ipaddr
ipaddr=192.168.1.190
=> ping 192.168.1.1
ethernet@70000 Waiting for PHY auto negotiation to complete....... done
Using ethernet@70000 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.1.1 is not alive

Thanks,
Martin
Re: debian on synology ds214 - periphery issues
November 20, 2022 07:36AM
I did some further tests regarding the sata drives:

the device tree specifies that pcie@1,0 is the usb controller. I think this is wrong, at least for the ds214:

- when I remove the pcie@1,0 definition usb stops working.
- when only pcie@1,0 is present usb works.

I guess this means that the definitions in armada-xp-mv78230.dtsi might also not be sufficient?

thanks,
Martin
Re: debian on synology ds214 - periphery issues
November 20, 2022 02:17PM
Martin,


Quote

I guess this means that the definitions in armada-xp-mv78230.dtsi might also not be sufficient?

I don't think that's the case. The ds414 has been working for a long time. This box is a 2-bay version for the ds414, so I'd expect that you only need 2 internal SATA ports, and the PCIe bus is just used for USB 3.0. I'm not sure, but my guess is this box does not have the separate PCIe controller like the ds414.

Ethernet is different because there is only one port. But the PHY addr is 1, according to your stock OS ethtool. And it is port 0.

So perhaps, try this DTS patch in the kernel too (boot with stock u-boot). Because if the PHY addr is wrong you would not get that far in u-boot to get ARP timeout.

=======

SATA nodes will need to be revised in the DTS.

=======

I wonder if the ds414 GPL source is also used to build the ds214? there is a SourceForge site for GPL source code:

https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/24922branch/armadaxp-source/

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 11/20/2022 02:20PM by bodhi.
Re: debian on synology ds214 - periphery issues
November 20, 2022 02:42PM
Hi bodhi,

I am currently looking at the GPL source code of synology which seems to be the correct one:
https://master.dl.sourceforge.net/project/dsgpl/Synology%20NAS%20GPL%20Source/24922branch/armadaxp-source/u-boot-armada-2011.12.txz?viasf=1
While I am a software developer myself, my knowledge of u-boot is very limited.

An interesting detail, that I have found so far:
In file mvBoardEnvLib.c:
Quote

...
#elif defined(SYNO_HW_VERSION_DS414) || defined(SYNO_HW_VERSION_DS414r1)
gBoardId = SYNO_AXP_4BAY_2BAY;
#elif defined(SYNO_HW_VERSION_DS214)
gBoardId = SYNO_AXP_2BAY;
...

MV_BOOL mvBoardIsPortInSgmii(MV_U32 ethPortNum)
{
...
case SYNO_AXP_4BAY_2BAY:
case SYNO_AXP_4BAY_RACK:
return MV_FALSE;
break;
case SYNO_AXP_2BAY:
return MV_TRUE;
break;
...

Your comment about the missing PCIe controller makes sense. This actually matches the lspci output I get from the original firmware (only one device in there - the usb3 controller)

regards,
Martin
Re: debian on synology ds214 - periphery issues
November 20, 2022 04:09PM
Martin,

> An interesting detail, that I have found so far:
> In file mvBoardEnvLib.c:
>
Quote

> ...
> #elif defined(SYNO_HW_VERSION_DS414) ||
> defined(SYNO_HW_VERSION_DS414r1)
> gBoardId = SYNO_AXP_4BAY_2BAY;
> #elif defined(SYNO_HW_VERSION_DS214)
> gBoardId = SYNO_AXP_2BAY;
> ...
>
> MV_BOOL mvBoardIsPortInSgmii(MV_U32 ethPortNum)
> {
> ...
> case SYNO_AXP_4BAY_2BAY:
> case SYNO_AXP_4BAY_RACK:
> return MV_FALSE;
> break;
> case SYNO_AXP_2BAY:
> return MV_TRUE;
> break;
> ...
>
>

That's a good news. Apparently the same code base is used for 414 and 214.

> Your comment about the missing PCIe controller
> makes sense. This actually matches the lspci
> output I get from the original firmware (only one
> device in there - the usb3 controller)

That's more good news. Meaning the DTS can be modified easily. Let me make another patch.

I think if possible you should first boot with stock u-boot and Debian rootfs to see if the DTS changes are working (and of course also run your version of u-boot when you add more to it).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 20, 2022 06:47PM
Here is the revised patch. Of course the other old definition for 4 SATAs need to be removed (or 2 regulators should be kept if they are correct). But here is the internal 2-port-sata node should be added.

diff -Naur armada-xp-synology-ds214.dts.orig armada-xp-synology-ds214.dts
--- armada-xp-synology-ds214.dts.orig	2022-11-03 08:00:35.000000000 -0700
+++ armada-xp-synology-ds214.dts	2022-11-20 16:37:12.258508487 -0800
@@ -25,8 +25,8 @@
 #include "armada-xp-mv78230.dtsi"
 
 / {
-	model = "Synology DS414";
-	compatible = "synology,ds414", "marvell,armadaxp-mv78230",
+	model = "Synology DS214";
+	compatible = "synology,ds414", "synology,ds214", "marvell,armadaxp-mv78230",
 		     "marvell,armadaxp", "marvell,armada-370-xp";
 
 	chosen {
@@ -95,17 +95,14 @@
 				status = "okay";
 				pinctrl-0 = <&ge0_rgmii_pins>;
 				pinctrl-names = "default";
-				phy = <&phy1>;
-				phy-mode = "rgmii-id";
-			};
-
-			ethernet@74000 {
-				pinctrl-0 = <&ge1_rgmii_pins>;
-				pinctrl-names = "default";
-				status = "okay";
 				phy = <&phy0>;
 				phy-mode = "rgmii-id";
 			};
+
+                        sata@a0000 {
+                                nr-ports = <2>;
+                                status = "okay";
+                        };
 		};
 	};
 
@@ -196,12 +193,9 @@
 
 &mdio {
 	phy0: ethernet-phy@0 { /* Marvell 88E1512 */
-		reg = <0>;
-	};
-
-	phy1: ethernet-phy@1 { /* Marvell 88E1512 */
 		reg = <1>;
 	};
+
 };
 
 &pinctrl {

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 21, 2022 01:58PM
Hi bodhi,

doesn't work yet:
on u-boot sata init blocks forever.

On linux the following lines are in the dmesg output:

Quote

[ 3.286187][ T1] scsi host0: sata_mv
[ 3.291223][ T1] scsi host1: sata_mv
[ 3.295841][ T1] ata1: SATA max UDMA/133 irq 37
[ 3.300665][ T1] ata2: SATA max UDMA/133 irq 37
[ 3.636269][ T674] ata1: SATA link down (SStatus 0 SControl F300)
[ 3.969677][ T679] ata2: SATA link down (SStatus 0 SControl F300)

regards,
Martin
Re: debian on synology ds214 - periphery issues
November 21, 2022 02:32PM
I think we are on the right track with the sata controller:

stock firmware:
Quote

[ 150.114185] sata_mv sata_mv.0: version 1.28
[ 150.114250] sata_mv sata_mv.0: cannot get clkdev
[ 150.118980] sata_mv sata_mv.0: slots 32 ports 2
[ 150.124957] scsi0 : sata_mv
[ 150.128240] scsi1 : sata_mv
[ 150.131399] ata1: SATA max UDMA/133 irq 55
[ 150.135512] ata2: SATA max UDMA/133 irq 55
[ 150.487695] ata1: SATA link down (SStatus 0 SControl F300)
[ 159.037686] ata2: link is slow to respond, please be patient (ready=0)
[ 160.417698] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 160.617734] ata2.00: ATA-9: WDC WD30EFRX-68EUZN0, 82.00A82, max UDMA/133
[ 160.624461] ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 160.647941] ata2.00: configured for UDMA/133

linux with latest device tree: see previous post.
Re: debian on synology ds214 - periphery issues
November 21, 2022 08:41PM
Hi Martin,

> On linux the following lines are in the dmesg
> output:
>
>
Quote

> [ 3.286187][ T1] scsi host0: sata_mv
> [ 3.291223][ T1] scsi host1: sata_mv
> [ 3.295841][ T1] ata1: SATA max UDMA/133 irq
> 37
> [ 3.300665][ T1] ata2: SATA max UDMA/133 irq
> 37
> [ 3.636269][ T674] ata1: SATA link down
> (SStatus 0 SControl F300)
> [ 3.969677][ T679] ata2: SATA link down
> (SStatus 0 SControl F300)
>

Please always post a complete serial console log. At the minum, I would like to see the whole dmesg log. Excerpts obmit a lot of rlevant info.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 22, 2022 02:20PM
Hi bodhi,

Interesting fact: the drive is correctly powered up after ata2 link down message. This is the same behavior as on stock image. So at least this part seems to be ok.

Unplugging network during dhcp request leads to the following messages:
Quote

Listening on LPF/eth0/00:50:43:02:02:00
Sending on LPF/eth0/00:50:43:02:02:00
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
[ 49.275479][ T71] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 49.284091][ T71] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 59.636616][ T71] mvneta f1070000.ethernet eth0: TIMEOUT for TX stopped status=0x0000ff19
[ 69.649818][ T71] mvneta f1070000.ethernet eth0: TX FIFO empty timeout status=0x00010001
[ 69.658687][ T71] mvneta f1070000.ethernet eth0: Link is Down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.

so apparently link detection is correct.

full dmesg without messing with network cable (plugged in):
U-Boot 2023.01-rc1 (Nov 22 2022 - 20:05:42 +0000)

SoC:   MV78230-B0 at 1066 MHz
DRAM:  512 MiB (533 MHz, 32-bit, ECC not enabled)
Core:  23 devices, 18 uclasses, devicetree: separate
Loading Environment from SPIFlash... SF: Detected n25q064 with page size 256 Bytes, erase size 4 KiB, total 8 MiB
OK
In:    serial@12000
Out:   serial@12000
Err:   serial@12000
Model: Synology DS214
Board: DS414
Net:   eth0: ethernet@70000
=> run startusb
Bus usb@50000: USB EHCI 1.00
Bus xhci_pci: Register 4000440 NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus usb@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
=> run loadimage
5344792 bytes read in 129 ms (39.5 MiB/s)
=> run loadinitrd
10482596 bytes read in 245 ms (40.8 MiB/s)
=> run doboot
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-6.0.8-mvebu-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5344728 Bytes = 5.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 08000000 ...
   Image Name:   initramfs-6.0.8--mvebu-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    10482532 Bytes = 10 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Working FDT set to 0
   Loading Kernel Image

Starting kernel ...

DTB:0x0051C9E8 (0x000043F0)
C:0x000080E0-0x00520E60->0x0127E700-0x01797480
DTB:0x01793008 (0x0000445F)
Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.0.8-mvebu-tld-1 (root@568e083df998) (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT Sun Nov 20 09:43:48 UTC 2022
[    0.000000][    T0] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: div instructions available: patching division code
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Synology DS214
[    0.000000][    T0] Memory policy: Data cache writealloc
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0]   HighMem  empty
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000][    T0] percpu: Embedded 17 pages/cpu s38996 r8192 d22444 u69632
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[    0.000000][    T0] Kernel command line: "console=ttyS0,115200 root=/dev/sda1 rootdelay=5 $mtdparts earlyprintk=serial"
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 488872K/524288K available (11264K kernel code, 1526K rwdata, 3516K rodata, 1024K init, 468K bss, 35416K reserved, 0K cma-reserved, 0K highmem)
[    0.000000][    T0] trace event string verifier disabled
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000][    T0]  Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0]  Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] L2C: DT/platform modifies aux control register: 0x1a096b00 -> 0x1a096b02
[    0.000000][    T0] Aurora cache controller enabled, 16 ways, 1024 kB
[    0.000000][    T0] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a096b02
[    0.000000][    T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000][    T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval)
[    0.000000][    T0] Switching to timer-based delay loop, resolution 40ns
[    0.000001][    T0] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[    0.000018][    T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.001253][    T0] Console: colour dummy device 80x30
[    0.001297][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[    0.001314][    T0] pid_max: default: 32768 minimum: 301
[    0.001649][    T0] LSM: Security Framework initializing
[    0.001851][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001868][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.002996][    T0] CPU: Testing write buffer coherency: ok
[    0.003361][    T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.004870][    T1] cblist_init_generic: Setting adjustable number of callback queues.
[    0.004882][    T1] cblist_init_generic: Setting shift to 1 and lim to 1.
[    0.005046][    T1] cblist_init_generic: Setting shift to 1 and lim to 1.
[    0.005214][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.005576][    T1] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x2
[    0.005718][    T1] mvebu-pmsu: Initializing Power Management Service Unit
[    0.005973][    T1] rcu: Hierarchical SRCU implementation.
[    0.005980][    T1] rcu:     Max phase no-delay instances is 1000.
[    0.007106][    T1] smp: Bringing up secondary CPUs ...
[    0.008115][    T1] Booting CPU 1
[    0.008547][    T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.018634][    T1] smp: Brought up 1 node, 2 CPUs
[    0.018647][    T1] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[    0.018656][    T1] CPU: All CPU(s) started in SVC mode.
[    0.019362][    T1] devtmpfs: initialized
[    0.025101][    T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.025482][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.025521][    T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    0.025735][    T1] prandom: seed boundary self test passed
[    0.028555][    T1] prandom: 100 self tests passed
[    0.028614][    T1] pinctrl core: initialized pinctrl subsystem
[    0.030259][    T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.030642][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.031706][    T1] audit: initializing netlink subsys (disabled)
[    0.032069][   T24] audit: type=2000 audit(0.030:1): state=initialized audit_enabled=0 res=1
[    0.032775][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.033125][    T1] cpuidle: using governor ladder
[    0.033170][    T1] cpuidle: using governor menu
[    0.033248][   T16] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[    0.033259][   T16] hw-breakpoint: CPU 0 failed to disable vector catch
[    0.033296][   T17] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[    0.240149][    T1] raid6: int32x8  gen()   188 MB/s
[    0.410120][    T1] raid6: int32x4  gen()   203 MB/s
[    0.580097][    T1] raid6: int32x2  gen()   340 MB/s
[    0.750083][    T1] raid6: int32x1  gen()   343 MB/s
[    0.750093][    T1] raid6: using algorithm int32x1 gen() 343 MB/s
[    0.920084][    T1] raid6: .... xor() 169 MB/s, rmw enabled
[    0.920092][    T1] raid6: using intx1 recovery algorithm
[    0.921325][    T1] SCSI subsystem initialized
[    0.921919][    T1] usbcore: registered new interface driver usbfs
[    0.921978][    T1] usbcore: registered new interface driver hub
[    0.922028][    T1] usbcore: registered new device driver usb
[    0.922399][    T1] pps_core: LinuxPPS API ver. 1 registered
[    0.922407][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.922431][    T1] PTP clock support registered
[    0.924093][    T1] vgaarb: loaded
[    0.924694][    T1] clocksource: Switched to clocksource armada_370_xp_clocksource
[    0.925521][    T1] VFS: Disk quotas dquot_6.6.0
[    0.925627][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.938964][    T1] NET: Registered PF_INET protocol family
[    0.939187][    T1] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.940492][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.940603][    T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.940636][    T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.940681][    T1] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.940725][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    0.940955][    T1] MPTCP token hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.941035][    T1] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.941061][    T1] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.941324][    T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.942139][    T1] RPC: Registered named UNIX socket transport module.
[    0.942149][    T1] RPC: Registered udp transport module.
[    0.942155][    T1] RPC: Registered tcp transport module.
[    0.942160][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.942172][    T1] PCI: CLS 0 bytes, default 64
[    0.942253][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.942619][    T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.945191][    T8] Trying to unpack rootfs image as initramfs...
[    1.335041][    T1] Initialise system trusted keyrings
[    1.335133][    T1] Key type blacklist registered
[    1.336080][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    1.336296][    T1] zbud: loaded
[    1.338276][    T1] NFS: Registering the id_resolver key type
[    1.338330][    T1] Key type id_resolver registered
[    1.338337][    T1] Key type id_legacy registered
[    1.338383][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.338399][    T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.427610][    T1] xor: measuring software checksum speed
[    1.436813][    T1]    arm4regs        :  1076 MB/sec
[    1.449804][    T1]    8regs           :   769 MB/sec
[    1.459984][    T1]    32regs          :   972 MB/sec
[    1.459998][    T1] xor: using function: arm4regs (1076 MB/sec)
[    1.460020][    T1] async_tx: api initialized (async)
[    1.460034][    T1] Key type asymmetric registered
[    1.460042][    T1] Asymmetric key parser 'x509' registered
[    1.548514][    T8] Freeing initrd memory: 10240K
[    1.572806][    T1] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[    1.573028][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.573221][    T1] io scheduler bfq registered
[    1.577441][    T1] armada-xp-pinctrl f1018000.pin-ctrl: registered pinctrl driver
[    1.579777][    T1] debugfs: Directory 'f1018100.gpio' with parent 'regmap' already present!
[    1.580966][    T1] debugfs: Directory 'f1018140.gpio' with parent 'regmap' already present!
[    1.581934][    T1] mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges:
[    1.582014][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    1.582056][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    1.582094][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0x00f1048000..0x00f1049fff -> 0x0000048000
[    1.582132][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0x00f104c000..0x00f104dfff -> 0x000004c000
[    1.582170][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    1.582207][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.582243][    T1] mvebu-pcie soc:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    1.582280][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.582316][    T1] mvebu-pcie soc:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    1.582351][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.582387][    T1] mvebu-pcie soc:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[    1.582424][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.582459][    T1] mvebu-pcie soc:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[    1.582495][    T1] mvebu-pcie soc:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[    1.582520][    T1] mvebu-pcie soc:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[    1.582607][    T1] mvebu-pcie soc:pcie@82000000: pcie0.0: legacy INTx interrupts cannot be masked individually, /soc/pcie@82000000/pcie@1,0 does not contain intx interrupt
[    1.582954][    T1] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[    1.582970][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.582988][    T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    1.583002][    T1] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    1.583016][    T1] pci_bus 0000:00: root bus resource [mem 0xf1048000-0xf1049fff] (bus address [0x00048000-0x00049fff])
[    1.583030][    T1] pci_bus 0000:00: root bus resource [mem 0xf104c000-0xf104dfff] (bus address [0x0004c000-0x0004dfff])
[    1.583043][    T1] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    1.583055][    T1] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[    1.583066][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    1.583209][    T1] pci 0000:00:01.0: [11ab:7823] type 01 class 0x060400
[    1.586588][    T1] PCI: bus0: Fast back to back transfers disabled
[    1.586615][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.587039][    T1] pci 0000:01:00.0: [1b6f:7023] type 00 class 0x0c0330
[    1.587080][    T1] pci 0000:01:00.0: reg 0x10: [mem 0xc0000000-0xc0007fff 64bit]
[    1.587148][    T1] pci 0000:01:00.0: enabling Extended Tags
[    1.587245][    T1] pci 0000:01:00.0: supports D1 D2
[    1.587255][    T1] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
[    1.587732][    T1] pci 0000:00:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[    1.614870][    T1] PCI: bus1: Fast back to back transfers disabled
[    1.614892][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.614946][    T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff]
[    1.614965][    T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8007fff 64bit]
[    1.614989][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.615005][    T1] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    1.615097][    T1] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    1.615993][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.685949][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.689922][    T1] mv_xor f10f0900.xor: Marvell shared XOR driver
[    1.755957][    T1] mv_xor f10f0900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.901863][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.906310][    T1] printk: console [ttyS0] disabled
[    1.926513][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 35, base_baud = 15625000) is a 16550A
[    3.255879][    T1] printk: console [ttyS0] enabled
[    3.282760][    T1] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 36, base_baud = 15625000) is a 16550A
[    3.296625][    T1] sata_mv f10a0000.sata: slots 32 ports 2
[    3.305178][    T1] scsi host0: sata_mv
[    3.310257][    T1] scsi host1: sata_mv
[    3.314670][    T1] ata1: SATA max UDMA/133 irq 37
[    3.319577][    T1] ata2: SATA max UDMA/133 irq 37
[    3.328401][    T1] spi-nor spi0.0: n25q064 (8192 Kbytes)
[    3.334011][    T1] 6 fixed-partitions partitions found on MTD device spi0.0
[    3.341134][    T1] Creating 6 MTD partitions on "spi0.0":
[    3.346677][    T1] 0x000000000000-0x0000000d0000 : "RedBoot"
[    3.354922][    T1] 0x0000000d0000-0x0000003a0000 : "zImage"
[    3.362924][    T1] 0x0000003a0000-0x0000007d0000 : "rd.gz"
[    3.370863][    T1] 0x0000007d0000-0x0000007e0000 : "vendor"
[    3.378927][    T1] 0x0000007e0000-0x0000007f0000 : "RedBoot config"
[    3.387659][    T1] 0x0000007f0000-0x000000800000 : "FIS directory"
[    3.397081][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    3.405726][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    3.437600][    T1] hwmon hwmon0: temp1_input not attached to any thermal zone
[    3.450717][    T1] mvneta f1070000.ethernet eth0: Using hardware mac address 00:50:43:02:02:00
[    3.460724][    T1] sky2: driver version 1.30
[    3.465557][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.472840][    T1] ehci-pci: EHCI PCI platform driver
[    3.478227][    T1] ehci-orion: EHCI orion driver
[    3.483225][    T1] orion-ehci f1050000.usb: EHCI Host Controller
[    3.489412][    T1] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
[    3.497876][    T1] orion-ehci f1050000.usb: irq 39, io mem 0xf1050000
[    3.534747][    T1] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
[    3.541826][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.00
[    3.550866][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.558839][    T1] usb usb1: Product: EHCI Host Controller
[    3.564437][    T1] usb usb1: Manufacturer: Linux 6.0.8-mvebu-tld-1 ehci_hcd
[    3.571530][    T1] usb usb1: SerialNumber: f1050000.usb
[    3.577977][    T1] hub 1-0:1.0: USB hub found
[    3.582497][    T1] hub 1-0:1.0: 1 port detected
[    3.589048][    T1] usbcore: registered new interface driver usblp
[    3.595524][    T1] usbcore: registered new interface driver usb-storage
[    3.603086][    T1] mousedev: PS/2 mouse device common for all mice
[    3.611168][    T1] i2c_dev: i2c /dev entries driver
[    3.617173][    T1] mv64xxx_i2c f1011000.i2c: can't get pinctrl, bus recovery not supported
[    3.631290][    T1] rtc-s35390a 0-0030: registered as rtc0
[    3.637165][    T1] rtc-s35390a 0-0030: setting system clock to 2022-11-22T20:14:58 UTC (1669148098)
[    3.656414][  T674] ata1: SATA link down (SStatus 0 SControl F300)
[    3.750904][    T1] orion_wdt: Initial timeout 171 sec
[    3.757738][    T1] device-mapper: uevent: version 1.0.3
[    3.763488][    T1] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[    3.773177][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    3.780464][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    3.787820][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    3.795247][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    3.802065][    T1] device-mapper: raid: Loading target version 1.15.1
[    3.810091][    T1] debugfs: Directory 'cpu1' with parent 'opp' already present!
[    3.820351][    T1] marvell-cesa f1090000.crypto: CESA device successfully registered
[    3.828971][    T1] hid: raw HID events driver (C) Jiri Kosina
[    3.835739][    T1] usbcore: registered new interface driver usbhid
[    3.842042][    T1] usbhid: USB HID core driver
[    3.847374][    T1] drop_monitor: Initializing network drop monitor service
[    3.855235][    T1] NET: Registered PF_INET6 protocol family
[    3.862592][    T1] Segment Routing with IPv6
[    3.867040][    T1] RPL Segment Routing with IPv6
[    3.871885][    T1] In-situ OAM (IOAM) with IPv6
[    3.876671][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.885812][    T1] NET: Registered PF_PACKET protocol family
[    3.891852][    T1] 8021q: 802.1Q VLAN Support v1.8
[    3.896866][    T1] Key type dns_resolver registered
[    3.901941][    T1] ThumbEE CPU extension supported.
[    3.906995][    T1] Registering SWP/SWPB emulation handler
[    3.913400][    T1] registered taskstats version 1
[    3.918266][    T1] Loading compiled-in X.509 certificates
[    3.924475][    T1] zswap: loaded using pool lzo/zbud
[    3.930297][    T1] Key type .fscrypt registered
[    3.934985][    T1] Key type fscrypt-provisioning registered
[    3.942874][    T1] Key type big_key registered
[    3.970403][    T1] Key type encrypted registered
[    3.986795][  T679] ata2: SATA link down (SStatus 0 SControl F300)
[   24.801912][    T1] Freeing unused kernel image (initmem) memory: 1024K
[   24.847346][    T1] Checked W+X mappings: passed, no W+X pages found
[   24.853763][    T1] Run /init as init process
Loading, please wait...
Starting version 247.3-7+deb11u1
[   26.737529][ T1001] xhci_hcd 0000:01:00.0: xHCI Host Controller
[   26.744834][ T1001] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[   26.754380][ T1001] xhci_hcd 0000:01:00.0: hcc params 0x040050a7 hci version 0x100 quirks 0x0000000000080490
[   26.769278][ T1001] xhci_hcd 0000:01:00.0: xHCI Host Controller
[   26.786993][ T1001] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[   26.819398][ T1001] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[   26.850296][ T1001] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.00
[   26.873011][ T1001] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   26.885818][ T1001] usb usb2: Product: xHCI Host Controller
[   26.903638][ T1001] usb usb2: Manufacturer: Linux 6.0.8-mvebu-tld-1 xhci-hcd
[   26.916450][ T1001] usb usb2: SerialNumber: 0000:01:00.0
[   26.928947][ T1001] hub 2-0:1.0: USB hub found
[   26.935903][ T1001] hub 2-0:1.0: 2 ports detected
[   26.944196][ T1001] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[   26.959734][ T1001] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.00
[   26.975716][ T1001] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   26.990275][ T1001] usb usb3: Product: xHCI Host Controller
[   27.006743][ T1001] usb usb3: Manufacturer: Linux 6.0.8-mvebu-tld-1 xhci-hcd
[   27.017657][ T1001] usb usb3: SerialNumber: 0000:01:00.0
[   27.032526][ T1001] hub 3-0:1.0: USB hub found
[   27.049005][ T1001] hub 3-0:1.0: 2 ports detected
[   27.224895][  T970] usb 2-2: new high-speed USB device number 2 using xhci_hcd
[   27.472254][  T970] usb 2-2: New USB device found, idVendor=0781, idProduct=55b0, bcdDevice= 3.05
[   27.485442][  T970] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[   27.493341][  T970] usb 2-2: Product: Portable SSD
[   27.501190][  T970] usb 2-2: Manufacturer: SanDisk
[   27.508601][  T970] usb 2-2: SerialNumber: 32323332315A343031383630
[   27.923894][ T1001] scsi host2: uas
[   27.929169][ T1001] usbcore: registered new interface driver uas
[   27.930496][   T10] scsi 2:0:0:0: Direct-Access     SanDisk  Portable SSD     0305 PQ: 0 ANSI: 6
[   27.955939][   T10] scsi 2:0:0:1: Enclosure         SanDisk  SES Device       0305 PQ: 0 ANSI: 6
[   27.992614][   T35] sd 2:0:0:0: [sda] 937701376 512-byte logical blocks: (480 GB/447 GiB)
[   28.001113][   T35] sd 2:0:0:0: [sda] 4096-byte physical blocks
[   28.007814][   T35] sd 2:0:0:0: [sda] Write Protect is off
[   28.014436][   T35] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   28.024404][   T35] sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[   28.031691][   T35] sd 2:0:0:0: [sda] Optimal transfer size 1048576 bytes
[   28.055206][   T35]  sda: sda1 sda2 sda3
[   28.061932][   T35] sd 2:0:0:0: [sda] Attached SCSI disk
[   28.106579][  T997] scsi 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
[   28.113523][  T997] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[   28.134767][  T997] scsi 2:0:0:1: Failed to bind enclosure -19
[   28.140757][  T997] ses 2:0:0:1: Attached Enclosure device
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sda1] fsck.ext2 -a -C0 /dev/sda1 
/dev/sda1: clean, 28300/1310720 files, 695468/5242880 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.96 booting
Using makefile-style concurrent boot in runlevel S.
Setting hostname to 'debian'...done.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...[   38.068539][ T1212] sd 2:0:0:0: Attached scsi generic sg0 type 0
[   38.087662][ T1212] ses 2:0:0:1: Attached scsi generic sg1 type 13
done.
Not activating swap on swapfile. ... (warning).
[   40.450596][ T1353] ext2 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
Will now check all file systems.
Checking all file systems.
/dev/sda1 is mounted
Done checking file systems.
Log is being saved in /var/log/fsck/checkfs if that location is writable.
Cleaning up temporary files...Cleaning /tmp...done.
 /tmp.
[   43.243501][ T1640] Adding 1048572k swap on /swapfile.  Priority:-2 extents:16 across:2954944k SSFS
Will now mount local filesystems:.
Will now activate swapfile swap, if any:swapon: /swapfile: found signature [pagesize=4096, signature=swap]
swapon: /swapfile: pagesize=4096, swapsize=1073741824, devsize=1073741824
swapon /swapfile
done.
Checking minimum space in /tmp...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
[   45.574763][    C1] random: crng init done
Initializing random number generator...done.
[   46.116060][ T1767] mvneta f1070000.ethernet eth0: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[   46.129875][ T1767] mvneta f1070000.ethernet eth0: configuring for phy/rgmii-id link mode
Configuring network interfaces...Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:50:43:02:02:00
Sending on   LPF/eth0/00:50:43:02:02:00
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
[   49.275838][   T32] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   49.284464][   T32] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
Starting RPC port mapper daemon: rpcbind.
Starting NFS common utilities: statd idmapd.
Cleaning up temporary files....
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Not starting fancontrol; run pwmconfig first. ... (warning).
Not starting NFS kernel daemon: no exports. ... (warning).
Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1918 (syslogd)
.
Starting periodic command scheduler: cron.
Starting NTP server: ntpd.
Starting system message bus: dbus.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting OpenBSD Secure Shell server: sshd.
Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1958 (klogd)
.
Running local boot scripts (/etc/rc.local)
Cannot read environment, using default
Cannot read default environment from file
<13>Nov 22 12:16:47 root[2043]: Cannot read u-boot env ethaddr
.

Debian GNU/Linux 11 debian ttyS0

debian login: 
Re: debian on synology ds214 - periphery issues
November 22, 2022 02:22PM
i did a cat /proc/interrupts as suggested by a friend:


root@debian:~# cat /proc/interrupts 
           CPU0       CPU1       
 24:       5120      10230      MPIC   5 Level     armada_370_xp_per_cpu_tick
 25:          0          0      MPIC   3 Level     arm-pmu
 33:          2          0      MPIC  51 Level     f1060900.xor
 34:          2          0      MPIC  94 Level     f10f0900.xor
 35:        381          0      MPIC  41 Level     ttyS0
 37:          0          0      MPIC  55 Level     sata_mv[f10a0000.sata]
 38:         13         20      MPIC   8 Level     eth0
 39:          0          0      MPIC  45 Level     ehci_hcd:usb1
 40:       1548          0      MPIC  31 Level     mv64xxx_i2c
 41:          0          0      MPIC  48 Level     f1090000.crypto
 42:          0          0      MPIC  49 Level     f1090000.crypto
 44:       5116          0  MPIC MSI 524288 Edge      xhci_hcd
IPI0:          0          0  CPU wakeup interrupts
IPI1:          0          0  Timer broadcast interrupts
IPI2:        418        740  Rescheduling interrupts
IPI3:       2248       5027  Function call interrupts
IPI4:          0          0  CPU stop interrupts
IPI5:          0          0  IRQ work interrupts
IPI6:          0          0  completion interrupts
Err:          0

interrupt 37 seems to not trigger...
Re: debian on synology ds214 - periphery issues
November 22, 2022 02:34PM
the corresponding output from stock:
lonestar@ds214:/$ cat /proc/interrupts 
           CPU0       CPU1       
  5:       4666       4188   axp_irq  axp_local_clockevent
  8:         26          0   axp_irq  mv_eth
 31:         92          0   axp_irq  mv64xxx_i2c
 41:       1188          0   axp_irq  serial
 42:          1          0   axp_irq  serial
 45:          0          0   axp_irq  ehci_hcd:usb1
 46:          0          0   axp_irq  ehci_hcd:usb2
 48:          0          0   axp_irq  cesa0
 49:          0          0   axp_irq  cesa1
 55:       6882          0   axp_irq  sata_mv
 58:        196          0   axp_irq  
107:          0          0   axp_irq  axp-temp
IPI0:          0          0  Timer broadcast interrupts
IPI1:       4255       5050  Rescheduling interrupts
IPI2:          0          0  Function call interrupts
IPI3:         74        118  Single function call interrupts
IPI4:          0          0  CPU stop interrupts
Err:          0
Re: debian on synology ds214 - periphery issues
November 22, 2022 03:40PM
lonestar,

Quote

Interesting fact: the drive is correctly powered up after ata2 link down message. This is the same behavior as on stock image. So at least this part seems to be ok.

So did any of the 2 SATA drives power up?

If none of the SATA drives is up, at this point, we need to find out if 2 out of these 4 regulators can be used. IOW, is the GPIO in each one is correct? or the ds214 uses different GPIOs for 2 SATA ports. Searching in GPL source might be faster to the solution.


regulators {
		compatible = "simple-bus";
		#address-cells = <1>;
		#size-cells = <0>;
		pinctrl-0 = <&sata1_pwr_pin &sata2_pwr_pin
			     &sata3_pwr_pin &sata4_pwr_pin>;
		pinctrl-names = "default";

		sata1_regulator: sata1-regulator@1 {
			compatible = "regulator-fixed";
			reg = <1>;
			regulator-name = "SATA1 Power";
			regulator-min-microvolt = <5000000>;
			regulator-max-microvolt = <5000000>;
			startup-delay-us = <2000000>;
			enable-active-high;
			regulator-always-on;
			regulator-boot-on;
			gpio = <&gpio1 10 GPIO_ACTIVE_HIGH>;
		};

		sata2_regulator: sata2-regulator@2 {
			compatible = "regulator-fixed";
			reg = <2>;
			regulator-name = "SATA2 Power";
			regulator-min-microvolt = <5000000>;
			regulator-max-microvolt = <5000000>;
			startup-delay-us = <4000000>;
			enable-active-high;
			regulator-always-on;
			regulator-boot-on;
			gpio = <&gpio1 12 GPIO_ACTIVE_HIGH>;
		};

		sata3_regulator: sata3-regulator@3 {
			compatible = "regulator-fixed";
			reg = <3>;
			regulator-name = "SATA3 Power";
			regulator-min-microvolt = <5000000>;
			regulator-max-microvolt = <5000000>;
			startup-delay-us = <6000000>;
			enable-active-high;
			regulator-always-on;
			regulator-boot-on;
			gpio = <&gpio1 13 GPIO_ACTIVE_HIGH>;
		};

		sata4_regulator: sata4-regulator@4 {
			compatible = "regulator-fixed";
			reg = <4>;
			regulator-name = "SATA4 Power";
			regulator-min-microvolt = <5000000>;
			regulator-max-microvolt = <5000000>;
			startup-delay-us = <8000000>;
			enable-active-high;
			regulator-always-on;
			regulator-boot-on;
			gpio = <&gpio1 14 GPIO_ACTIVE_HIGH>;
		};
	};

Or just by trial and error. Remove all 4 and add in one by one. Pretend that there is only one HDD.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 22, 2022 07:00PM
lonestar,

So I've confirmed: in the GPL, the GPIOs 42, 44 are for SATA 1 and 2.

Try this attached pacth (removed the other 2 SATA ports and their associated nodes).

-bodhi
===========================
Forum Wiki
bodhi's corner
Attachments:
open | download - armada-xp-synology-ds214.dts.patch (2.9 KB)
Re: debian on synology ds214 - periphery issues
November 23, 2022 03:11PM
Hi bodhi,

SATA 1 regulator works correctly.
For SATA 2 even when all are configured the disk does not spin up (previously I only tested with one disk).

I will have to do further tests, but it likely won't happen before the weekend.

thanks,
Martin
Re: debian on synology ds214 - periphery issues
November 23, 2022 04:39PM
Hi Martin,

> SATA 1 regulator works correctly.

Cool!

> For SATA 2 even when all are configured the disk
> does not spin up (previously I only tested with
> one disk).

That's a bumer! u-boot GPL source is quite clear about the both SATA GPIO numbers. I'll look at the DTS to see if there is any typo.

>
> I will have to do further tests, but it likely
> won't happen before the weekend.

Try only 1 HDD in the 2nd SATA slot.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 26, 2022 09:37AM
Hi bodhi,

I did some further tests now with two different disks:
Disk1:
- spins up on sata 1 when link down is shown, but link never goes up
- spins up on sata 2 before u-boot loads and never stops

Disk2:
- doesn't spin up on any of the two sata ports.

Note that both disks work in stock image.

This looks to me that this is not just a device tree issue, but maybe some timeout problem or missing initialization in one of the drivers.

I attach a log of Disk2 when not spinning up. Though nothing much to see there (at least for me)

thanks,
Martin
Attachments:
open | download - dmesg-nospin.txt (30.7 KB)
Re: debian on synology ds214 - periphery issues
November 26, 2022 03:41PM
Martin,

What type of HDD for disk 1 and 2? 2.5", or 3.5" HDD?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
November 27, 2022 01:56AM
Hi bodhi,

they are both 3.5" HDDs

regards,
Martin
Re: debian on synology ds214 - periphery issues
November 28, 2022 06:13PM
Martin,

Try this patch to see if both SATA drives will be brought up.

-bodhi
===========================
Forum Wiki
bodhi's corner
Attachments:
open | download - armada-xp-synology-ds214.dts.patch (4.4 KB)
Re: debian on synology ds214 - periphery issues
November 29, 2022 01:48PM
Hi bodhi,

a very morising idea, yet no improvement so far.

see attached dmesg.txt. Added a dump of sys/class/regulators, to confirm that the setting arrived at the kernel.

Test was done with
- 2 disks (see dmesg),
- one disk that failed to spin up on any of the two sata ports alone in both of the ports.

results: exactly the same behavior as before.

thanks,
Martin
Attachments:
open | download - dmesg-12v-2disks.txt (42.7 KB)
Re: debian on synology ds214 - periphery issues
November 30, 2022 05:21PM
Martin,


> - one disk that failed to spin up on any of the
> two sata ports alone in both of the ports.

This is really weird. If a specific port works for one 3.5" HDD, it should work for another 3.5" HDD.

With stock u-boot, can you see both HDDs?

ide reset

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: debian on synology ds214 - periphery issues
December 01, 2022 12:55PM
Hi bodhi,

a maybe important difference is that the disk that does not spin up at all in the self-built u-boot is a 7200 rpm disk. The other one is a 5400 rpm disk.

I tested with stock u-boot:
ide reset found the 7200 disk in sata 2. but not the 5400 drive in sata 1.

Then I exchanged the two disks:
it found the 5400 disk in sata 2 but not the 7200 in sata 1.

This was reproducible.

Attached the u-boot log.
Attachments:
open | download - u-boot.log (5.9 KB)
Re: debian on synology ds214 - periphery issues
December 01, 2022 03:01PM
Martin,

> I tested with stock u-boot:
> ide reset found the 7200 disk in sata 2. but not
> the 5400 drive in sata 1.
>
> Then I exchanged the two disks:
> it found the 5400 disk in sata 2 but not the 7200
> in sata 1.

This means Syno u-boot does not power up the SATA 1 slot. So boot into Debian and verify that same SATA 2 slot is actually working.

While you are in u-boot dump these memory locations.

md.l f1018000 8
md.l f1018100 1
md.l f1018140 1

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: