NVME drives not working (although they should?)

Post Reply
User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

NVME drives not working (although they should?)

Post by Sjonnie »

On request of Moderator Odroid I open a seperate topic on NVME drives for the M1 board that are not working. So I copied the message I placed in the "working NVME drives" thread below:
Hi All,

Been a while since I have been hanging around here. After some very good adventures with a C2 I started a new adventure with a M1/8GB. I had two NVME's lying around of which I hoped they would work. They don't! So in order to prevent others from buying the below mentioned drives I thought I'd mention them here (Why isn't there a thread about not working NVME's?)

So *NOT WORKING*

1. Brand : Toshiba
2. Model :THNSN526GPU7
3. Capacity : 256 GB
4. NVMe controller and firmware version : unknown
5. Additional comments : OEM partnumber: HP 829093-005
6. Price and where to buy : don't!

1. Brand : Samsung
2. Model :SM961 / MZ-VKW5120
3. Capacity : 512 GB
4. NVMe controller and firmware version : unknown
5. Additional comments : OEM partnumber: HP 861960-003
6. Price and where to buy : don't

Again: these drives are *NOT WORKING*

Bought a Kingston A2000 from the compatibility list, hoping I can get the M1 running :)
I tried to install the Toshiba drive using petitboot with net install of Ubuntu 22.04, 20.04 and Debian Bullseye. In all cases the drive is not found during install.

The Samsung was found during net install of Ubuntu 22.04, 20.04 and Debian Bullseye. But during installation of the base system the drive failed. With 22.04 and Bullseye it failed at 6%, with 20.04 it failed at 48% (IIRC). Mod asked for output of dmesg but I can't get that info since install does not complete.

I tried to image the drive using a micro USB cable connected to my PC (Mint Linux) but I couldn't get past the CLI and was unable to install. Felt a bit noobish about that but gave up on the drives and bought a Kingston A2000 (which is seriously delayed :( ) and I just ordered a Gigabyte GP-GSM2NE3256GNTD which should arrive tomorrow.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Copied the image of Ubuntu server 20.04 which I downloaded from HK website. This does seem to be working:

Output of dmesg:

Code: Select all

