![]() Please try 'cgroup_disable=memory' option if you don't want memory cgroups Inode-cache hash table entries: 32768 (order: 2, 131072 bytes) PID hash table entries: 2048 (order: -2, 8192 bytes)ĭentry cache hash table entries: 65536 (order: 3, 262144 bytes) ![]() Kernel command line: root=/dev/ram console=ttyS0,115200 PERCPU: Embedded 1 pages/cpu s8320 r8192 d16256 u32768īuilt 1 zonelists in Zone order, mobility grouping on. Memory policy: ECC disabled, Data cache writealloc Machine: Marvell Armada 380/381/382/385/388 (Device Tree), model: Marvell Armada 385 Development Board Marvell GCC Dev 201310-2126.3d181f66 64K MAXPAGESIZE ALIGN) ) #1 SMP Fri Apr 29 10:03: 2014T30p5 Build-git11369fbĬPU: ARMv7 Processor revision 1 (ARMv7), cr=10c53c7dĬPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Image Type: ARM Linux RAMDisk Image (gzip compressed) # Loading init Ramdisk from Legacy Image at 00f00000. Image Type: ARM Linux Kernel Image (uncompressed) # Booting kernel from Legacy Image at 00a00000. NAND read: device 0 offset 0xa00000, size 0x500000 UBIFS: reserved for root: 200807 bytes (196 KiB) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: journal size: 1015809 bytes (992 KiB, 0 MiB, 6 LEBs) ![]() UBIFS: file system size: 4063232 bytes (3968 KiB, 3 MiB, 32 LEBs) UBIFS: mounted UBI device 0, volume 0, name "reserve2" UBI: number of PEBs reserved for bad PEB handling: 2 UBI: VID header offset: 2048 (aligned 2048) UBI: logical eraseblock size: 126976 bytes UBI: physical eraseblock size: 131072 bytes (128 KiB) U-Boot 2013.01_v1.04 (11:11:05) Marvell version: 2014_T3.0p6ĭDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled ![]() MvSysEnvGetTopologyUpdateInfo: TWSI Read failedĭDR3 Training Sequence - Switching XBAR Window to FastPath WindowĭDR3 Training Sequence - Ended SuccessfullyīootROM: Image checksum verification PASSED Are you ready to get started? This is the MCM Gen2. I now have some legible output when I boot (this log without drives connected). ![]() Solved my problems regarding data corruption. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |