Home > OS >  Ok6410 linux4.4.217 kernel loading errors
Ok6410 linux4.4.217 kernel loading errors

Time:11-22


[2.145745] hctosys: unable to open RTC device (rtc0)
S3c64xx_serial_startup: port=c0b16e88 (7 f005000 f7005000)
S3c64xx_serial_startup ok
Udivslot=0080 (div 1)
Config: 8 bits/char
Setting ulcon to 00000003, brddiv to 35, udivslot 00000080
Uart: ulcon=0 x00000003, ucon=0 x0000fb85, ufcon=0 x00000031
Md: [14.235454] Waiting for all devices to be available before autodetect
[14.236708] md: If you don 't use raid, use raid=noautodetect
Md: [14.245090] Autodetecting RAID arrays.
Md: [14.246343] Scanned 0 and added 0 devices.
Md: [14.250854] autorun...
Md: [14.253601]... Autorun DONE.



[109.278614] VFS: Unable to mount the root fs via NFS, trying floppy.
[109.280134] VFS: always open a root device "NFS or unknown - block (2, 0) : error - 6
[109.286298] both Please append a correct "root=" boot option. Here are the available partitions:
[109.294620], 0100, 65536 ram0 (driver?
[109.299151], 0101, 65536 ram1 (driver?
[109.303748], 0102, 65536 ram2 (driver?
[109.308396], 0103, 65536 ram3 (driver?
[109.312998], 0104, 65536 ram4 (driver?
[109.317542], 0105, 65536 ram5 (driver?
[109.322141], 0106, 65536 ram6 (driver?
[109.326740], 0107, 65536 ram7 (driver?
[109.331338], 0108, 65536 ram8 (driver?
[109.335936], 0109, 65536 ram9 (driver?
[109.340583] 010 a 65536 ram10 (driver)?
[109.345277] 010 b 65536 ram11 (driver)?
[109.349906] 010 c 65536 ram12 (driver)?
[109.354592] 010 d 65536 ram13 (driver)?
[109.359277] 010 e 65536 ram14 (driver)?
[109.363962] 010 f 65536 ram15 (driver)?
[109.368703] Kernel panic - not syncing: VFS: Unable to mount the root fs on unknown - block (2, 0)
[109.376885] : CPU 0 PID: 1 Comm: swapper Not tainted 4.4.217 # 0
[109.382684] Hardware name: OK6410
[109.386040] [& lt; c00123b0 & gt;] (unwind_backtrace) from [& lt; c000e848 & gt;] (show_stack + 0 x20/0 x24)
[109.393744] [& lt; c000e848 & gt;] (show_stack) from [& lt; c036fc78 & gt;] (dump_stack + 0 x20/0 x28)
[109.400939] [& lt; c036fc78 & gt;] (dump_stack) from [& lt; c00f84e0 & gt;] (panic + 0 x88/0 x214)
[109.407788] [& lt; c00f84e0 & gt;] (panic) from [& lt; c0a2b3ac & gt;] (mount_block_root + 0 x194/0 x264)
[109.415240] [& lt; c0a2b3ac & gt;] (mount_block_root) from [& lt; c0a2b69c & gt;] (mount_root + 0 x100/0 x12c)
[109.423135] [& lt; c0a2b69c & gt;] (mount_root) from [& lt; c0a2b834 & gt;] (prepare_namespace + 0 x16c/0 x1d0)
[109.431117] [& lt; c0a2b834 & gt;] (prepare_namespace) from [& lt; c0a2af48 & gt;] (kernel_init_freeable + 0 x1cc/0 x21c)
[109.439988] [& lt; c0a2af48 & gt;] (kernel_init_freeable) from [& lt; c06f5374 & gt;] (kernel_init + 0 x18/0 xf8)
[109.448134] [& lt; c06f5374 & gt;] (kernel_init) from [& lt; c000a650 & gt;] (ret_from_fork + 0 x14/0 x24)
[109.455677] - [end Kernel panic - not syncing: VFS: Unable to mount the root fs on unknown - block (2, 0)
[124.012333] random: from the pool is initialized

CodePudding user response:

Uboot launch parameters is wrong, or the file system format is wrong

CodePudding user response:

How do you set the uboot launch parameters? The file system with infineon official
  • Related