odroid@server:~$ dmesg
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 4.19.219-odroid-arm64 (debian-kernel@lists.debian.org) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-6ubuntu2), GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP Fri, 27 May 2022 03:16:46 +0000
[    0.000000] Machine model: Hardkernel ODROID-M1
[    0.000000] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '')
[    0.000000] bootconsole [uart8250] enabled
[    0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@00000000': base 0x0000000000000000, size 0 MiB
[    0.000000] cma: Reserved 16 MiB at 0x00000000e8c00000
[    0.000000] On node 0 totalpages: 1968203
[    0.000000]   DMA32 zone: 14938 pages used for memmap
[    0.000000]   DMA32 zone: 0 pages reserved
[    0.000000]   DMA32 zone: 955975 pages, LIFO batch:63
[    0.000000]   Normal zone: 16382 pages used for memmap
[    0.000000]   Normal zone: 1012228 pages, LIFO batch:63
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 24 pages/cpu s58344 r8192 d31768 u98304
[    0.000000] pcpu-alloc: s58344 r8192 d31768 u98304 alloc=24*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: Virtualization Host Extensions
[    0.000000] CPU features: detected: Speculative Store Bypassing Safe (SSBS)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1936883
[    0.000000] Kernel command line: root=/dev/nvme0n1p2 quiet splash earlycon=uart8250,mmio32,0xfe660000 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x20000@0xe0000(env),0x200000@0x100000(uboot),0x100000@0x300000(splash),0xc00000@0x400000(firmware) console=tty1 
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 0xe4c00000-0xe8c00000] (64MB)
[    0.000000] Memory: 7618356K/7872812K available (10110K kernel code, 1350K rwdata, 3616K rodata, 1280K init, 479K bss, 238072K reserved, 16384K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 38725 entries in 152 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: 	RCU event tracing is enabled.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] ITS [mem 0xfd440000-0xfd45ffff]
[    0.000000] ITS@0x00000000fd440000: allocated 8192 Devices @ee2a0000 (indirect, esz 8, psz 64K, shr 0)
[    0.000000] ITS@0x00000000fd440000: allocated 32768 Interrupt Collections @ee2b0000 (flat, esz 2, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GIC: using LPI property table @0x000000000a520000
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000
[    0.000000] CPU0: Booted with LPIs enabled, memory probably corrupted
[    0.000000] CPU0: Failed to disable LPIs
[    0.000000] random: random: get_random_bytes called from start_kernel+0x368/0x500 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.001423] Console: colour dummy device 80x25
[    0.001435] console [tty1] enabled
[    0.001440] bootconsole [uart8250] disabled
[    0.001482] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=80000)
[    0.001493] pid_max: default: 32768 minimum: 301
[    0.001647] Security Framework initialized
[    0.001660] AppArmor: AppArmor disabled by boot time parameter
[    0.001755] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.001803] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.003833] ASID allocator initialised with 32768 entries
[    0.004001] rcu: Hierarchical SRCU implementation.
[    0.005999] Platform MSI: interrupt-controller@fd440000 domain created
[    0.006558] PCI/MSI: /interrupt-controller@fd400000/interrupt-controller@fd440000 domain created
[    0.007371] smp: Bringing up secondary CPUs ...
[    0.008180] Detected VIPT I-cache on CPU1
[    0.008219] GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000
[    0.008229] CPU1: Booted with LPIs enabled, memory probably corrupted
[    0.008234] CPU1: Failed to disable LPIs
[    0.008276] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[    0.009204] Detected VIPT I-cache on CPU2
[    0.009237] GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000
[    0.009246] CPU2: Booted with LPIs enabled, memory probably corrupted
[    0.009251] CPU2: Failed to disable LPIs
[    0.009281] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]
[    0.010252] Detected VIPT I-cache on CPU3
[    0.010284] GICv3: CPU3: found redistributor 300 region 0:0x00000000fd4c0000
[    0.010292] CPU3: Booted with LPIs enabled, memory probably corrupted
[    0.010297] CPU3: Failed to disable LPIs
[    0.010326] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]
[    0.010461] smp: Brought up 1 node, 4 CPUs
[    0.010506] SMP: Total of 4 processors activated.
[    0.010513] CPU features: detected: GIC system register CPU interface
[    0.010517] CPU features: detected: Privileged Access Never
[    0.010522] CPU features: detected: LSE atomic instructions
[    0.010525] CPU features: detected: User Access Override
[    0.010529] CPU features: detected: 32-bit EL0 Support
[    0.010534] CPU features: detected: RAS Extension Support
[    0.010701] CPU: All CPU(s) started at EL2
[    0.010730] alternatives: patching kernel code
[    0.016741] devtmpfs: initialized
[    0.047895] Registered cp15_barrier emulation handler
[    0.047911] Registered setend emulation handler
[    0.048229] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
[    0.048248] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.049181] pinctrl core: initialized pinctrl subsystem
[    0.049559] regulator-dummy: no parameters
[    0.050357] NET: Registered protocol family 16
[    0.051027] audit: initializing netlink subsys (disabled)
[    0.051293] audit: type=2000 audit(0.046:1): state=initialized audit_enabled=0 res=1
[    0.054955] cpuidle: using governor menu
[    0.054990] Registered FIQ tty driver
[    0.055431] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.056720] DMA: preallocated 256 KiB pool for atomic allocations
[    0.096213] rockchip-gpio fdd60000.gpio: probed gpio0 (fdd60000.gpio)
[    0.096932] rockchip-gpio fe740000.gpio: probed gpio1 (fe740000.gpio)
[    0.097639] rockchip-gpio fe750000.gpio: probed gpio2 (fe750000.gpio)
[    0.098358] rockchip-gpio fe760000.gpio: probed gpio3 (fe760000.gpio)
[    0.099100] rockchip-gpio fe770000.gpio: probed gpio4 (fe770000.gpio)
[    0.099205] rockchip-pinctrl pinctrl: probed pinctrl
[    0.109658] fbcon: Taking over console
[    0.111051] console [ttyFIQ0] enabled
[    0.111328] Registered fiq debugger ttyFIQ0
[    0.111894] dc_12v: 12000 mV 
[    0.112181] reg-fixed-voltage dc-12v: dc_12v supplying 12000000uV
[    0.112340] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.112354] vcc3v3_sys: supplied by dc_12v
[    0.112364] dc_12v: could not add device link regulator.2 err -2
[    0.112418] vcc3v3_sys: 3300 mV 
[    0.112679] reg-fixed-voltage vcc3v3-sys: vcc3v3_sys supplying 3300000uV
[    0.112821] reg-fixed-voltage vcc5v0-sys: Looking up vin-supply from device tree
[    0.112834] vcc5v0_sys: supplied by dc_12v
[    0.112844] dc_12v: could not add device link regulator.3 err -2
[    0.112897] vcc5v0_sys: 5000 mV 
[    0.113153] reg-fixed-voltage vcc5v0-sys: vcc5v0_sys supplying 5000000uV
[    0.113301] reg-fixed-voltage vcc5v0-usb: Looking up vin-supply from device tree
[    0.113313] vcc5v0_usb: supplied by dc_12v
[    0.113323] dc_12v: could not add device link regulator.4 err -2
[    0.113376] vcc5v0_usb: 5000 mV 
[    0.113606] reg-fixed-voltage vcc5v0-usb: vcc5v0_usb supplying 5000000uV
[    0.113889] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.113904] vcc5v0_host: supplied by vcc5v0_usb
[    0.113915] vcc5v0_usb: could not add device link regulator.5 err -2
[    0.113992] vcc5v0_host: 5000 mV 
[    0.114236] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 5000000uV
[    0.114510] vcc5v0_otg: 5000 mV 
[    0.114701] reg-fixed-voltage vcc5v0-otg-regulator: Looking up vin-supply from device tree
[    0.114715] vcc5v0_otg: supplied by vcc5v0_usb
[    0.114849] reg-fixed-voltage vcc5v0-otg-regulator: vcc5v0_otg supplying 5000000uV
[    0.115003] reg-fixed-voltage pcie30-avdd0v9: Looking up vin-supply from device tree
[    0.115017] pcie30_avdd0v9: supplied by vcc3v3_sys
[    0.115027] vcc3v3_sys: could not add device link regulator.7 err -2
[    0.115086] pcie30_avdd0v9: 900 mV 
[    0.115345] reg-fixed-voltage pcie30-avdd0v9: pcie30_avdd0v9 supplying 900000uV
[    0.115491] reg-fixed-voltage pcie30-avdd1v8: Looking up vin-supply from device tree
[    0.115504] pcie30_avdd1v8: supplied by vcc3v3_sys
[    0.115514] vcc3v3_sys: could not add device link regulator.8 err -2
[    0.115573] pcie30_avdd1v8: 1800 mV 
[    0.115851] reg-fixed-voltage pcie30-avdd1v8: pcie30_avdd1v8 supplying 1800000uV
[    0.116026] vcc3v3_pcie: 3300 mV 
[    0.116220] reg-fixed-voltage gpio-regulator: Looking up vin-supply from device tree
[    0.116233] vcc3v3_pcie: supplied by dc_12v
[    0.116348] reg-fixed-voltage gpio-regulator: vcc3v3_pcie supplying 3300000uV
[    0.117243] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vpu-supply from device tree
[    0.117272] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vpu-supply property in node /power-management@fdd90000/power-controller failed
[    0.117321] rk_iommu fdea0800.iommu: version = 2
[    0.117994] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rga-supply from device tree
[    0.118019] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rga-supply property in node /power-management@fdd90000/power-controller failed
[    0.118064] rk_iommu fded0480.iommu: version = 2
[    0.118544] rk_iommu fdee0800.iommu: version = 2
[    0.119011] rk_iommu fdef0800.iommu: version = 2
[    0.119441] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvenc-supply from device tree
[    0.119465] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvenc-supply property in node /power-management@fdd90000/power-controller failed
[    0.119507] rk_iommu fdf40f00.iommu: version = 2
[    0.119977] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvdec-supply from device tree
[    0.120002] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvdec-supply property in node /power-management@fdd90000/power-controller failed
[    0.120044] rk_iommu fdf80800.iommu: version = 2
[    0.120422] rk_iommu fe043e00.iommu: version = 2
[    0.121463] SCSI subsystem initialized
[    0.121725] usbcore: registered new interface driver usbfs
[    0.121792] usbcore: registered new interface driver hub
[    0.121848] usbcore: registered new device driver usb
[    0.121901] media: Linux media interface: v0.10
[    0.121945] videodev: Linux video capture interface: v2.00
[    0.122039] pps_core: LinuxPPS API ver. 1 registered
[    0.122044] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.122066] PTP clock support registered
[    0.122466] arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
[    0.125163] Advanced Linux Sound Architecture Driver Initialized.
[    0.126019] rockchip-cpuinfo cpuinfo: SoC		: 35682000
[    0.126029] rockchip-cpuinfo cpuinfo: Serial		: f450100cd8558ec3
[    0.126929] clocksource: Switched to clocksource arch_sys_counter
[    0.173483] VFS: Disk quotas dquot_6.6.0
[    0.173609] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.187716] NET: Registered protocol family 2
[    0.188163] IP idents hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.192061] tcp_listen_portaddr_hash hash table entries: 4096 (order: 5, 163840 bytes)
[    0.192245] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[    0.192855] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes)
[    0.194894] TCP: Hash tables configured (established 65536 bind 65536)
[    0.195127] UDP hash table entries: 4096 (order: 6, 393216 bytes)
[    0.195497] UDP-Lite hash table entries: 4096 (order: 6, 393216 bytes)
[    0.196101] NET: Registered protocol family 1
[    0.196390] PCI: CLS 0 bytes, default 64
[    0.197445] Unpacking initramfs...
[    0.803457] Freeing initrd memory: 10188K
[    0.804774] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.807485] Initialise system trusted keyrings
[    0.807734] workingset: timestamp_bits=45 max_order=21 bucket_order=0
[    0.820490] NET: Registered protocol family 38
[    0.820515] Key type asymmetric registered
[    0.820521] Asymmetric key parser 'x509' registered
[    0.820570] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.820578] io scheduler noop registered
[    0.820583] io scheduler deadline registered
[    0.820743] io scheduler cfq registered (default)
[    0.820751] io scheduler mq-deadline registered
[    0.820756] io scheduler kyber registered
[    0.824097] phy phy-fe8a0000.usb2-phy.0: Looking up phy-supply from device tree
[    0.824126] vcc5v0_host: could not add device link phy-fe8a0000.usb2-phy.0 err -2
[    0.824206] phy phy-fe8a0000.usb2-phy.0: Linked as a consumer to regulator.5
[    0.824345] phy phy-fe8a0000.usb2-phy.1: Looking up phy-supply from device tree
[    0.824359] phy phy-fe8a0000.usb2-phy.1: Looking up phy-supply property in node /usb2-phy@fe8a0000/otg-port failed
[    0.824491] phy phy-fe8a0000.usb2-phy.1: Looking up vbus-supply from device tree
[    0.824572] phy phy-fe8a0000.usb2-phy.1: Linked as a consumer to regulator.6
[    0.826175] extcon extcon1: failed to create extcon usb2-phy link
[    0.826276] phy phy-fe8b0000.usb2-phy.2: Looking up phy-supply from device tree
[    0.826301] vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.2 err -2
[    0.826362] phy phy-fe8b0000.usb2-phy.2: Linked as a consumer to regulator.5
[    0.826510] phy phy-fe8b0000.usb2-phy.3: Looking up phy-supply from device tree
[    0.826530] vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.3 err -2
[    0.826610] phy phy-fe8b0000.usb2-phy.3: Linked as a consumer to regulator.5
[    0.826723] phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply from device tree
[    0.826737] phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply property in node /usb2-phy@fe8b0000/otg-port failed
[    0.826758] phy phy-fe8b0000.usb2-phy.3: No vbus specified for otg port
[    0.828999] phy phy-fe850000.video-phy.4: Looking up phy-supply from device tree
[    0.829016] phy phy-fe850000.video-phy.4: Looking up phy-supply property in node /video-phy@fe850000 failed
[    0.831280] phy phy-fe820000.phy.5: Looking up phy-supply from device tree
[    0.831296] phy phy-fe820000.phy.5: Looking up phy-supply property in node /phy@fe820000 failed
[    0.831847] phy phy-fe830000.phy.6: Looking up phy-supply from device tree
[    0.831861] phy phy-fe830000.phy.6: Looking up phy-supply property in node /phy@fe830000 failed
[    0.832334] phy phy-fe840000.phy.7: Looking up phy-supply from device tree
[    0.832348] phy phy-fe840000.phy.7: Looking up phy-supply property in node /phy@fe840000 failed
[    0.833681] phy phy-fe8c0000.phy.8: Looking up phy-supply from device tree
[    0.833699] phy phy-fe8c0000.phy.8: Looking up phy-supply property in node /phy@fe8c0000 failed
[    0.837080] rk-pcie 3c0800000.pcie: Looking up vpcie3v3-supply from device tree
[    0.837193] rk-pcie 3c0800000.pcie: Linked as a consumer to regulator.9
[    0.837661] pwm-backlight backlight: Looking up power-supply from device tree
[    0.837677] pwm-backlight backlight: Looking up power-supply property in node /backlight failed
[    0.837698] pwm-backlight backlight: backlight supply power not found, using dummy regulator
[    0.837779] pwm-backlight backlight: Linked as a consumer to regulator.0
[    0.838031] pwm-backlight backlight1: Looking up power-supply from device tree
[    0.838044] pwm-backlight backlight1: Looking up power-supply property in node /backlight1 failed
[    0.838060] pwm-backlight backlight1: backlight1 supply power not found, using dummy regulator
[    0.838147] pwm-backlight backlight1: Linked as a consumer to regulator.0
[    0.838453] mpp_service mpp-srv: 
[    0.838461] mpp_service mpp-srv: probe start
[    0.839582] iommu: Adding device fdf40000.rkvenc to group 4
[    0.839610] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu
[    0.839867] mpp_rkvenc fdf40000.rkvenc: probing start
[    0.840558] mpp_rkvenc fdf40000.rkvenc: Looking up venc-supply from device tree
[    0.840580] mpp_rkvenc fdf40000.rkvenc: venc regulator not ready, retry
[    0.840587] rkvenc_init:1199: failed to add venc devfreq
[    0.841045] mpp_rkvenc fdf40000.rkvenc: probing finish
[    0.842313] iommu: Adding device fdea0400.vdpu to group 0
[    0.842343] mpp_vdpu2 fdea0400.vdpu: Linked as a consumer to fdea0800.iommu
[    0.842557] mpp_vdpu2 fdea0400.vdpu: probe device
[    0.842797] rk-pcie 3c0800000.pcie: missing legacy IRQ resource
[    0.842814] rk-pcie 3c0800000.pcie: Missing *config* reg space
[    0.842865] rk-pcie 3c0800000.pcie: host bridge /pcie@fe280000 ranges:
[    0.842881] rk-pcie 3c0800000.pcie: Parsing ranges property...
[    0.842901] rk-pcie 3c0800000.pcie:   err 0x380000000..0x3807fffff -> 0x80000000
[    0.842918] rk-pcie 3c0800000.pcie:    IO 0x380800000..0x3808fffff -> 0x80800000
[    0.842933] rk-pcie 3c0800000.pcie:   MEM 0x380900000..0x3bfffffff -> 0x80900000
[    0.843364] mpp_vdpu2 fdea0400.vdpu: probing finish
[    0.844117] iommu: Adding device fdee0000.vepu to group 2
[    0.844147] mpp_vepu2 fdee0000.vepu: Linked as a consumer to fdee0800.iommu
[    0.844389] mpp_vepu2 fdee0000.vepu: probe device
[    0.845134] mpp_vepu2 fdee0000.vepu: probing finish
[    0.845838] iommu: Adding device fdef0000.iep to group 3
[    0.845867] mpp-iep2 fdef0000.iep: Linked as a consumer to fdef0800.iommu
[    0.846055] mpp-iep2 fdef0000.iep: probe device
[    0.846675] mpp-iep2 fdef0000.iep: allocate roi buffer failed
[    0.846981] mpp-iep2 fdef0000.iep: probing finish
[    0.847603] iommu: Adding device fded0000.jpegd to group 1
[    0.847634] mpp_jpgdec fded0000.jpegd: Linked as a consumer to fded0480.iommu
[    0.847808] mpp_jpgdec fded0000.jpegd: probe device
[    0.848538] mpp_jpgdec fded0000.jpegd: probing finish
[    0.849186] iommu: Adding device fdf80200.rkvdec to group 5
[    0.849221] mpp_rkvdec2 fdf80200.rkvdec: Linked as a consumer to fdf80800.iommu
[    0.849500] mpp_rkvdec2 fdf80200.rkvdec: probing start
[    0.849680] mpp_rkvdec2 fdf80200.rkvdec: 16 task capacity link mode detected
[    0.850116] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found!
[    0.850160] rkvdec2_init:661: No niu aclk reset resource define
[    0.850185] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found!
[    0.850203] rkvdec2_init:664: No niu hclk reset resource define
[    0.850510] mpp_rkvdec2 fdf80200.rkvdec: sram_start 0x00000000fdcc0000
[    0.850519] mpp_rkvdec2 fdf80200.rkvdec: rcb_iova 0x0000000010000000
[    0.850526] mpp_rkvdec2 fdf80200.rkvdec: sram_size 45056
[    0.850532] mpp_rkvdec2 fdf80200.rkvdec: rcb_size 65536
[    0.850542] mpp_rkvdec2 fdf80200.rkvdec: min_width 512
[    0.850612] mpp_rkvdec2 fdf80200.rkvdec: link mode probe finish
[    0.850693] mpp_rkvdec2 fdf80200.rkvdec: probing finish
[    0.851064] mpp_service mpp-srv: probe success
[    0.859620] dma-pl330 fe530000.dmac: Loaded driver for PL330 DMAC-241330
[    0.859633] dma-pl330 fe530000.dmac: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    0.863001] dma-pl330 fe550000.dmac: Loaded driver for PL330 DMAC-241330
[    0.863013] dma-pl330 fe550000.dmac: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    0.864663] rockchip-system-monitor rockchip-system-monitor: system monitor probe
[    0.866000] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    0.869510] random: fast init done
[    0.869698] gpiomem-rk3568 fd660000.rk3568-gpiomem: Initialised: Registers at 0xfd660000
[    0.869830] random: crng init done
[    0.870713] iommu: Adding device fe040000.vop to group 6
[    0.870744] rockchip-vop2 fe040000.vop: Linked as a consumer to fe043e00.iommu
[    0.876468] rockchip-drm display-subsystem: Linked as a consumer to fe040000.vop
[    0.878019] rockchip-drm display-subsystem: Linked as a consumer to fe0a0000.hdmi
[    0.880457] rockchip-drm display-subsystem: defer getting devfreq
[    0.880814] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x3f, primary plane phy id: 4
[    0.880833] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x0, primary plane phy id: -1
[    0.880848] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x0, primary plane phy id: -1
[    0.881109] [drm] unsupported AFBC format[3432564e]
[    0.881176] [drm] failed to init overlay plane Cluster0-win1
[    0.881246] [drm] failed to init overlay plane Cluster1-win1
[    0.881377] rockchip-drm display-subsystem: bound fe040000.vop (ops 0xffffff8008b07e08)
[    0.881633] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    0.882369] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    0.883177] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops 0xffffff8008b0b8b0)
[    0.883189] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.883193] [drm] No driver support for vblank timestamp query.
[    0.883411] get_framebuffer_by_node: failed to get logo,offset
[    0.883464] rockchip-drm display-subsystem: can't not find any loader display
[    0.883476] rockchip-drm display-subsystem: failed to show loader logo
[    0.883558] [drm] Cannot find any crtc or sizes
[    0.883815] [drm] Cannot find any crtc or sizes
[    0.884950] [drm] Initialized rockchip 2.0.0 20140818 for display-subsystem on minor 0
[    0.893467] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_gpu-supply from device tree
[    0.893500] rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_gpu-supply property in node /power-management@fdd90000/power-controller failed
[    0.893564] mali fde60000.gpu: Kernel DDK version g7p1-01bet0
[    0.893703] mali fde60000.gpu: Looking up mali-supply from device tree
[    0.893743] mali fde60000.gpu: Device initialization Deferred
[    0.893868] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    0.894106] lkdtm: No crash points registered, enable through debugfs
[    0.898409] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-none-smt
[    0.898465] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-none-smt
[    0.898479] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-up-drv-level-2
[    0.898509] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-up-drv-level-2
[    0.898521] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-up-drv-level-1
[    0.898557] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-up-drv-level-1
[    0.898570] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-none-drv-level-3
[    0.898606] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-none-drv-level-3
[    0.898618] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-none-drv-level-2
[    0.898654] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-none-drv-level-2
[    0.898667] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-none-drv-level-1
[    0.898707] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-none-drv-level-1
[    0.898720] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-none
[    0.898750] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-none
[    0.898762] spi_master spi0: cannot find modalias for /spi@fe610000/pcfg-pull-up
[    0.898799] spi_master spi0: Failed to create SPI device for /spi@fe610000/pcfg-pull-up
[    0.899471] libphy: Fixed MDIO Bus: probed
[    0.900656] usbcore: registered new interface driver cdc_ether
[    0.900705] usbcore: registered new interface driver rndis_host
[    0.900782] usbcore: registered new interface driver cdc_ncm
[    0.902205] dwc3 fcc00000.dwc3: Failed to get clk 'ref': -2
[    0.902563] dwc3 fcc00000.dwc3: Configuration mismatch. dr_mode forced to host
[    0.906062] dwc3 fd000000.dwc3: Failed to get clk 'ref': -2
[    0.910112] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.910135] ehci-pci: EHCI PCI platform driver
[    0.910209] ehci-platform: EHCI generic platform driver
[    0.912598] ehci-platform fd800000.usb: EHCI Host Controller
[    0.912867] ehci-platform fd800000.usb: new USB bus registered, assigned bus number 1
[    0.913167] ehci-platform fd800000.usb: irq 12, io mem 0xfd800000
[    0.923642] ehci-platform fd800000.usb: USB 2.0 started, EHCI 1.00
[    0.923970] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.923981] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.923988] usb usb1: Product: EHCI Host Controller
[    0.923995] usb usb1: Manufacturer: Linux 4.19.219-odroid-arm64 ehci_hcd
[    0.924001] usb usb1: SerialNumber: fd800000.usb
[    0.924669] hub 1-0:1.0: USB hub found
[    0.924721] hub 1-0:1.0: 1 port detected
[    0.927513] ehci-platform fd880000.usb: EHCI Host Controller
[    0.927768] ehci-platform fd880000.usb: new USB bus registered, assigned bus number 2
[    0.928046] ehci-platform fd880000.usb: irq 14, io mem 0xfd880000
[    0.940307] ehci-platform fd880000.usb: USB 2.0 started, EHCI 1.00
[    0.940600] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.940611] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.940619] usb usb2: Product: EHCI Host Controller
[    0.940627] usb usb2: Manufacturer: Linux 4.19.219-odroid-arm64 ehci_hcd
[    0.940634] usb usb2: SerialNumber: fd880000.usb
[    0.941258] hub 2-0:1.0: USB hub found
[    0.941315] hub 2-0:1.0: 1 port detected
[    0.942306] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.942330] ohci-platform: OHCI generic platform driver
[    0.942627] ohci-platform fd840000.usb: Generic Platform OHCI controller
[    0.942889] ohci-platform fd840000.usb: new USB bus registered, assigned bus number 3
[    0.943119] ohci-platform fd840000.usb: irq 13, io mem 0xfd840000
[    1.001206] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    1.001217] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.001225] usb usb3: Product: Generic Platform OHCI controller
[    1.001232] usb usb3: Manufacturer: Linux 4.19.219-odroid-arm64 ohci_hcd
[    1.001239] usb usb3: SerialNumber: fd840000.usb
[    1.001891] hub 3-0:1.0: USB hub found
[    1.001952] hub 3-0:1.0: 1 port detected
[    1.002747] ohci-platform fd8c0000.usb: Generic Platform OHCI controller
[    1.003038] ohci-platform fd8c0000.usb: new USB bus registered, assigned bus number 4
[    1.003257] ohci-platform fd8c0000.usb: irq 15, io mem 0xfd8c0000
[    1.061212] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    1.061222] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.061230] usb usb4: Product: Generic Platform OHCI controller
[    1.061237] usb usb4: Manufacturer: Linux 4.19.219-odroid-arm64 ohci_hcd
[    1.061243] usb usb4: SerialNumber: fd8c0000.usb
[    1.061881] hub 4-0:1.0: USB hub found
[    1.061933] hub 4-0:1.0: 1 port detected
[    1.063948] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[    1.064234] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 5
[    1.064704] xhci-hcd xhci-hcd.4.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000011002010010
[    1.064774] xhci-hcd xhci-hcd.4.auto: irq 70, io mem 0xfcc00000
[    1.065228] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    1.065239] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.065246] usb usb5: Product: xHCI Host Controller
[    1.065254] usb usb5: Manufacturer: Linux 4.19.219-odroid-arm64 xhci-hcd
[    1.065260] usb usb5: SerialNumber: xhci-hcd.4.auto
[    1.065927] hub 5-0:1.0: USB hub found
[    1.065988] hub 5-0:1.0: 1 port detected
[    1.066484] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[    1.066721] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 6
[    1.066743] xhci-hcd xhci-hcd.4.auto: Host supports USB 3.0 SuperSpeed
[    1.066850] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.067080] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    1.067092] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.067099] usb usb6: Product: xHCI Host Controller
[    1.067108] usb usb6: Manufacturer: Linux 4.19.219-odroid-arm64 xhci-hcd
[    1.067114] usb usb6: SerialNumber: xhci-hcd.4.auto
[    1.067742] hub 6-0:1.0: USB hub found
[    1.067792] hub 6-0:1.0: 1 port detected
[    1.068475] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    1.068713] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 7
[    1.069176] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000011002010010
[    1.069247] xhci-hcd xhci-hcd.5.auto: irq 71, io mem 0xfd000000
[    1.069731] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    1.069741] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.069748] usb usb7: Product: xHCI Host Controller
[    1.069755] usb usb7: Manufacturer: Linux 4.19.219-odroid-arm64 xhci-hcd
[    1.069762] usb usb7: SerialNumber: xhci-hcd.5.auto
[    1.070459] hub 7-0:1.0: USB hub found
[    1.070523] hub 7-0:1.0: 1 port detected
[    1.071022] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    1.071275] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 8
[    1.071298] xhci-hcd xhci-hcd.5.auto: Host supports USB 3.0 SuperSpeed
[    1.071405] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.071590] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    1.071600] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.071608] usb usb8: Product: xHCI Host Controller
[    1.071615] usb usb8: Manufacturer: Linux 4.19.219-odroid-arm64 xhci-hcd
[    1.071621] usb usb8: SerialNumber: xhci-hcd.5.auto
[    1.072269] hub 8-0:1.0: USB hub found
[    1.072322] hub 8-0:1.0: 1 port detected
[    1.073020] usbcore: registered new interface driver cdc_acm
[    1.073026] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.073088] usbcore: registered new interface driver cdc_wdm
[    1.073368] usbcore: registered new interface driver uas
[    1.073649] usbcore: registered new interface driver usb-storage
[    1.074014] .. rk pwm remotectl v2.0 init
[    1.074411] input: fdd70030.pwm as /devices/platform/fdd70030.pwm/input/input0
[    1.074884] remotectl-pwm fdd70030.pwm: pwm version is 0x2130000
[    1.074959] remotectl-pwm fdd70030.pwm: Controller support pwrkey capture
[    1.075932] i2c /dev entries driver
[    1.078335] fan53555-regulator 3-001c: FAN53555 Option[12] Rev[15] Detected!
[    1.078839] vdd_cpu: override max_uV, 1390000 -> 1387500
[    1.080141] fan53555-regulator 3-001c: Looking up vin-supply from device tree
[    1.080160] vdd_cpu: supplied by vcc5v0_sys
[    1.080172] vcc5v0_sys: could not add device link regulator.10 err -2
[    1.082562] vdd_cpu: 712 <--> 1387 mV at 1025 mV 
[    1.085373] rk808 3-0020: chip id: 0x8090
[    1.085437] rk808 3-0020: No cache defaults, reading back from HW
[    1.109237] rk808 3-0020: source: on=0x10, off=0x00
[    1.109252] rk808 3-0020: support dcdc3 fb mode:-22, 63
[    1.109621] rk808 3-0020: support pmic reset mode:0,0
[    1.115796] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    1.115827] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    1.115910] rk808 3-0020: Looking up vcc1-supply from device tree
[    1.115929] vdd_logic: supplied by vcc3v3_sys
[    1.115941] vcc3v3_sys: could not add device link regulator.11 err -2
[    1.116024] vdd_logic: 500 <--> 1350 mV at 900 mV 
[    1.116435] rk808 3-0020: Looking up vcc2-supply from device tree
[    1.116451] vdd_gpu: supplied by vcc3v3_sys
[    1.116462] vcc3v3_sys: could not add device link regulator.12 err -2
[    1.116528] vdd_gpu: 500 <--> 1350 mV at 900 mV 
[    1.116966] rk808 3-0020: Looking up vcc3-supply from device tree
[    1.116982] vcc_ddr: supplied by vcc3v3_sys
[    1.116993] vcc3v3_sys: could not add device link regulator.13 err -2
[    1.117060] vcc_ddr: at 500 mV 
[    1.117448] rk808 3-0020: Looking up vcc4-supply from device tree
[    1.117463] vdd_npu: supplied by vcc3v3_sys
[    1.117475] vcc3v3_sys: could not add device link regulator.14 err -2
[    1.117927] vdd_npu: 500 <--> 1350 mV at 900 mV 
[    1.118328] rk808 3-0020: Looking up vcc9-supply from device tree
[    1.118343] vcc_1v8: supplied by vcc3v3_sys
[    1.118354] vcc3v3_sys: could not add device link regulator.15 err -2
[    1.118413] vcc_1v8: 1800 mV 
[    1.118779] rk808 3-0020: Looking up vcc5-supply from device tree
[    1.118793] vdda0v9_image: supplied by vcc3v3_sys
[    1.118804] vcc3v3_sys: could not add device link regulator.16 err -2
[    1.119757] vdda0v9_image: 900 mV 
[    1.120123] rk808 3-0020: Looking up vcc5-supply from device tree
[    1.120139] vdda_0v9: supplied by vcc3v3_sys
[    1.120150] vcc3v3_sys: could not add device link regulator.17 err -2
[    1.120210] vdda_0v9: 900 mV 
[    1.120618] rk808 3-0020: Looking up vcc5-supply from device tree
[    1.120634] vdda0v9_pmu: supplied by vcc3v3_sys
[    1.120644] vcc3v3_sys: could not add device link regulator.18 err -2
[    1.120706] vdda0v9_pmu: 900 mV 
[    1.121069] rk808 3-0020: Looking up vcc6-supply from device tree
[    1.121084] vccio_acodec: supplied by vcc3v3_sys
[    1.121095] vcc3v3_sys: could not add device link regulator.19 err -2
[    1.122043] vccio_acodec: 3300 mV 
[    1.122416] rk808 3-0020: Looking up vcc6-supply from device tree
[    1.122431] vccio_sd: supplied by vcc3v3_sys
[    1.122442] vcc3v3_sys: could not add device link regulator.20 err -2
[    1.122506] vccio_sd: 1800 <--> 3300 mV at 3300 mV 
[    1.122894] rk808 3-0020: Looking up vcc6-supply from device tree
[    1.122908] vcc3v3_pmu: supplied by vcc3v3_sys
[    1.122919] vcc3v3_sys: could not add device link regulator.21 err -2
[    1.122980] vcc3v3_pmu: 3300 mV 
[    1.123338] rk808 3-0020: Looking up vcc7-supply from device tree
[    1.123352] vcca_1v8: supplied by vcc3v3_sys
[    1.123364] vcc3v3_sys: could not add device link regulator.22 err -2
[    1.123440] vcca_1v8: 1800 mV 
[    1.123831] rk808 3-0020: Looking up vcc7-supply from device tree
[    1.123845] vcca1v8_pmu: supplied by vcc3v3_sys
[    1.123856] vcc3v3_sys: could not add device link regulator.23 err -2
[    1.123938] vcca1v8_pmu: 1800 mV 
[    1.124308] rk808 3-0020: Looking up vcc7-supply from device tree
[    1.124322] vcca1v8_image: supplied by vcc3v3_sys
[    1.124333] vcc3v3_sys: could not add device link regulator.24 err -2
[    1.125306] vcca1v8_image: 1800 mV 
[    1.125664] rk808 3-0020: Looking up vcc9-supply from device tree
[    1.125680] vcc_3v3: supplied by vcc3v3_sys
[    1.125695] vcc3v3_sys: could not add device link regulator.25 err -2
[    1.125758] vcc_3v3: at 3300 mV 
[    1.126095] rk808 3-0020: Looking up vcc8-supply from device tree
[    1.126110] vcc3v3_sd: supplied by vcc3v3_sys
[    1.126125] vcc3v3_sys: could not add device link regulator.26 err -2
[    1.126186] vcc3v3_sd: at 3300 mV 
[    1.126698] rk817-battery rk817-battery: Failed to find matching dt id
[    1.127093] rk817-charger rk817-charger: Failed to find matching dt id
[    1.130556] input: rk805 pwrkey as /devices/platform/fdd40000.i2c/i2c-3/3-0020/rk805-pwrkey/input/input1
[    1.137293] rk808-rtc rk808-rtc: registered as rtc0
[    1.139068] rk808-rtc rk808-rtc: setting system clock to 2023-01-05 16:33:30 UTC (1672936410)
[    1.144046] rockchip-iodomain fdc20000.syscon:io-domains: Looking up pmuio1-supply from device tree
[    1.144065] rockchip-iodomain fdc20000.syscon:io-domains: Looking up pmuio1-supply property in node /syscon@fdc20000/io-domains failed
[    1.144107] rockchip-iodomain fdc20000.syscon:io-domains: Looking up pmuio2-supply from device tree
[    1.144216] rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.21
[    1.144256] rockchip-iodomain fdc20000.syscon:io-domains: pmuio2(3300000 uV) supplied by vcc3v3_pmu
[    1.144288] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio1-supply from device tree
[    1.144396] rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.19
[    1.144431] rockchip-iodomain fdc20000.syscon:io-domains: vccio1(3300000 uV) supplied by vccio_acodec
[    1.144462] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio2-supply from device tree
[    1.144476] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio2-supply property in node /syscon@fdc20000/io-domains failed
[    1.144506] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio3-supply from device tree
[    1.144589] rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.20
[    1.144622] rockchip-iodomain fdc20000.syscon:io-domains: vccio3(3300000 uV) supplied by vccio_sd
[    1.144658] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio4-supply from device tree
[    1.144739] rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.15
[    1.144772] rockchip-iodomain fdc20000.syscon:io-domains: vccio4(1800000 uV) supplied by vcc_1v8
[    1.144802] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio5-supply from device tree
[    1.144910] rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.25
[    1.144945] rockchip-iodomain fdc20000.syscon:io-domains: vccio5(3300000 uV) supplied by vcc_3v3
[    1.144977] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio6-supply from device tree
[    1.145087] rockchip-iodomain fdc20000.syscon:io-domains: vccio6(3300000 uV) supplied by vcc_3v3
[    1.145118] rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio7-supply from device tree
[    1.145227] rockchip-iodomain fdc20000.syscon:io-domains: vccio7(3300000 uV) supplied by vcc_3v3
[    1.149008] rockchip-thermal fe710000.tsadc: tsadc is probed successfully!
[    1.150816] cpu cpu0: leakage=29
[    1.150871] cpu cpu0: pvtm = 88970, from nvmem
[    1.150888] cpu cpu0: pvtm-volt-sel=1
[    1.151216] cpu cpu0: Looking up cpu-supply from device tree
[    1.151835] cpu cpu0: Linked as a consumer to regulator.10
[    1.151905] cpu cpu0: Dropping the link to regulator.10
[    1.152054] cpu cpu0: Looking up cpu-supply from device tree
[    1.152607] cpu cpu0: Linked as a consumer to regulator.10
[    1.153881] cpu cpu0: avs=0
[    1.153987] cpu cpu0: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0
[    1.160409] cpu cpu0: failed to find power_model node
[    1.161194] sdhci: Secure Digital Host Controller Interface driver
[    1.161197] sdhci: Copyright(c) Pierre Ossman
[    1.161198] Synopsys Designware Multimedia Card Interface Driver
[    1.161892] dwmmc_rockchip fe2b0000.dwmmc: IDMAC supports 32-bit address mode.
[    1.161959] dwmmc_rockchip fe2b0000.dwmmc: Using internal DMA controller.
[    1.161965] dwmmc_rockchip fe2b0000.dwmmc: Version ID is 270a
[    1.162004] dwmmc_rockchip fe2b0000.dwmmc: DW MMC controller at irq 46,32 bit host data width,256 deep fifo
[    1.162020] dwmmc_rockchip fe2b0000.dwmmc: Looking up vmmc-supply from device tree
[    1.162102] dwmmc_rockchip fe2b0000.dwmmc: Linked as a consumer to regulator.26
[    1.162107] dwmmc_rockchip fe2b0000.dwmmc: Looking up vqmmc-supply from device tree
[    1.162147] dwmmc_rockchip fe2b0000.dwmmc: Linked as a consumer to regulator.20
[    1.175089] mmc_host mmc1: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    1.187918] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.188915] sdhci-dwcmshc fe310000.sdhci: Looking up vmmc-supply from device tree
[    1.188923] sdhci-dwcmshc fe310000.sdhci: Looking up vmmc-supply property in node /sdhci@fe310000 failed
[    1.188948] sdhci-dwcmshc fe310000.sdhci: Looking up vqmmc-supply from device tree
[    1.188952] sdhci-dwcmshc fe310000.sdhci: Looking up vqmmc-supply property in node /sdhci@fe310000 failed
[    1.188989] mmc0: Unknown controller version (5). You may experience problems.
[    1.220541] mmc0: SDHCI controller on fe310000.sdhci [fe310000.sdhci] using ADMA
[    1.221602] ledtrig-cpu: registered to indicate activity on CPUs
[    1.221976] hidraw: raw HID events driver (C) Jiri Kosina
[    1.222179] rockchip,bus bus-npu: Looking up bus-supply from device tree
[    1.222245] rockchip,bus bus-npu: Linked as a consumer to regulator.11
[    1.222255] rockchip,bus bus-npu: Failed to get leakage
[    1.222322] rockchip,bus bus-npu: pvtm = 88970, from nvmem
[    1.222330] rockchip,bus bus-npu: pvtm-volt-sel=1
[    1.222521] rockchip,bus bus-npu: avs=0
[    1.224135] rockchip-saradc fe720000.saradc: Looking up vref-supply from device tree
[    1.224203] rockchip-saradc fe720000.saradc: Linked as a consumer to regulator.22
[    1.224666] rksfc_base v1.1 2016-01-08
[    1.225195] rksfc fe300000.sfc: rksfc_probe clk rate = 99000000
[    1.225420] rkflash_dev_init enter
[    1.225448] sfc nor id: c2 25 38
[    1.225831] rkflash[1] init success
[    1.226033] 4 cmdlinepart partitions found on MTD device sfc_nor
[    1.226035] Creating 4 MTD partitions on "sfc_nor":
[    1.226041] 0x0000000e0000-0x000000100000 : "env"
[    1.226689] 0x000000100000-0x000000300000 : "uboot"
[    1.227314] 0x000000300000-0x000000400000 : "splash"
[    1.227853] 0x000000400000-0x000001000000 : "firmware"
[    1.228380] sfc_nor_mtd_init register mtd succuss
[    1.228384] rkflash_dev_init device register as mtd dev, ret= 0
[    1.230121] rk817-codec rk817-codec: DMA mask not set
[    1.234437] Initializing XFRM netlink socket
[    1.234483] NET: Registered protocol family 17
[    1.234498] NET: Registered protocol family 15
[    1.234514] Key type dns_resolver registered
[    1.235285] registered taskstats version 1
[    1.235288] Loading compiled-in X.509 certificates
[    1.235512] Key type ._fscrypt registered
[    1.235514] Key type .fscrypt registered
[    1.235516] Key type fscrypt-provisioning registered
[    1.236241] rga2: Driver loaded successfully ver:3.2.63318
[    1.236488] rga2: Module initialized.
[    1.258100] mali fde60000.gpu: Kernel DDK version g7p1-01bet0
[    1.258184] mali fde60000.gpu: Looking up mali-supply from device tree
[    1.258247] mali fde60000.gpu: Linked as a consumer to regulator.12
[    1.258252] mali fde60000.gpu: Looking up shadercores-supply from device tree
[    1.258261] mali fde60000.gpu: Looking up shadercores-supply property in node /gpu@fde60000 failed
[    1.258313] mali fde60000.gpu: Looking up mali-supply from device tree
[    1.258329] vdd_gpu: could not add device link fde60000.gpu err -17
[    1.258336] vdd_gpu: Failed to create debugfs directory
[    1.258342] mali fde60000.gpu: Looking up shadercores-supply from device tree
[    1.258348] mali fde60000.gpu: Looking up shadercores-supply property in node /gpu@fde60000 failed
[    1.258361] mali fde60000.gpu: dev_pm_opp_set_regulators: no regulator (shadercores) found: -19
[    1.258482] mali fde60000.gpu: leakage=8
[    1.258512] mali fde60000.gpu: pvtm = 88970, from nvmem
[    1.258789] asoc-simple-card hdmi-sound: i2s-hifi <-> fe400000.i2s mapping ok
[    1.258950] mali fde60000.gpu: avs=0
[    1.258962] W : [File] : /opt/source/drivers/gpu/arm/bifrost/platform/rk/mali_kbase_config_rk.c; [Line] : 112; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available.
[    1.259236] mali fde60000.gpu: GPU identified as 0x2 arch 7.4.0 r1p0 status 0
[    1.259299] mali fde60000.gpu: No priority control manager is configured
[    1.259304] mali fde60000.gpu: No memory group manager is configured
[    1.259776] mali fde60000.gpu: l=-2147483648 h=2147483647 hyst=0 l_limit=0 h_limit=0 h_table=0
[    1.260065] asoc-simple-card rk809-sound: ASoC: DAPM unknown pin Headphones
[    1.260438] mali fde60000.gpu: Probed as mali0
[    1.264685] asoc-simple-card rk809-sound: rk817-hifi <-> fe410000.i2s mapping ok
[    1.265216] input: ODROID-M1-FRONT Headphones as /devices/platform/rk809-sound/sound/card1/input2
[    1.267855] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply from device tree
[    1.267869] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply property in node /ethernet@fe2a0000 failed
[    1.267893] rk_gmac-dwmac fe2a0000.ethernet: no regulator found
[    1.267930] rk_gmac-dwmac fe2a0000.ethernet: clock input or output? (output).
[    1.267935] rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x4f).
[    1.267938] rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2d).
[    1.267945] rk_gmac-dwmac fe2a0000.ethernet: integrated PHY? (no).
[    1.272976] rk_gmac-dwmac fe2a0000.ethernet: init for RGMII
[    1.273366] rk_gmac-dwmac fe2a0000.ethernet: User ID: 0x30, Synopsys ID: 0x51
[    1.273372] rk_gmac-dwmac fe2a0000.ethernet: 	DWMAC4/5
[    1.273377] rk_gmac-dwmac fe2a0000.ethernet: DMA HW capability register supported
[    1.273380] rk_gmac-dwmac fe2a0000.ethernet: RX Checksum Offload Engine supported
[    1.273382] rk_gmac-dwmac fe2a0000.ethernet: TX Checksum insertion supported
[    1.273385] rk_gmac-dwmac fe2a0000.ethernet: Wake-Up On Lan supported
[    1.273407] rk_gmac-dwmac fe2a0000.ethernet: TSO supported
[    1.273411] rk_gmac-dwmac fe2a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    1.273474] rk_gmac-dwmac fe2a0000.ethernet: rk_get_eth_addr: mac address: 00:1e:06:51:1c:f4
[    1.273498] rk_gmac-dwmac fe2a0000.ethernet: device MAC address 00:1e:06:51:1c:f4
[    1.273502] rk_gmac-dwmac fe2a0000.ethernet: TSO feature enabled
[    1.300640] mmc0: Got command interrupt 0x00000001 even though no command operation was in progress.
[    1.300661] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[    1.300671] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00000005
[    1.300679] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[    1.300688] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[    1.300697] mmc0: sdhci: Present:   0x03f700f0 | Host ctl: 0x00000001
[    1.300705] mmc0: sdhci: Power:     0x0000000d | Blk gap:  0x00000000
[    1.300714] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00000847
[    1.300722] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[    1.300731] mmc0: sdhci: Int enab:  0x00ff0003 | Sig enab: 0x00ff0003
[    1.300742] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[    1.300753] mmc0: sdhci: Caps:      0x226dc881 | Caps_1:   0x08000007
[    1.300764] mmc0: sdhci: Cmd:       0x00000102 | Max curr: 0x00000000
[    1.300774] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[    1.300785] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[    1.300795] mmc0: sdhci: Host ctl2: 0x00000000
[    1.300805] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[    1.300814] mmc0: sdhci: ============================================
[    1.334939] mmc0: Got command interrupt 0x00000001 even though no command operation was in progress.
[    1.334955] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[    1.334965] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00000005
[    1.334974] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[    1.334982] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[    1.334990] mmc0: sdhci: Present:   0x03f700f0 | Host ctl: 0x00000001
[    1.334998] mmc0: sdhci: Power:     0x0000000d | Blk gap:  0x00000000
[    1.335006] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00000847
[    1.335014] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[    1.335022] mmc0: sdhci: Int enab:  0x00ff0003 | Sig enab: 0x00ff0003
[    1.335037] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[    1.335048] mmc0: sdhci: Caps:      0x226dc881 | Caps_1:   0x08000007
[    1.335060] mmc0: sdhci: Cmd:       0x00000102 | Max curr: 0x00000000
[    1.335071] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[    1.335081] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[    1.335092] mmc0: sdhci: Host ctl2: 0x00000000
[    1.335101] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[    1.335111] mmc0: sdhci: ============================================
[    1.394581] rockchip-vop2 fe040000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 1920x1200p60, type: 11 for vp0
[    1.406975] libphy: stmmac: probed
[    1.413107] asoc-simple-card rk809-sound: ASoC: DAPM unknown pin Headphones
[    1.414365] devfreq fde60000.gpu: Couldn't update frequency transition information.
[    1.414987] rockchip-pm rockchip-suspend: not set pwm-regulator-config
[    1.416138] I : [File] : /opt/source/drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 417; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '', rk_ko_ver is '5', built at '03:16:46', on 'May 27 2022'.
[    1.416386] Mali: 
[    1.416387] Mali device driver loaded
[    1.428319] Console: switching to colour frame buffer device 240x75
[    1.460012] rockchip-drm display-subsystem: fb0:  frame buffer device
[    1.463596] usb 4-1: new low-speed USB device number 2 using ohci-platform
[    1.690031] usb 4-1: New USB device found, idVendor=413c, idProduct=2003, bcdDevice= 3.06
[    1.690035] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.690038] usb 4-1: Product: Dell USB Keyboard
[    1.690042] usb 4-1: Manufacturer: Dell
[    1.846968] rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x0
[    1.970389] ALSA device list:
[    1.970392]   #0: ODROID-M1-HDMI
[    1.970394]   #1: ODROID-M1-FRONT
[    1.972324] Freeing unused kernel memory: 1280K
[    1.972413] Run /init as init process
[    2.248927] libata version 3.00 loaded.
[    2.252244] ahci fc800000.sata: Looking up target-supply from device tree
[    2.252255] ahci fc800000.sata: Looking up target-supply property in node /sata@fc800000 failed
[    2.252418] ahci fc800000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[    2.252424] ahci fc800000.sata: flags: ncq sntf pm led clo only pmp fbs pio slum part ccc apst 
[    2.252439] ahci fc800000.sata: port 0 is not capable of FBS
[    2.254192] scsi host0: ahci
[    2.254592] ata1: SATA max UDMA/133 mmio [mem 0xfc800000-0xfc800fff] port 0x100 irq 11
[    2.257079] usbcore: registered new interface driver usbhid
[    2.257085] usbhid: USB HID core driver
[    2.357105] input: Dell Dell USB Keyboard as /devices/platform/fd8c0000.usb/usb4/4-1/4-1:1.0/0003:413C:2003.0001/input/input3
[    2.414246] hid-generic 0003:413C:2003.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-fd8c0000.usb-1/input0
[    2.570609] ata1: SATA link down (SStatus 0 SControl 300)
[    2.966969] rk-pcie 3c0800000.pcie: PCIe Link up, LTSSM is 0x30011
[    2.967136] rk-pcie 3c0800000.pcie: PCI host bridge to bus 0002:20
[    2.967144] pci_bus 0002:20: root bus resource [bus 20-2f]
[    2.967150] pci_bus 0002:20: root bus resource [??? 0x380000000-0x3807fffff flags 0x0] (bus address [0x80000000-0x807fffff])
[    2.967155] pci_bus 0002:20: root bus resource [io  0x0000-0xfffff] (bus address [0x80800000-0x808fffff])
[    2.967159] pci_bus 0002:20: root bus resource [mem 0x380900000-0x3bfffffff] (bus address [0x80900000-0xbfffffff])
[    2.967163] pci_bus 0002:20: scanning bus
[    2.967188] pci 0002:20:00.0: [1d87:3566] type 01 class 0x060400
[    2.967214] pci 0002:20:00.0: reg 0x10: [mem 0x00000000-0x3fffffff 64bit]
[    2.967221] pci 0002:20:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
[    2.967271] pci 0002:20:00.0: supports D1 D2
[    2.967274] pci 0002:20:00.0: PME# supported from D0 D1 D3hot
[    2.967281] pci 0002:20:00.0: PME# disabled
[    2.967311] PCI: OF: /pcie@fe280000: msi-map, using mask ffffffff, rid-base: 00002000, out-base: 00002000, length: 00001000, rid: 00002000 -> 00002000
[    2.971917] pci_bus 0002:20: fixups for bus
[    2.971932] pci 0002:20:00.0: scanning [bus 01-ff] behind bridge, pass 0
[    2.971935] pci 0002:20:00.0: Primary bus is hard wired to 0
[    2.971939] pci 0002:20:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring
[    2.971950] pci 0002:20:00.0: scanning [bus 00-00] behind bridge, pass 1
[    2.972106] pci_bus 0002:21: scanning bus
[    2.972214] pci 0002:21:00.0: [1179:010f] type 00 class 0x010802
[    2.972415] pci 0002:21:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    2.972678] pci 0002:21:00.0: enabling Extended Tags
[    2.973289] pci 0002:21:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x2 link at 0002:20:00.0 (capable of 31.504 Gb/s with 8 GT/s x4 link)
[    2.973318] PCI: OF: /pcie@fe280000: msi-map, using mask ffffffff, rid-base: 00002000, out-base: 00002000, length: 00001000, rid: 00002100 -> 00002100
[    3.004097] pci_bus 0002:21: fixups for bus
[    3.004105] pci_bus 0002:21: bus scan returning with max=21
[    3.004114] pci_bus 0002:21: busn_res: [bus 21-2f] end is updated to 21
[    3.004122] pci_bus 0002:20: bus scan returning with max=21
[    3.004154] pci 0002:20:00.0: BAR 0: no space for [mem size 0x40000000 64bit]
[    3.004158] pci 0002:20:00.0: BAR 0: failed to assign [mem size 0x40000000 64bit]
[    3.004163] pci 0002:20:00.0: BAR 8: assigned [mem 0x380900000-0x3809fffff]
[    3.004167] pci 0002:20:00.0: BAR 6: assigned [mem 0x380a00000-0x380a0ffff pref]
[    3.004175] pci 0002:21:00.0: BAR 0: assigned [mem 0x380900000-0x380903fff 64bit]
[    3.004243] pci 0002:20:00.0: PCI bridge to [bus 21]
[    3.004249] pci 0002:20:00.0:   bridge window [mem 0x380900000-0x3809fffff]
[    3.004426] pcieport 0002:20:00.0: assign IRQ: got 99
[    3.004616] pcieport 0002:20:00.0: Signaling PME with IRQ 99
[    3.006284] nvme 0002:21:00.0: assign IRQ: got 99
[    3.006544] nvme nvme0: pci function 0002:21:00.0
[    3.006646] nvme 0002:21:00.0: enabling device (0000 -> 0002)
[    3.006688] nvme 0002:21:00.0: enabling bus mastering
[    3.116204]  nvme0n1: p1 p2
[    3.187085] EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.317378] systemd[1]: Inserted module 'autofs4'
[    3.337009] NET: Registered protocol family 10
[    3.356192] Segment Routing with IPv6
[    3.366465] systemd[1]: systemd 245.4-4ubuntu3.17 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    3.367193] systemd[1]: Detected architecture arm64.
[    3.369707] systemd[1]: Set hostname to <server>.
[    3.597521] systemd[1]: Created slice system-modprobe.slice.
[    3.598375] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    3.599017] systemd[1]: Created slice User and Session Slice.
[    3.599222] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    3.599354] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    3.599483] systemd[1]: Condition check resulted in Arbitrary Executable File Formats File System Automount Point being skipped.
[    3.599563] systemd[1]: Reached target Local Encrypted Volumes.
[    3.599649] systemd[1]: Reached target Remote File Systems.
[    3.599682] systemd[1]: Reached target Slices.
[    3.599726] systemd[1]: Reached target Swap.
[    3.600110] systemd[1]: Listening on Syslog Socket.
[    3.600373] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    3.600925] systemd[1]: Listening on Journal Audit Socket.
[    3.601210] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.601529] systemd[1]: Listening on Journal Socket.
[    3.601905] systemd[1]: Listening on Network Service Netlink Socket.
[    3.602217] systemd[1]: Listening on udev Control Socket.
[    3.602430] systemd[1]: Listening on udev Kernel Socket.
[    3.602733] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[    3.605716] systemd[1]: Mounting POSIX Message Queue File System...
[    3.609043] systemd[1]: Mounting Kernel Debug File System...
[    3.612755] systemd[1]: Mounting Kernel Trace File System...
[    3.617669] systemd[1]: Starting Journal Service...
[    3.621442] systemd[1]: Starting Set the console keyboard layout...
[    3.625379] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    3.625541] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[    3.625755] systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped.
[    3.627080] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    3.632801] systemd[1]: Starting Load Kernel Modules...
[    3.636537] systemd[1]: Starting Remount Root and Kernel File Systems...
[    3.640639] systemd[1]: Starting udev Coldplug all Devices...
[    3.646828] systemd[1]: Mounted POSIX Message Queue File System.
[    3.647639] systemd[1]: Mounted Kernel Debug File System.
[    3.648350] systemd[1]: Mounted Kernel Trace File System.
[    3.650890] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    3.659138] systemd[1]: Finished Load Kernel Modules.
[    3.660143] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[    3.664127] systemd[1]: Mounting Kernel Configuration File System...
[    3.666494] EXT4-fs (nvme0n1p2): re-mounted. Opts: data=ordered
[    3.668138] systemd[1]: Starting Apply Kernel Variables...
[    3.674545] systemd[1]: Finished Remount Root and Kernel File Systems.
[    3.677911] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[    3.678037] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    3.682370] systemd[1]: Starting Load/Save Random Seed...
[    3.692143] systemd[1]: Starting Create System Users...
[    3.695619] systemd[1]: Mounted Kernel Configuration File System.
[    3.741589] systemd[1]: Finished Load/Save Random Seed.
[    3.755366] systemd[1]: Finished Create System Users.
[    3.758864] systemd[1]: Starting Create Static Device Nodes in /dev...
[    3.763220] systemd[1]: Finished Apply Kernel Variables.
[    3.794767] systemd[1]: Finished Create Static Device Nodes in /dev.
[    3.798481] systemd[1]: Starting udev Kernel Device Manager...
[    3.836036] systemd[1]: Finished Set the console keyboard layout.
[    3.836622] systemd[1]: Reached target Local File Systems (Pre).
[    3.853163] systemd[1]: Started udev Kernel Device Manager.
[    3.858241] systemd[1]: Starting Network Service...
[    3.978930] systemd[1]: Finished udev Coldplug all Devices.
[    4.070906] systemd[1]: Started Network Service.
[    4.124790] systemd[1]: Created slice system-systemd\x2dbacklight.slice.
[    4.129816] systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:backlight1...
[    4.141037] systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:backlight...
[    4.166417] systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:backlight.
[    4.172997] systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:backlight1.
[    4.181053] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=98)
[    4.198612] dwmac4: Master AXI performs any burst length
[    4.198633] rk_gmac-dwmac fe2a0000.ethernet eth0: No Safety Features support found
[    4.198651] rk_gmac-dwmac fe2a0000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[    4.198968] rk_gmac-dwmac fe2a0000.ethernet eth0: registered PTP clock
[    4.199444] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.320033] systemd[1]: Found device THNSN5256GPU7 TOSHIBA BOOT.
[    4.324550] systemd[1]: Started Journal Service.
[    4.394845] systemd-journald[194]: Received client request to flush runtime journal.
[    4.623272] cryptd: max_cpu_qlen set to 1000
[    5.503348] ttyFIQ ttyFIQ0: tty_port_close_start: tty->count = 1 port count = 2
[   38.757283] rk_gmac-dwmac fe2a0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   38.757316] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
I will go forth installing some packages and see how that goes.

I am a bit confused why the net installer would not recognize the drive. I would really like to have Debian Bullseye installed and have not been able to find a downloadable image for that. It is (so it sems) only offered as a netinstall.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Installed some packages (Webmin) and ran upgrades. After a short period of time (might be two minutes) I get this:

Image

No need to say that the system becomes unresponsive after this and all that is left is a reboot. So Toshiba is not as compatible as it first seemed :(

If there are settings to be made to get this drive to behave properly I am all ears.

EDIT: I repeated the same procedure for the Samsung NVME. Same result :( After a few minutes the M1 goes "bezirk" with error messages. Much the same as the ones in the above picture.

So one way or the other.... these drives don't seem to work on the M1 :o

User avatar
mctom
Posts: 2592
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: OGA, XU4, C2, M1, H3+, SP3, Vu8M
Location: Gdansk, Poland
Has thanked: 351 times
Been thanked: 447 times
Contact:

Re: NVME drives not working (although they should?)

Post by mctom »

When the drive is incompatible it usually doesn't work at all, I think.

If you have two totally different drives that give these bizarre errors, I'd start suspecting there is something wrong with your M1.
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

User avatar
odroid
Site Admin
Posts: 40566
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 3011 times
Been thanked: 1672 times
Contact:

Re: NVME drives not working (although they should?)

Post by odroid »

I think you have a hardware problem.
Try cleaning the M.2 NVMe connector contact pins on the M1 board with cotton swab and alcohol just in case.

If it doesn't help, please contact "odroid at hardkernel dot com" with a URL of this thread.
They will help your RMA process if you purchased the M1 from our web-store directly.
Otherwise, contact your local distributor/reseller.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Thank you both for your reply. I received the Kingston A2000 this morning and placed it in the M1. Did a net install of Bullseye without a glitch. I am going to build the system as I intended and see if the errors I had yesterday will reappear. I hope not of course :)

Will edit this post with my findings.
These users thanked the author Sjonnie for the post:
odroid (Fri Jan 06, 2023 7:50 pm)

User avatar
mctom
Posts: 2592
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: OGA, XU4, C2, M1, H3+, SP3, Vu8M
Location: Gdansk, Poland
Has thanked: 351 times
Been thanked: 447 times
Contact:

Re: NVME drives not working (although they should?)

Post by mctom »

Sjonnie wrote:
Fri Jan 06, 2023 7:41 pm
Will edit this post with my findings.
You'd better just add another post, otherwise we won't get notified. :)
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

You got a point there. I didn't want to flood this thread though ;)

Anyway up to this point (over an hour in building the system) the M1 and the A2000 are behaving as expected. No crashes, no weird errors on the connected monitor. Installed Webmin and docker-compose.

Tried fio (iozone is not available on Bullseye) and these are the results:

Code: Select all

sudo fio --filename=/dev/nvme0n1 --direct=1 --rw=read --bs=1024k --ioengine=libaio --iodepth=64 --size=4G --runtime=10 --numjobs=4 --group_reporting --name=fio-rand-read-sequential --eta-newline=1 --readonly | grep READ
   READ: bw=393MiB/s (412MB/s), 393MiB/s-393MiB/s (412MB/s-412MB/s), io=3966MiB (4159MB), run=10086-10086msec
Not too bad a figure I suppose (haven't checked references on this forum yet)?

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

And 15 minutes later? Bingo! Crash :( Same error as previously posted. Cleaned the connector and restarted the M1. Will continue to build the system. Let's hope cleaning did the trick.

I think you haven't had the time to read this post so I can safely edit this with the following:

It crashed again after 5 minutes!

Will contact local seller to request RMA.

User avatar
mctom
Posts: 2592
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: OGA, XU4, C2, M1, H3+, SP3, Vu8M
Location: Gdansk, Poland
Has thanked: 351 times
Been thanked: 447 times
Contact:

Re: NVME drives not working (although they should?)

Post by mctom »

Sorry to hear that. But at least it may be concluded that the drives you have tested so far are not confirmed to be not working.
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

That's true. The RMA has been submitted and is currently under review. I expect to have a fresh M1 somewhere the coming week. I will test all 4 NVME's so I can confirm they are working (or not).

User avatar
mctom
Posts: 2592
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: OGA, XU4, C2, M1, H3+, SP3, Vu8M
Location: Gdansk, Poland
Has thanked: 351 times
Been thanked: 447 times
Contact:

Re: NVME drives not working (although they should?)

Post by mctom »

If I may suggest something, test your drives in reverse order, just in case one of them killed you M1 somehow.
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

That's scary! Hadn't thought of that. Then I think I will stick with the A2000 which has been reported to work. I'll find another use for the two "old" NVMe's. I don't want to have to apply for another RMA in case you're right.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

I am lost! I got a new M1 from seller and placed the Kingston A2000 (brand new - reported to work). Install went smooth with Ubuntu 22.04 and Debian 11 (both from netboot). In both cases the device crashes after a few hours. sometimes 2 hours, other times 4 hours. I installed with a screen (1920x1200) and a keyboard attached. Powered down the device and disconnected peripherals because I thought that might have influence on the behaviour of the M1.

Only other thing I have added to the M1 is a CR2032 (also brand new) for the RTC.

Note: I am using the "official" power adapter supplied by seller. Output DC 12V - 2A

Any clues?

I will try an old NVMe but fear that won't do any good.

User avatar
mad_ady
Posts: 11208
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, H2, Go, Go Advance, M1
Location: Bucharest, Romania
Has thanked: 647 times
Been thanked: 1059 times
Contact:

Re: NVME drives not working (although they should?)

Post by mad_ady »

At this point it would be useful to see what causes the crash. Are you sure it's disk related? Do you get anything on screen/serial port when it crashes?

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

I get messages similar to those posted in my third post. I have taken a photo of the last crash. It looks like this:

Image

Note: the miniserv.pl is a component from Webmin.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

The output of dmesg after a reboot:

Code: Select all

  [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 5.18.0-odroid-arm64 (tobetter@gmail.com) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT Debian 5.18.0-202205171802~bullseye (2022-05-17)
[    0.000000] Machine model: Hardkernel ODROID-M1
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000001fff5cfff]
[    0.000000] NUMA: NODE_DATA [mem 0x1f6264040-0x1f6265fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000200000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x00000001fff5cfff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000200000-0x000000000198ffff]
[    0.000000]   node   0: [mem 0x0000000001a60000-0x00000000083fffff]
[    0.000000]   node   0: [mem 0x0000000009400000-0x000000000a0fffff]
[    0.000000]   node   0: [mem 0x000000000a121000-0x000000000a1fffff]
[    0.000000]   node   0: [mem 0x000000000a51b000-0x00000000808fffff]
[    0.000000]   node   0: [mem 0x0000000080a00000-0x00000000e9fe8fff]
[    0.000000]   node   0: [mem 0x00000000ee28d000-0x00000000eeff6fff]
[    0.000000]   node   0: [mem 0x0000000100000000-0x00000001f6ffffff]
[    0.000000]   node   0: [mem 0x00000001f7e00000-0x00000001f7f5bfff]
[    0.000000]   node   0: [mem 0x00000001ffe00000-0x00000001ffea5fff]
[    0.000000]   node   0: [mem 0x00000001fff5b000-0x00000001fff5cfff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000001fff5cfff]
[    0.000000] On node 0, zone DMA: 512 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 208 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 4096 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 33 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 795 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 256 pages in unavailable ranges
[    0.000000] On node 0, zone DMA: 17060 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 4105 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 3584 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 32420 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 181 pages in unavailable ranges
[    0.000000] On node 0, zone Normal: 163 pages in unavailable ranges
[    0.000000] cma: Reserved 32 MiB at 0x00000000e7c00000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 20 pages/cpu s43496 r8192 d30232 u81920
[    0.000000] pcpu-alloc: s43496 r8192 d30232 u81920 alloc=20*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: Virtualization Host Extensions
[    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    0.000000] alternatives: patching kernel code
[    0.000000] Fallback order for Node 0: 0 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1936883
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: quiet console=tty1 console=ttyS2,1500000 pci=nomsi fsck.mode=force fsck.repair=yes console=ttyS0,115200n8 
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 0x00000000e3c00000-0x00000000e7c00000] (64MB)
[    0.000000] Memory: 7581076K/7872812K available (16384K kernel code, 1948K rwdata, 5840K rodata, 3328K init, 637K bss, 258968K reserved, 32768K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000] 	Trampoline variant of Tasks RCU enabled.
[    0.000000] 	Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 320 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: MBI range [296:319]
[    0.000000] GICv3: Using MBI frame 0x00000000fd410000
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x478/0x668 with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000001] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.001396] Console: colour dummy device 80x25
[    0.001450] printk: console [tty1] enabled
[    0.001574] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001595] pid_max: default: 32768 minimum: 301
[    0.001678] LSM: Security Framework initializing
[    0.001733] Yama: disabled by default; enable with sysctl kernel.yama.*
[    0.001767] SELinux:  Initializing.
[    0.001972] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.002028] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.004243] cblist_init_generic: Setting adjustable number of callback queues.
[    0.004262] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.004388] cblist_init_generic: Setting shift to 2 and lim to 1.
[    0.004663] rcu: Hierarchical SRCU implementation.
[    0.008618] smp: Bringing up secondary CPUs ...
[    0.009403] Detected VIPT I-cache on CPU1
[    0.009453] GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000
[    0.009513] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[    0.010400] Detected VIPT I-cache on CPU2
[    0.010442] GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000
[    0.010487] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]
[    0.011311] Detected VIPT I-cache on CPU3
[    0.011353] GICv3: CPU3: found redistributor 300 region 0:0x00000000fd4c0000
[    0.011396] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]
[    0.011521] smp: Brought up 1 node, 4 CPUs
[    0.011542] SMP: Total of 4 processors activated.
[    0.011550] CPU features: detected: 32-bit EL0 Support
[    0.011555] CPU features: detected: 32-bit EL1 Support
[    0.011562] CPU features: detected: Data cache clean to the PoU not required for I/D coherence
[    0.011568] CPU features: detected: Common not Private translations
[    0.011573] CPU features: detected: CRC32 instructions
[    0.011581] CPU features: detected: RCpc load-acquire (LDAPR)
[    0.011585] CPU features: detected: LSE atomic instructions
[    0.011590] CPU features: detected: Privileged Access Never
[    0.011595] CPU features: detected: RAS Extension Support
[    0.011602] CPU features: detected: Speculative Store Bypassing Safe (SSBS)
[    0.030102] CPU: All CPU(s) started at EL2
[    0.034004] devtmpfs: initialized
[    0.054307] Registered cp15_barrier emulation handler
[    0.054333] Registered setend emulation handler
[    0.054345] KASLR disabled due to lack of seed
[    0.054583] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.054613] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.055773] pinctrl core: initialized pinctrl subsystem
[    0.057379] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.059034] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    0.059482] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.059888] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.059967] audit: initializing netlink subsys (disabled)
[    0.060176] audit: type=2000 audit(0.060:1): state=initialized audit_enabled=0 res=1
[    0.062729] thermal_sys: Registered thermal governor 'fair_share'
[    0.062744] thermal_sys: Registered thermal governor 'bang_bang'
[    0.062751] thermal_sys: Registered thermal governor 'step_wise'
[    0.062756] thermal_sys: Registered thermal governor 'user_space'
[    0.063341] cpuidle: using governor menu
[    0.063621] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.063787] ASID allocator initialised with 65536 entries
[    0.065749] Serial: AMBA PL011 UART driver
[    0.079680] platform fe0a0000.hdmi: Fixing up cyclic dependency with fe040000.vop
[    0.104419] rockchip-gpio fdd60000.gpio: probed /pinctrl/gpio@fdd60000
[    0.105193] rockchip-gpio fe740000.gpio: probed /pinctrl/gpio@fe740000
[    0.105906] rockchip-gpio fe750000.gpio: probed /pinctrl/gpio@fe750000
[    0.106658] rockchip-gpio fe760000.gpio: probed /pinctrl/gpio@fe760000
[    0.107373] rockchip-gpio fe770000.gpio: probed /pinctrl/gpio@fe770000
[    0.112981] platform hdmi-con: Fixing up cyclic dependency with fe0a0000.hdmi
[    0.130297] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.130318] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.130327] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.130335] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.131815] cryptd: max_cpu_qlen set to 1000
[    0.198345] raid6: neonx8   gen()  1408 MB/s
[    0.266520] raid6: neonx4   gen()  1438 MB/s
[    0.334735] raid6: neonx2   gen()  1283 MB/s
[    0.402798] raid6: neonx1   gen()  1088 MB/s
[    0.470906] raid6: int64x8  gen()   956 MB/s
[    0.538999] raid6: int64x4  gen()  1047 MB/s
[    0.607079] raid6: int64x2  gen()   935 MB/s
[    0.675169] raid6: int64x1  gen()   689 MB/s
[    0.675179] raid6: using algorithm neonx4 gen() 1438 MB/s
[    0.743260] raid6: .... xor() 1099 MB/s, rmw enabled
[    0.743269] raid6: using neon recovery algorithm
[    0.747184] iommu: Default domain type: Translated 
[    0.747204] iommu: DMA domain TLB invalidation policy: strict mode 
[    0.747561] SCSI subsystem initialized
[    0.747891] usbcore: registered new interface driver usbfs
[    0.747954] usbcore: registered new interface driver hub
[    0.748005] usbcore: registered new device driver usb
[    0.748703] pps_core: LinuxPPS API ver. 1 registered
[    0.748713] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.748738] PTP clock support registered
[    0.748981] EDAC MC: Ver: 3.0.0
[    0.750486] arm-scmi firmware:scmi: Enabled polling mode TX channel - prot_id:16
[    0.750672] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.
[    0.750745] arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
[    0.752042] Advanced Linux Sound Architecture Driver Initialized.
[    0.753157] vgaarb: loaded
[    0.753631] clocksource: Switched to clocksource arch_sys_counter
[    0.753957] VFS: Disk quotas dquot_6.6.0
[    0.754018] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.765873] NET: Registered PF_INET protocol family
[    0.766371] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.771036] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
[    0.771195] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.771714] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.772641] TCP: Hash tables configured (established 65536 bind 65536)
[    0.772792] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    0.772960] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    0.773270] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.773817] RPC: Registered named UNIX socket transport module.
[    0.773828] RPC: Registered udp transport module.
[    0.773833] RPC: Registered tcp transport module.
[    0.773838] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.773849] PCI: CLS 0 bytes, default 64
[    0.774251] Trying to unpack rootfs image as initramfs...
[    0.785716] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available
[    0.786639] kvm [1]: IPA Size Limit: 40 bits
[    0.786680] kvm [1]: GICv3: no GICV resource entry
[    0.786689] kvm [1]: disabling GICv2 emulation
[    0.786713] kvm [1]: GIC system register CPU interface enabled
[    0.786928] kvm [1]: vgic interrupt IRQ9
[    0.787177] kvm [1]: VHE mode initialized successfully
[    0.790078] Initialise system trusted keyrings
[    0.790349] workingset: timestamp_bits=44 max_order=21 bucket_order=0
[    0.798227] zbud: loaded
[    0.800382] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.801519] NFS: Registering the id_resolver key type
[    0.801557] Key type id_resolver registered
[    0.801564] Key type id_legacy registered
[    0.801714] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.801725] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.801732] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.803319] JFS: nTxBlock = 8192, nTxLock = 65536
[    0.809685] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[    0.812002] ocfs2: Registered cluster interface o2cb
[    0.812263] OCFS2 User DLM kernel interface loaded
[    0.814421] gfs2: GFS2 installed
[    0.868781] xor: measuring software checksum speed
[    0.874570]    8regs           :  1719 MB/sec
[    0.880846]    32regs          :  1575 MB/sec
[    0.886673]    arm64_neon      :  1700 MB/sec
[    0.886686] xor: using function: 8regs (1719 MB/sec)
[    0.886703] Key type asymmetric registered
[    0.886711] Asymmetric key parser 'x509' registered
[    0.886862] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.887127] io scheduler mq-deadline registered
[    0.887141] io scheduler kyber registered
[    0.887221] io scheduler bfq registered
[    0.900959] rockchip-snps-pcie3-phy fe8c0000.phy: failed to find rockchip,pipe_grf regmap
[    0.912600] rockchip-dw-pcie 3c0800000.pcie: host bridge /pcie@fe280000 ranges:
[    0.912662] rockchip-dw-pcie 3c0800000.pcie:       IO 0x0381000000..0x03810fffff -> 0x0001000000
[    0.912690] rockchip-dw-pcie 3c0800000.pcie:      MEM 0x0381100000..0x03bfffffff -> 0x0002000000
[    0.912834] rockchip-dw-pcie 3c0800000.pcie: iATU unroll: enabled
[    0.912845] rockchip-dw-pcie 3c0800000.pcie: Detected iATU regions: 8 outbound, 8 inbound
[    1.117706] rockchip-dw-pcie 3c0800000.pcie: Link up
[    1.117964] rockchip-dw-pcie 3c0800000.pcie: PCI host bridge to bus 0002:20
[    1.117981] pci_bus 0002:20: root bus resource [bus 20-2f]
[    1.117999] pci_bus 0002:20: root bus resource [io  0x0000-0xfffff] (bus address [0x1000000-0x10fffff])
[    1.118011] pci_bus 0002:20: root bus resource [mem 0x381100000-0x3bfffffff] (bus address [0x02000000-0x40efffff])
[    1.118069] pci 0002:20:00.0: [1d87:3566] type 01 class 0x060400
[    1.118095] pci 0002:20:00.0: reg 0x10: [mem 0x00000000-0x3fffffff]
[    1.118110] pci 0002:20:00.0: reg 0x14: [mem 0x00000000-0x3fffffff]
[    1.118124] pci 0002:20:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
[    1.118203] pci 0002:20:00.0: supports D1 D2
[    1.118213] pci 0002:20:00.0: PME# supported from D0 D1 D3hot
[    1.126883] pci 0002:20:00.0: Primary bus is hard wired to 0
[    1.126905] pci 0002:20:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring
[    1.127207] pci 0002:21:00.0: [2646:2263] type 00 class 0x010802
[    1.127308] pci 0002:21:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    1.127923] pci 0002:21:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0002:20:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[    1.146008] pci_bus 0002:21: busn_res: [bus 21-2f] end is updated to 21
[    1.146075] pci 0002:20:00.0: BAR 0: no space for [mem size 0x40000000]
[    1.146089] pci 0002:20:00.0: BAR 0: failed to assign [mem size 0x40000000]
[    1.146102] pci 0002:20:00.0: BAR 1: no space for [mem size 0x40000000]
[    1.146112] pci 0002:20:00.0: BAR 1: failed to assign [mem size 0x40000000]
[    1.146123] pci 0002:20:00.0: BAR 14: assigned [mem 0x381100000-0x3811fffff]
[    1.146136] pci 0002:20:00.0: BAR 6: assigned [mem 0x381200000-0x38120ffff pref]
[    1.146154] pci 0002:21:00.0: BAR 0: assigned [mem 0x381100000-0x381103fff 64bit]
[    1.146208] pci 0002:20:00.0: PCI bridge to [bus 21]
[    1.146220] pci 0002:20:00.0:   bridge window [mem 0x381100000-0x3811fffff]
[    1.146823] pcieport 0002:20:00.0: PME: Signaling with IRQ 52
[    1.158284] dma-pl330 fe530000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.158311] dma-pl330 fe530000.dma-controller: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    1.161786] dma-pl330 fe550000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.161815] dma-pl330 fe550000.dma-controller: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    1.165078] arm-scmi firmware:scmi: Failed. SCMI protocol 23 not active.
[    1.166635] arm-scmi firmware:scmi: Failed. SCMI protocol 22 not active.
[    1.173944] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.177344] printk: console [ttyS2] disabled
[    1.177440] fe660000.serial: ttyS2 at MMIO 0xfe660000 (irq = 35, base_baud = 1500000) is a 16550A
[    1.178999] printk: console [ttyS2] enabled
[    1.180584] Serial: AMBA driver
[    1.183284] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    1.189730] brd: module loaded
[    1.196217] loop: module loaded
[    1.201317] tun: Universal TUN/TAP device driver, 1.6
[    1.202188] usbcore: registered new interface driver cdc_ether
[    1.202288] usbcore: registered new interface driver cdc_subset
[    1.202608] VFIO - User Level meta-driver version: 0.3
[    1.205046] rockchip-naneng-combphy fe830000.phy: wait phy status ready timeout
[    1.210650] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.210727] ehci-pci: EHCI PCI platform driver
[    1.210830] ehci-platform: EHCI generic platform driver
[    1.213301] ehci-platform fd800000.usb: EHCI Host Controller
[    1.213349] ehci-platform fd800000.usb: new USB bus registered, assigned bus number 1
[    1.213553] ehci-platform fd800000.usb: irq 20, io mem 0xfd800000
[    1.225672] ehci-platform fd800000.usb: USB 2.0 started, EHCI 1.00
[    1.225975] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.18
[    1.225994] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.226005] usb usb1: Product: EHCI Host Controller
[    1.226013] usb usb1: Manufacturer: Linux 5.18.0-odroid-arm64 ehci_hcd
[    1.226021] usb usb1: SerialNumber: fd800000.usb
[    1.226780] hub 1-0:1.0: USB hub found
[    1.226833] hub 1-0:1.0: 1 port detected
[    1.229783] ehci-platform fd880000.usb: EHCI Host Controller
[    1.229829] ehci-platform fd880000.usb: new USB bus registered, assigned bus number 2
[    1.229996] ehci-platform fd880000.usb: irq 22, io mem 0xfd880000
[    1.245682] ehci-platform fd880000.usb: USB 2.0 started, EHCI 1.00
[    1.245983] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.18
[    1.246001] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.246012] usb usb2: Product: EHCI Host Controller
[    1.246020] usb usb2: Manufacturer: Linux 5.18.0-odroid-arm64 ehci_hcd
[    1.246028] usb usb2: SerialNumber: fd880000.usb
[    1.246716] hub 2-0:1.0: USB hub found
[    1.246767] hub 2-0:1.0: 1 port detected
[    1.247621] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.247659] ohci-pci: OHCI PCI platform driver
[    1.247764] ohci-platform: OHCI generic platform driver
[    1.248188] ohci-platform fd840000.usb: Generic Platform OHCI controller
[    1.248222] ohci-platform fd840000.usb: new USB bus registered, assigned bus number 3
[    1.248389] ohci-platform fd840000.usb: irq 21, io mem 0xfd840000
[    1.286619] Freeing initrd memory: 8288K
[    1.311890] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.18
[    1.311920] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.311930] usb usb3: Product: Generic Platform OHCI controller
[    1.311939] usb usb3: Manufacturer: Linux 5.18.0-odroid-arm64 ohci_hcd
[    1.311947] usb usb3: SerialNumber: fd840000.usb
[    1.312705] hub 3-0:1.0: USB hub found
[    1.312761] hub 3-0:1.0: 1 port detected
[    1.313673] ohci-platform fd8c0000.usb: Generic Platform OHCI controller
[    1.313713] ohci-platform fd8c0000.usb: new USB bus registered, assigned bus number 4
[    1.313896] ohci-platform fd8c0000.usb: irq 23, io mem 0xfd8c0000
[    1.377899] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.18
[    1.377927] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.377939] usb usb4: Product: Generic Platform OHCI controller
[    1.377947] usb usb4: Manufacturer: Linux 5.18.0-odroid-arm64 ohci_hcd
[    1.377956] usb usb4: SerialNumber: fd8c0000.usb
[    1.378721] hub 4-0:1.0: USB hub found
[    1.378778] hub 4-0:1.0: 1 port detected
[    1.380589] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    1.380631] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5
[    1.380782] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[    1.380859] xhci-hcd xhci-hcd.0.auto: irq 19, io mem 0xfd000000
[    1.381287] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.18
[    1.381304] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.381315] usb usb5: Product: xHCI Host Controller
[    1.381323] usb usb5: Manufacturer: Linux 5.18.0-odroid-arm64 xhci-hcd
[    1.381332] usb usb5: SerialNumber: xhci-hcd.0.auto
[    1.382086] hub 5-0:1.0: USB hub found
[    1.382141] hub 5-0:1.0: 1 port detected
[    1.382598] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    1.382624] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 6
[    1.382646] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    1.382739] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.382888] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.18
[    1.382905] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.382915] usb usb6: Product: xHCI Host Controller
[    1.382924] usb usb6: Manufacturer: Linux 5.18.0-odroid-arm64 xhci-hcd
[    1.382932] usb usb6: SerialNumber: xhci-hcd.0.auto
[    1.383578] hub 6-0:1.0: USB hub found
[    1.383639] hub 6-0:1.0: 1 port detected
[    1.384380] usbcore: registered new interface driver usb-storage
[    1.387780] mousedev: PS/2 mouse device common for all mice
[    1.389024] i2c_dev: i2c /dev entries driver
[    1.391882] fan53555-regulator 3-001c: FAN53555 Option[12] Rev[15] Detected!
[    1.401070] rk808 3-0020: chip id: 0x8090
[    1.434590] random: fast init done
[    1.444613] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    1.444656] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    1.511520] arm-scmi firmware:scmi: Failed. SCMI protocol 21 not active.
[    1.518837] arm-scmi firmware:scmi: Failed. SCMI protocol 19 not active.
[    1.520282] sdhci: Secure Digital Host Controller Interface driver
[    1.520297] sdhci: Copyright(c) Pierre Ossman
[    1.520474] Synopsys Designware Multimedia Card Interface Driver
[    1.521270] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.521768] dwmmc_rockchip fe2b0000.mmc: IDMAC supports 32-bit address mode.
[    1.521815] dwmmc_rockchip fe2b0000.mmc: Using internal DMA controller.
[    1.521823] dwmmc_rockchip fe2b0000.mmc: Version ID is 270a
[    1.521873] dwmmc_rockchip fe2b0000.mmc: DW MMC controller at irq 30,32 bit host data width,256 deep fifo
[    1.522289] dwmmc_rockchip fe2b0000.mmc: Got CD GPIO
[    1.523196] ledtrig-cpu: registered to indicate activity on CPUs
[    1.523663] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[    1.524510] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.524901] hid: raw HID events driver (C) Jiri Kosina
[    1.525567] usbcore: registered new interface driver usbhid
[    1.525588] usbhid: USB HID core driver
[    1.529354] NET: Registered PF_INET6 protocol family
[    1.530100] Segment Routing with IPv6
[    1.530120] In-situ OAM (IOAM) with IPv6
[    1.530159] NET: Registered PF_PACKET protocol family
[    1.530172] NET: Registered PF_KEY protocol family
[    1.530285] 8021q: 802.1Q VLAN Support v1.8
[    1.530386] Key type dns_resolver registered
[    1.530682] registered taskstats version 1
[    1.530695] Loading compiled-in X.509 certificates
[    1.530950] zswap: loaded using pool lzo/zbud
[    1.531217] Key type ._fscrypt registered
[    1.531221] Key type .fscrypt registered
[    1.531224] Key type fscrypt-provisioning registered
[    1.531791] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=no
[    1.532066] Key type encrypted registered
[    1.534208] mmc_host mmc1: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    1.567891] ALSA device list:
[    1.567906]   No soundcards found.
[    1.569163] Freeing unused kernel memory: 3328K
[    1.589744] Run /init as init process
[    1.589751]   with arguments:
[    1.589755]     /init
[    1.589758]   with environment:
[    1.589760]     HOME=/
[    1.589763]     TERM=linux
[    1.877574] libata version 3.00 loaded.
[    1.905971] ahci fc800000.sata: supply ahci not found, using dummy regulator
[    1.906258] ahci fc800000.sata: supply phy not found, using dummy regulator
[    1.906460] ahci fc800000.sata: supply target not found, using dummy regulator
[    1.906615] ahci fc800000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[    1.906626] ahci fc800000.sata: flags: ncq sntf pm led clo only pmp fbs pio slum part ccc apst 
[    1.906642] ahci fc800000.sata: port 0 is not capable of FBS
[    1.908572] rockchip-vop2 fe040000.vop: Adding to iommu group 0
[    1.915127] nvme nvme0: pci function 0002:21:00.0
[    1.915330] nvme 0002:21:00.0: enabling device (0000 -> 0002)
[    1.931493] rk808-rtc rk808-rtc: registered as rtc0
[    1.935336] rk808-rtc rk808-rtc: setting system clock to 2023-01-20T14:47:38 UTC (1674226058)
[    1.936082] scsi host0: ahci
[    1.947780] nvme nvme0: missing or invalid SUBNQN field.
[    1.962336] ata1: SATA max UDMA/133 mmio [mem 0xfc800000-0xfc800fff] port 0x100 irq 18
[    1.962676] rockchip-drm display-subsystem: bound fe040000.vop (ops vop2_component_ops [rockchipdrm])
[    1.979898] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    1.988482] mmc0: SDHCI controller on fe310000.mmc [fe310000.mmc] using ADMA
[    1.990854] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    1.991381] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm])
[    1.996132] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    1.996229] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[    1.996322] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[    2.021936] nvme nvme0: 1/0/0 default/read/poll queues
[    2.023487]  nvme0n1: p1 p2 p3 < p5 >
[    2.275859] ata1: SATA link down (SStatus 0 SControl 300)
[    2.281244] rk_gmac-dwmac fe2a0000.ethernet: IRQ eth_lpi not found
[    2.281780] rk_gmac-dwmac fe2a0000.ethernet: no regulator found
[    2.282328] rk_gmac-dwmac fe2a0000.ethernet: clock input or output? (output).
[    2.282336] rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x4f).
[    2.282341] rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2d).
[    2.282352] rk_gmac-dwmac fe2a0000.ethernet: integrated PHY? (no).
[    2.287396] rk_gmac-dwmac fe2a0000.ethernet: init for RGMII
[    2.287607] rk_gmac-dwmac fe2a0000.ethernet: User ID: 0x30, Synopsys ID: 0x51
[    2.287623] rk_gmac-dwmac fe2a0000.ethernet: 	DWMAC4/5
[    2.287629] rk_gmac-dwmac fe2a0000.ethernet: DMA HW capability register supported
[    2.287632] rk_gmac-dwmac fe2a0000.ethernet: RX Checksum Offload Engine supported
[    2.287635] rk_gmac-dwmac fe2a0000.ethernet: TX Checksum insertion supported
[    2.287638] rk_gmac-dwmac fe2a0000.ethernet: Wake-Up On Lan supported
[    2.287718] rk_gmac-dwmac fe2a0000.ethernet: TSO supported
[    2.287723] rk_gmac-dwmac fe2a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.287732] rk_gmac-dwmac fe2a0000.ethernet: device MAC address 3a:a9:25:e2:41:4b
[    2.287738] rk_gmac-dwmac fe2a0000.ethernet: Enabled RFS Flow TC (entries=10)
[    2.287748] rk_gmac-dwmac fe2a0000.ethernet: TSO feature enabled
[    2.287752] rk_gmac-dwmac fe2a0000.ethernet: Using 32 bits DMA width
[    5.102158] EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Quota mode: none.
[    5.232829] systemd[1]: systemd 247.3-7+deb11u1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[    5.233345] systemd[1]: Detected architecture arm64.
[    5.233918] systemd[1]: Set hostname to <Odroid>.
[    5.285890] dw-apb-uart fe660000.serial: forbid DMA for kernel console
[    5.481288] systemd[1]: Queued start job for default target Graphical Interface.
[    6.993633] random: crng init done
[    7.011961] systemd[1]: Created slice system-getty.slice.
[    7.013479] systemd[1]: Created slice system-modprobe.slice.
[    7.014877] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    7.016152] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.017243] systemd[1]: Created slice User and Session Slice.
[    7.017527] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    7.017754] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.018361] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    7.018507] systemd[1]: Reached target Local Encrypted Volumes.
[    7.018627] systemd[1]: Reached target Paths.
[    7.018683] systemd[1]: Reached target Remote File Systems.
[    7.018726] systemd[1]: Reached target Slices.
[    7.019235] systemd[1]: Listening on Syslog Socket.
[    7.019560] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.019749] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    7.020251] systemd[1]: Listening on Journal Audit Socket.
[    7.020569] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.020964] systemd[1]: Listening on Journal Socket.
[    7.021779] systemd[1]: Listening on udev Control Socket.
[    7.022164] systemd[1]: Listening on udev Kernel Socket.
[    7.025221] systemd[1]: Mounting Huge Pages File System...
[    7.028673] systemd[1]: Mounting POSIX Message Queue File System...
[    7.032443] systemd[1]: Mounting Kernel Debug File System...
[    7.032954] systemd[1]: Condition check resulted in Kernel Trace File System being skipped.
[    7.037424] systemd[1]: Starting Set the console keyboard layout...
[    7.041279] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    7.045306] systemd[1]: Starting Load Kernel Module configfs...
[    7.049353] systemd[1]: Starting Load Kernel Module drm...
[    7.053199] systemd[1]: Starting Load Kernel Module fuse...
[    7.054452] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    7.054659] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    7.060799] systemd[1]: Starting Journal Service...
[    7.065038] fuse: init (API version 7.36)
[    7.066236] systemd[1]: Starting Load Kernel Modules...
[    7.070499] systemd[1]: Starting Remount Root and Kernel File Systems...
[    7.074891] systemd[1]: Starting Coldplug All udev Devices...
[    7.082908] systemd[1]: Mounted Huge Pages File System.
[    7.083428] systemd[1]: Mounted POSIX Message Queue File System.
[    7.083904] systemd[1]: Mounted Kernel Debug File System.
[    7.085461] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    7.087118] systemd[1]: modprobe@configfs.service: Succeeded.
[    7.088080] systemd[1]: Finished Load Kernel Module configfs.
[    7.089345] systemd[1]: modprobe@drm.service: Succeeded.
[    7.090390] systemd[1]: Finished Load Kernel Module drm.
[    7.091821] systemd[1]: modprobe@fuse.service: Succeeded.
[    7.092718] systemd[1]: Finished Load Kernel Module fuse.
[    7.097354] systemd[1]: Mounting FUSE Control File System...
[    7.101533] systemd[1]: Mounting Kernel Configuration File System...
[    7.111264] systemd[1]: Mounted FUSE Control File System.
[    7.111783] systemd[1]: Mounted Kernel Configuration File System.
[    7.118635] systemd[1]: Finished Load Kernel Modules.
[    7.122644] systemd[1]: Starting Apply Kernel Variables...
[    7.123077] EXT4-fs (nvme0n1p2): re-mounted. Quota mode: none.
[    7.132218] systemd[1]: Finished Remount Root and Kernel File Systems.
[    7.133573] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[    7.133804] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    7.137182] systemd[1]: Starting Load/Save Random Seed...
[    7.141241] systemd[1]: Starting Create System Users...
[    7.168050] systemd[1]: Finished Load/Save Random Seed.
[    7.168612] systemd[1]: Condition check resulted in First Boot Complete being skipped.
[    7.171753] systemd[1]: Finished Apply Kernel Variables.
[    7.186199] systemd[1]: Finished Create System Users.
[    7.189825] systemd[1]: Starting Create Static Device Nodes in /dev...
[    7.224082] systemd[1]: Finished Create Static Device Nodes in /dev.
[    7.229583] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    7.258410] systemd[1]: Finished Set the console keyboard layout.
[    7.259179] systemd[1]: Reached target Local File Systems (Pre).
[    7.260004] systemd[1]: Set up automount mnt-JeNas_Download.automount.
[    7.260885] systemd[1]: Set up automount mnt-JeNas_NetBackup.automount.
[    7.262195] systemd[1]: Set up automount mnt-JeNas_Video.automount.
[    7.263075] systemd[1]: Set up automount mnt-JeNas_Video2.automount.
[    7.280388] systemd[1]: Started Rule-based Manager for Device Events and Files.
[    7.315809] systemd[1]: Started Journal Service.
[    7.345107] systemd-journald[927]: Received client request to flush runtime journal.
[    7.572209] panfrost fde60000.gpu: clock rate = 594000000
[    7.572244] panfrost fde60000.gpu: bus_clock rate = 500000000
[    7.574789] panfrost fde60000.gpu: mali-g52 id 0x7402 major 0x1 minor 0x0 status 0x0
[    7.574805] panfrost fde60000.gpu: features: 00000000,00000cf7, issues: 00000000,00000400
[    7.574811] panfrost fde60000.gpu: Features: L2:0x07110206 Shader:0x00000002 Tiler:0x00000209 Mem:0x1 MMU:0x00002823 AS:0xff JS:0x7
[    7.574817] panfrost fde60000.gpu: shader_present=0x1 l2_present=0x1
[    7.600228] [drm] Initialized panfrost 1.2.0 20180908 for fde60000.gpu on minor 1
[    7.697108] Adding 999420k swap on /dev/nvme0n1p5.  Priority:-2 extents:1 across:999420k SSFS
[    8.002127] ext2 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[    8.241697] rk_gmac-dwmac fe2a0000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[    8.285763] rk_gmac-dwmac fe2a0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[    8.293688] dwmac4: Master AXI performs any burst length
[    8.293715] rk_gmac-dwmac fe2a0000.ethernet eth0: No Safety Features support found
[    8.293740] rk_gmac-dwmac fe2a0000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[    8.293942] rk_gmac-dwmac fe2a0000.ethernet eth0: registered PTP clock
[    8.294243] rk_gmac-dwmac fe2a0000.ethernet eth0: configuring for phy/rgmii link mode
[    9.144133] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    9.145804] Bridge firewalling registered
[    9.297469] Initializing XFRM netlink socket
[   10.108415] docker0: port 1(veth4423dd7) entered blocking state
[   10.108449] docker0: port 1(veth4423dd7) entered disabled state
[   10.108645] device veth4423dd7 entered promiscuous mode
[   10.122447] docker0: port 1(veth4423dd7) entered blocking state
[   10.122474] docker0: port 1(veth4423dd7) entered forwarding state
[   10.124137] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[   10.124494] docker0: port 1(veth4423dd7) entered disabled state
[   10.133025] br-743eb0c390da: port 1(vethc9aa3ea) entered blocking state
[   10.133070] br-743eb0c390da: port 1(vethc9aa3ea) entered disabled state
[   10.133276] device vethc9aa3ea entered promiscuous mode
[   10.133812] br-743eb0c390da: port 1(vethc9aa3ea) entered blocking state
[   10.133836] br-743eb0c390da: port 1(vethc9aa3ea) entered forwarding state
[   10.133944] IPv6: ADDRCONF(NETDEV_CHANGE): br-743eb0c390da: link becomes ready
[   10.134239] br-743eb0c390da: port 1(vethc9aa3ea) entered disabled state
[   10.135585] br-853033c56151: port 1(vethe2c840a) entered blocking state
[   10.135620] br-853033c56151: port 1(vethe2c840a) entered disabled state
[   10.135828] device vethe2c840a entered promiscuous mode
[   10.136265] br-853033c56151: port 1(vethe2c840a) entered blocking state
[   10.136284] br-853033c56151: port 1(vethe2c840a) entered forwarding state
[   10.136516] IPv6: ADDRCONF(NETDEV_CHANGE): br-853033c56151: link becomes ready
[   10.136795] br-853033c56151: port 1(vethe2c840a) entered disabled state
[   10.136983] br-b06ce6dc30a8: port 1(veth077ec5d) entered blocking state
[   10.137015] br-b06ce6dc30a8: port 1(veth077ec5d) entered disabled state
[   10.137210] device veth077ec5d entered promiscuous mode
[   10.138552] br-dd454ea8894b: port 1(veth5e48401) entered blocking state
[   10.138598] br-dd454ea8894b: port 1(veth5e48401) entered disabled state
[   10.142005] device veth5e48401 entered promiscuous mode
[   10.142483] br-b06ce6dc30a8: port 1(veth077ec5d) entered blocking state
[   10.142500] br-b06ce6dc30a8: port 1(veth077ec5d) entered forwarding state
[   10.142858] br-dd454ea8894b: port 1(veth5e48401) entered blocking state
[   10.142872] br-dd454ea8894b: port 1(veth5e48401) entered forwarding state
[   10.143044] IPv6: ADDRCONF(NETDEV_CHANGE): br-b06ce6dc30a8: link becomes ready
[   10.143320] br-b06ce6dc30a8: port 1(veth077ec5d) entered disabled state
[   10.146642] br-dd454ea8894b: port 1(veth5e48401) entered disabled state
[   10.156556] docker0: port 2(veth0ae3e5c) entered blocking state
[   10.156608] docker0: port 2(veth0ae3e5c) entered disabled state
[   10.156882] device veth0ae3e5c entered promiscuous mode
[   10.157418] docker0: port 2(veth0ae3e5c) entered blocking state
[   10.157446] docker0: port 2(veth0ae3e5c) entered forwarding state
[   10.333631] docker0: port 2(veth0ae3e5c) entered disabled state
[   10.527093] FS-Cache: Loaded
[   10.547085] Key type cifs.spnego registered
[   10.547109] Key type cifs.idmap registered
[   10.548650] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[   10.548673] CIFS: Attempting to mount \\192.168.16.40\video2
[   10.591783] CIFS: Attempting to mount \\192.168.16.40\video2
[   10.622929] CIFS: Attempting to mount \\192.168.16.40\video2
[   10.645347] CIFS: Attempting to mount \\192.168.16.40\video2
[   10.876030] br-dd454ea8894b: port 1(veth5e48401) entered disabled state
[   10.878625] device veth5e48401 left promiscuous mode
[   10.878650] br-dd454ea8894b: port 1(veth5e48401) entered disabled state
[   11.385210] eth0: renamed from veth720454e
[   11.406732] IPv6: ADDRCONF(NETDEV_CHANGE): veth4423dd7: link becomes ready
[   11.406872] docker0: port 1(veth4423dd7) entered blocking state
[   11.406885] docker0: port 1(veth4423dd7) entered forwarding state
[   11.689775] eth0: renamed from veth8249317
[   11.723790] IPv6: ADDRCONF(NETDEV_CHANGE): veth0ae3e5c: link becomes ready
[   11.723975] docker0: port 2(veth0ae3e5c) entered blocking state
[   11.723992] docker0: port 2(veth0ae3e5c) entered forwarding state
[   12.251149] eth0: renamed from veth4dedcc8
[   12.278979] IPv6: ADDRCONF(NETDEV_CHANGE): vethc9aa3ea: link becomes ready
[   12.279126] br-743eb0c390da: port 1(vethc9aa3ea) entered blocking state
[   12.279162] br-743eb0c390da: port 1(vethc9aa3ea) entered forwarding state
[   12.367685] eth0: renamed from veth9061418
[   12.386809] IPv6: ADDRCONF(NETDEV_CHANGE): vethe2c840a: link becomes ready
[   12.386987] br-853033c56151: port 1(vethe2c840a) entered blocking state
[   12.387001] br-853033c56151: port 1(vethe2c840a) entered forwarding state
[   12.422360] rk_gmac-dwmac fe2a0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   12.422418] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   12.462634] eth0: renamed from veth37599a0
[   12.479303] IPv6: ADDRCONF(NETDEV_CHANGE): veth077ec5d: link becomes ready
[   12.479463] br-b06ce6dc30a8: port 1(veth077ec5d) entered blocking state
[   12.479480] br-b06ce6dc30a8: port 1(veth077ec5d) entered forwarding state
[   13.051789] docker0: port 2(veth0ae3e5c) entered disabled state
[   13.052026] veth8249317: renamed from eth0
[   13.116448] docker0: port 2(veth0ae3e5c) entered disabled state
[   13.119069] device veth0ae3e5c left promiscuous mode
[   13.119099] docker0: port 2(veth0ae3e5c) entered disabled state
[   13.229398] docker0: port 2(veth66f2eb0) entered blocking state
[   13.229435] docker0: port 2(veth66f2eb0) entered disabled state
[   13.229707] device veth66f2eb0 entered promiscuous mode
[   13.230090] docker0: port 2(veth66f2eb0) entered blocking state
[   13.230112] docker0: port 2(veth66f2eb0) entered forwarding state
[   13.409849] docker0: port 2(veth66f2eb0) entered disabled state
[   13.814820] eth0: renamed from veth08be8e4
[   13.842836] IPv6: ADDRCONF(NETDEV_CHANGE): veth66f2eb0: link becomes ready
[   13.842980] docker0: port 2(veth66f2eb0) entered blocking state
[   13.842994] docker0: port 2(veth66f2eb0) entered forwarding state
[   15.076195] docker0: port 2(veth66f2eb0) entered disabled state
[   15.076594] veth08be8e4: renamed from eth0
[   15.149544] docker0: port 2(veth66f2eb0) entered disabled state
[   15.151759] device veth66f2eb0 left promiscuous mode
[   15.151783] docker0: port 2(veth66f2eb0) entered disabled state
[   15.266914] docker0: port 2(veth0984728) entered blocking state
[   15.266952] docker0: port 2(veth0984728) entered disabled state
[   15.267181] device veth0984728 entered promiscuous mode
[   15.267570] docker0: port 2(veth0984728) entered blocking state
[   15.267592] docker0: port 2(veth0984728) entered forwarding state
[   15.858810] eth0: renamed from veth9edccbd
[   15.894847] IPv6: ADDRCONF(NETDEV_CHANGE): veth0984728: link becomes ready
[   17.102964] docker0: port 2(veth0984728) entered disabled state
[   17.103218] veth9edccbd: renamed from eth0
[   17.157000] docker0: port 2(veth0984728) entered disabled state
[   17.159298] device veth0984728 left promiscuous mode
[   17.159326] docker0: port 2(veth0984728) entered disabled state
[   17.506353] docker0: port 2(vethb620cc9) entered blocking state
[   17.506391] docker0: port 2(vethb620cc9) entered disabled state
[   17.506595] device vethb620cc9 entered promiscuous mode
[   17.506959] docker0: port 2(vethb620cc9) entered blocking state
[   17.506982] docker0: port 2(vethb620cc9) entered forwarding state
[   18.113882] docker0: port 2(vethb620cc9) entered disabled state
[   18.230816] eth0: renamed from veth45b7dd9
[   18.250841] IPv6: ADDRCONF(NETDEV_CHANGE): vethb620cc9: link becomes ready
[   18.250989] docker0: port 2(vethb620cc9) entered blocking state
[   18.251024] docker0: port 2(vethb620cc9) entered forwarding state
[   19.445774] docker0: port 2(vethb620cc9) entered disabled state
[   19.446049] veth45b7dd9: renamed from eth0
[   19.507549] docker0: port 2(vethb620cc9) entered disabled state
[   19.510880] device vethb620cc9 left promiscuous mode
[   19.510915] docker0: port 2(vethb620cc9) entered disabled state
[   20.235890] docker0: port 2(vetha379d7b) entered blocking state
[   20.235923] docker0: port 2(vetha379d7b) entered disabled state
[   20.236101] device vetha379d7b entered promiscuous mode
[   20.236414] docker0: port 2(vetha379d7b) entered blocking state
[   20.236428] docker0: port 2(vetha379d7b) entered forwarding state
[   20.446200] docker0: port 2(vetha379d7b) entered disabled state
[   20.760418] eth0: renamed from vethdcebbc1
[   20.778624] IPv6: ADDRCONF(NETDEV_CHANGE): vetha379d7b: link becomes ready
[   20.778763] docker0: port 2(vetha379d7b) entered blocking state
[   20.778774] docker0: port 2(vetha379d7b) entered forwarding state
[   21.960259] docker0: port 2(vetha379d7b) entered disabled state
[   21.960499] vethdcebbc1: renamed from eth0
[   22.029037] docker0: port 2(vetha379d7b) entered disabled state
[   22.031721] device vetha379d7b left promiscuous mode
[   22.031743] docker0: port 2(vetha379d7b) entered disabled state
[   23.554381] docker0: port 2(vethc187712) entered blocking state
[   23.554419] docker0: port 2(vethc187712) entered disabled state
[   23.554679] device vethc187712 entered promiscuous mode
[   24.162653] eth0: renamed from veth0c708f0
[   24.182619] IPv6: ADDRCONF(NETDEV_CHANGE): vethc187712: link becomes ready
[   24.182760] docker0: port 2(vethc187712) entered blocking state
[   24.182772] docker0: port 2(vethc187712) entered forwarding state
[   25.354118] docker0: port 2(vethc187712) entered disabled state
[   25.354313] veth0c708f0: renamed from eth0
[   25.400878] docker0: port 2(vethc187712) entered disabled state
[   25.403473] device vethc187712 left promiscuous mode
[   25.403496] docker0: port 2(vethc187712) entered disabled state
[   28.542429] docker0: port 2(veth3d85355) entered blocking state
[   28.542462] docker0: port 2(veth3d85355) entered disabled state
[   28.542626] device veth3d85355 entered promiscuous mode
[   29.028383] eth0: renamed from veth37f84c2

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Well this is not encouraging!

I installed Debian Bullseye (from netboot) with Cockpit and Docker. I did not install Webmin, thinking that might be the source of the crashing. Unfortunately I was wrong :( After about 10.000 seconds the Odroid M1 crashed again. This time I was ready and made a picture "grasping" the start of the crash (and subsequent errors). I really (really!) need some help with this because I am at a loss here! Note that this error occurred with the Toshiba drive (the Kingston had his share of crashes).

Image

EDIT: It might be useful to mention that I installed Portainer and Watchtower under Docker. I noticed Portainer would become unresponsive after installing a new container and I had to restart Docker. Also some containers were unreachable after installing. Something I have never experienced on my x86/64 devices or that fruity Pi 4B before. Am I using the wrong version of Docker? I installed it from the bullseye repo though.

User avatar
mad_ady
Posts: 11208
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, H2, Go, Go Advance, M1
Location: Bucharest, Romania
Has thanked: 647 times
Been thanked: 1059 times
Contact:

Re: NVME drives not working (although they should?)

Post by mad_ady »

Hmm, is it possible that you experience this when the disk has been idle for a while and something tries to put nvme in a lower power mode? If yes, it shouldn't happen when you keep benchmarking the disk...
Maybe there's a kernel boot parameter that can tweak the behavior.

usual user
Posts: 55
Joined: Sat Sep 10, 2022 10:47 pm
languages_spoken: english
Has thanked: 1 time
Been thanked: 17 times
Contact:

Re: NVME drives not working (although they should?)

Post by usual user »

Looks like an APST (Autonomous Power State Transition) issue, see the first log message in the screenshot.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Tx for your replies. The M1 was being used during the crash. It hadn't been in idle state.

The question is: why does this occur on this particular M1 with at least two different NVMe's and at least 3 different OS's?

User avatar
tobetter
Posts: 11390
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 779 times
Been thanked: 1934 times
Contact:

Re: NVME drives not working (although they should?)

Post by tobetter »

Sjonnie wrote:
Sun Jan 22, 2023 6:42 pm
Tx for your replies. The M1 was being used during the crash. It hadn't been in idle state.

The question is: why does this occur on this particular M1 with at least two different NVMe's and at least 3 different OS's?
IMO, your NVMe would not be compatible with ODROID-M1 and I also doubt APST issue.
In order to test APST, please do install new OS again to SD or USB storage, not NVME, without any other additional packages like Docker. Then add nvme_core.default_ps_max_latency_us=0 to the line of LINUX_KERNEL_CMDLINE and run update-bootscript. The change will be applied from next power cycle.

After rebooting, share the output of cat /proc/cmdline and lspci. For testing your NVMe, you can run dd if=/dev/random of=/dev/nvme0n1 bs=1M conv=fsync, this will erase all your NVMe, but keep writing something to your NVMe so it will crash when the problem happens.

Also glad to know the output of uname -a.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Thanks for your reply but I am afraid I don't understand what you want me to do and where. Sorry about that.

I installed Ubuntu 20.04.4 LTS minimal from Hardkernel on an SD card. Booted from that but don't know where to modify the LINUX_KERNEL_CMDLINE. I searched but could not find. I tried to edit the entry in the petitboot menu but that did work. See picture:

Image

The update-bootscript did not change the file /boot/boot.scr unfortunately.

EDIT1: uname -a gives me
Linux server 4.19.219-odroid-arm64 #1 SMP Fri, 27 May 2022 03:16:46 +0000 aarch64 aarch64 aarch64 GNU/Linux
lspci was not installed and could not be installed (Couldn't find package)

usual user
Posts: 55
Joined: Sat Sep 10, 2022 10:47 pm
languages_spoken: english
Has thanked: 1 time
Been thanked: 17 times
Contact:

Re: NVME drives not working (although they should?)

Post by usual user »

Also the output of

Code: Select all

smartctl --all /dev/nvme0n1
is of some interest to get more details about the NVME used.

User avatar
tobetter
Posts: 11390
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 779 times
Been thanked: 1934 times
Contact:

Re: NVME drives not working (although they should?)

Post by tobetter »

Sjonnie wrote:
Sun Jan 22, 2023 8:11 pm
Thanks for your reply but I am afraid I don't understand what you want me to do and where. Sorry about that.

I installed Ubuntu 20.04.4 LTS minimal from Hardkernel on an SD card. Booted from that but don't know where to modify the LINUX_KERNEL_CMDLINE. I searched but could not find. I tried to edit the entry in the petitboot menu but that did work. See picture:

The update-bootscript did not change the file /boot/boot.scr unfortunately.
You must do this in Ubuntu 20.04, not in Petitboot. Petitboot have nothing to do for this problem.
EDIT1: uname -a gives me
Linux server 4.19.219-odroid-arm64 #1 SMP Fri, 27 May 2022 03:16:46 +0000 aarch64 aarch64 aarch64 GNU/Linux
lspci was not installed and could not be installed (Couldn't find package)
lspci is available with a package pciutils.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

E: unable to locate smartctl

Apparently the image is a bit more minimal than one would expect.

I did however install lspci. Running it gave me this:

Code: Select all

0002:20:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)
0002:21:00.0 Non-Volatile memory controller: Kingston Technology Company, Inc. Device 2263 (rev 03)
I will try to find a way to install smartctl...

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

tobetter wrote:
Sun Jan 22, 2023 8:21 pm

You must do this in Ubuntu 20.04, not in Petitboot. Petitboot have nothing to do for this problem.
Please tell me where? Or how? I searched and if Ubuntu it should be in /etc/default/grub. But I can't find that file (and it should be there, right?)

EDIT: Found smartctl. Will post output

User avatar
tobetter
Posts: 11390
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 779 times
Been thanked: 1934 times
Contact:

Re: NVME drives not working (although they should?)

Post by tobetter »

Sjonnie wrote:
Sun Jan 22, 2023 8:41 pm
tobetter wrote:
Sun Jan 22, 2023 8:21 pm

You must do this in Ubuntu 20.04, not in Petitboot. Petitboot have nothing to do for this problem.
Please tell me where? Or how? I searched and if Ubuntu it should be in /etc/default/grub. But I can't find that file (and it should be there, right?)
Do you have /etc/default/flash-kernel?

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Yes I do!

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Output from smartctl:

Image

usual user
Posts: 55
Joined: Sat Sep 10, 2022 10:47 pm
languages_spoken: english
Has thanked: 1 time
Been thanked: 17 times
Contact:

Re: NVME drives not working (although they should?)

Post by usual user »

Looks like there are Kingston NVME SSDs that have issues with there APST implementation. I haven't checked if it is known for your model, but if you disable ASPT you should reconsider your power supply.
A small calculation for the power requirement:
5W (ODROID M1) + 5W (2xUSB 2.0) + 9W (2xUSB 3.0) + 9W (NVME) = 28W
28W * 1,5 (Rush in Power Headroom) = 42W
I would consider a power supply of at least 40W necessary to guarantee stable operation even under specification conditions. It will also work with lower power, since the maximum power is not retrieved on average, but stable function is not guaranteed at all times.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Unfortunately the same problems arise with a Toshiba NVMe and they also showed using a Samsung NVMe (as per first post). As far as I know they are not having these problems. But I could be wrong.

I will experiment with an Armbian Image on the Kingston NVMe to see if that makes any difference.

usual user
Posts: 55
Joined: Sat Sep 10, 2022 10:47 pm
languages_spoken: english
Has thanked: 1 time
Been thanked: 17 times
Contact:

Re: NVME drives not working (although they should?)

Post by usual user »

Sjonnie wrote:
Sun Jan 22, 2023 9:53 pm
I will experiment with an Armbian Image on the Kingston NVMe to see if that makes any difference.
As this is a feature of the NVME, the used OS does not matter, except it disables APST by default.
If the other NVMEs also display this error message:
log.png
log.png (137.67 KiB) Viewed 421 times
there is also an APST issue, because the message means that the NVME does not successfully awake from a powersave mode.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Well, Armbian did not work out very well. Petitboot crashed on the image I wrote to the NVMe. Upon inspection I saw that the image had a 17 MB unallocated space at the beginning of the drive. Petitboot did not like that. I reflashed the NVMe with the Ubuntu 20.04 server image from Hardkernel and that at least allowed me to boot from the NVMe.

EDIT: At the time of the error the drive was in use. I had been installing packages and configuring them. I think the drive had not been "idle" for more that 5 or 10 minutes.

usual user
Posts: 55
Joined: Sat Sep 10, 2022 10:47 pm
languages_spoken: english
Has thanked: 1 time
Been thanked: 17 times
Contact:

Re: NVME drives not working (although they should?)

Post by usual user »

Sjonnie wrote:
Sun Jan 22, 2023 10:59 pm
I think the drive had not been "idle" for more that 5 or 10 minutes.
Deep powersave APST kicks in usually by default at round about 10 seconds disk idle time.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

OK, so how do I fix this? I have been trying to get the LINUX_KERNEL_CMDLINE option to work but I don't have grub. And I don't know how to get the nvme_core.default_ps_max_latency_us=0 to boot with.

I am clasping at straws here and it is not getting better :|

User avatar
mad_ady
Posts: 11208
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4 (HC1, HC2), C1+, C2, C4 (HC4), N1, N2, H2, Go, Go Advance, M1
Location: Bucharest, Romania
Has thanked: 647 times
Been thanked: 1059 times
Contact:

Re: NVME drives not working (although they should?)

Post by mad_ady »

If you're on Hardkernel's Ubuntu 20 image, you'll need to edit /media/boot/boot.ini (or /media/boot/config.ini) and append that option to bootargs variable.
After reboot you can check it was passed to the kernel by looking at cat /proc/cmdline

User avatar
tobetter
Posts: 11390
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 779 times
Been thanked: 1934 times
Contact:

Re: NVME drives not working (although they should?)

Post by tobetter »

Sjonnie wrote:
Sun Jan 22, 2023 11:24 pm
OK, so how do I fix this? I have been trying to get the LINUX_KERNEL_CMDLINE option to work but I don't have grub. And I don't know how to get the nvme_core.default_ps_max_latency_us=0 to boot with.

I am clasping at straws here and it is not getting better :|
Instructed here already, add it to the file /etc/default/flash-kernel and run update-bootscript.
viewtopic.php?p=364389#p364389

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Installed Ubuntu 20.04 from netboot and added the option to flash-kernel.

The output from cat /proc/cmdline is:

Code: Select all

quiet splash nvme_core.default_ps_max_latency_us=0 earlycon=uart8250,mmio32,0xfe660000 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x20000@0xe0000(enc),0x200000@0x100000(uboot),0x00000@0x300000(splash),0xc00000@0x400000(firmware) console=tty1
lspci: same as earlier posted

uname -a: same as earlier posted

EDIT: would the same commands work on 22.04 or Bullseye? I could try of course but installation takes some time.

User avatar
tobetter
Posts: 11390
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 779 times
Been thanked: 1934 times
Contact:

Re: NVME drives not working (although they should?)

Post by tobetter »

Sjonnie wrote:
Mon Jan 23, 2023 12:40 am
Installed Ubuntu 20.04 from netboot and added the option to flash-kernel.

The output from cat /proc/cmdline is:

Code: Select all

quiet splash nvme_core.default_ps_max_latency_us=0 earlycon=uart8250,mmio32,0xfe660000 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x20000@0xe0000(enc),0x200000@0x100000(uboot),0x00000@0x300000(splash),0xc00000@0x400000(firmware) console=tty1
lspci: same as earlier posted

uname -a: same as earlier posted

EDIT: would the same commands work on 22.04 or Bullseye? I could try of course but installation takes some time.
You can try but I doubt it helps if it's ASPT issue. There are multiple thread regarding to ASPT issue and they are saying to change the value of nvme_core.default_ps_max_latency_us to 0, 5000, 5500 or so.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Tried Bullseye which failed (no /etc/default/flash-kernel) and installed 22.04 (from netboot) which does have the flash-kernel file. Updated as per instruction.

Will install cockpit and some goodies (but no docker) and see if it stays stable for the coming hours.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Well... the first results are promising. I do however get a few errors in the Cockpit web interface:

Code: Select all

5:35 PM rk_gmac-dwmac fe2a0000.ethernet: no regulator found kernel 
5:35 PM arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active. kernel
5:35 PM arm-scmi firmware:scmi: Failed. SCMI protocol 19 not active. kernel
5:35 PM arm-scmi firmware:scmi: Failed. SCMI protocol 21 not active. kernel
5:35 PM arm-scmi firmware:scmi: Failed. SCMI protocol 22 not active. kernel
5:35 PM arm-scmi firmware:scmi: Failed. SCMI protocol 23 not active.
Something I should be worried about?

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

The M1 has not crashed the last 27 hours. So that's promising. Let's see what happens when I install Docker and Portainer. Once installed I will leave them run for another 24 hours and keep my fingers crossed ;)
These users thanked the author Sjonnie for the post:
mctom (Tue Jan 24, 2023 2:16 am)

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Installed docker and docker-compose and after an hour the Odroid crashed :(

This is what is in the logs (warning and above):

Image

Set the NVMe variable to 5000 to see if that makes a difference.

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

Update (and it's positive :) ): I set the value to 5000 and the M1 staid stable for another 24 hours. so I bit the bullet and installed Watchtower and Adguard Home as Docker containers on the M1.

Will let the M1 "stew" for another 24 hours to see if it remains stable. If so I think I can conclude that the nvme_core.default_ps_max_latency_us=5000 seems to work with the Kingston A2000.

Keep my fingers crossed :)
These users thanked the author Sjonnie for the post:
mctom (Wed Jan 25, 2023 3:42 am)

User avatar
Sjonnie
Posts: 41
Joined: Wed Oct 26, 2016 1:20 am
languages_spoken: english
ODROIDs: M1
Has thanked: 0
Been thanked: 5 times
Contact:

Re: NVME drives not working (although they should?)

Post by Sjonnie »

OK, so this will be my final update for this thread! If I (ever) run into other problems I will open a new thread (after I've searched the forum of course ;) )

The M1 has been running stable for the last 24 hours running Cockpit, Docker and a few containers (Adguard Home, Portainer, Watchtower, Sonarr, Jackett). I will continue to build the system to it's final configuration which includes containers for Domoticz, Dashticz, Mosquitto and Bitwarden Unified in full confidence. :mrgreen:

Thanks for your continued support in my quest for a stable system. Much appreciated!
These users thanked the author Sjonnie for the post:
odroid (Thu Jan 26, 2023 9:30 am)

Post Reply

Return to “Hardware and peripherals”

Who is online

Users browsing this forum: No registered users and 1 guest