NFS does not connect LS1046ARDB LSDK 1909

itzik_sherf — Tue, 12 May 2020 16:26:21 GMT

Trying to enable a boot from NFS process.

Standard Yocto build based on instructions, full network image.
The LS1046ARDB board is in its initial state, no changes in QFLASH or in U-boot configuration.
Booting the kernel from a boot partition on /dev/sda1 (SSD drive).
The bootargs are: ttyS0,115200 root=/dev/nfs nfsroot=10.0.0.15:/var/nfsshare rw ip=dhcp
The boot script is: bootnfs=scsi reset; ext4load scsi 0:1 a0000000 /boot/fitImage.bin; bootm a0000000:kernel@1 - a0000000:fdt@freescale_fsl-ls1046a-rdb-sdk.dtb
The NFS server works good, tried on CentOS and Ubuntu servers, fully accessible.
DHCP request succeeds, and it shows the right "rootserver":
Sending DHCP requests ..
[ 9.123360] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 10.738900] ., OK
[ 10.764834] IP-Config: Got DHCP answer from 10.0.0.138, my address is 10.0.0.7
[ 10.772062] IP-Config: Complete:
[ 10.775288] device=eth2, hwaddr=00:04:9f:06:50:be, ipaddr=10.0.0.7, mask=255.255.255.0, gw=10.0.0.138
[ 10.784941] host=10.0.0.7, domain=Home, nis-domain=(none)
[ 10.790776] bootserver=0.0.0.0, rootserver=10.0.0.15, rootpath=
[ 10.790778] nameserver0=10.0.0.138
After it is stuck for a while, it fails on Kernel panic:
[ 208.354955] VFS: Unable to mount root fs via NFS, trying floppy.
[ 208.361229] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
[ 208.368464] Please append a correct "root=" boot option; here are the available partitions:
[ 208.376821] 0100 4096 ram0
[ 208.376822] (driver?)
...
[ 208.462581] (driver?)
[ 208.468765] 010f 4096 ram15
[ 208.468766] (driver?)
[ 208.474961] 1f00 524288 mtdblock0
[ 208.474962] (driver?)
[ 208.481492] 1f01 65536 mtdblock1
[ 208.481493] (driver?)
[ 208.488031] 1f02 65536 mtdblock2
[ 208.488032] (driver?)
[ 208.494562] 0800 117220824 sda
[ 208.494563] driver: sd
[ 208.500667] 0801 5242880 sda1 9fb1f8e1-01
[ 208.500668]
[ 208.507034] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[ 208.515295] CPU: 2 PID: 1 Comm: swapper/0 Tainted: G W 5.4.3+gf811858 #1
[ 208.523294] Hardware name: LS1046A RDB Board (DT)
[ 208.527990] Call trace:
[ 208.530432] dump_backtrace+0x0/0x140
[ 208.534087] show_stack+0x14/0x20
[ 208.537395] dump_stack+0xb4/0xf8
[ 208.540703] panic+0x158/0x324
[ 208.543750] mount_block_root+0x1d0/0x284
[ 208.547752] mount_root+0x124/0x158
[ 208.551232] prepare_namespace+0x15c/0x1c0
[ 208.555321] kernel_init_freeable+0x210/0x22c
[ 208.559671] kernel_init+0x10/0x100
[ 208.563152] ret_from_fork+0x10/0x18
[ 208.566721] SMP: stopping secondary CPUs
[ 208.570643] Kernel Offset: 0x2b9897c00000 from 0xffff800010000000
[ 208.576728] PHYS_OFFSET: 0xffffbf0c80000000
[ 208.580904] CPU features: 0x0002,20806000
[ 208.584904] Memory Limit: none
[ 208.587953] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) ]---
Tested with static IP as well, no difference.
Tried using the old NFSwatch tool on the Ubuntu NFS server, it shows no attempts of connection. It does show manual test connections.

As a side note, there are some worrying issues in the kernel log before the DHCP process:

[ 4.007485] ------------[ cut here ]------------
[ 4.012107] Your devicetree is out of date, please update it. The AQR107 family doesn't support XGMII, maybe you mean USXGMII.
[ 4.023535] WARNING: CPU: 2 PID: 1 at drivers/net/phy/aquantia_main.c:595 aqr107_config_init+0x94/0xa8
[ 4.032836] Modules linked in:
[ 4.035885] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.3+gf811858 #1
[ 4.042492] Hardware name: LS1046A RDB Board (DT)
[ 4.047190] pstate: 60000005 (nZCv daif -PAN -UAO)
[ 4.051974] pc : aqr107_config_init+0x94/0xa8
[ 4.056324] lr : aqr107_config_init+0x94/0xa8
[ 4.060672] sp : ffff80001003ba10
[ 4.063978] x29: ffff80001003ba10 x28: ffff0009710b6000
[ 4.069284] x27: ffffab98a95c4000 x26: 0000000000001002
[ 4.074589] x25: ffff000971608800 x24: 0000000000000000
[ 4.079894] x23: 0000000000000000 x22: 000000000000000e
[ 4.085198] x21: ffff0009710b6000 x20: ffff0009710b64c0
[ 4.090503] x19: ffff000971608000 x18: 0000000000000010
[ 4.095808] x17: 0000000080cd1967 x16: 00000000b2afac86
[ 4.101113] x15: ffff000972475258 x14: 0720072007200720
[ 4.106418] x13: 0720072007200720 x12: 0000000000000001
[ 4.111723] x11: 0000000000000000 x10: 00000000000009a0
[ 4.117028] x9 : ffff80001003b750 x8 : ffff000972475800
[ 4.122333] x7 : ffff000972474f80 x6 : ffff0009739db900
[ 4.127638] x5 : 0000000000000000 x4 : 00000000000018b0
[ 4.132943] x3 : ffff5470ca174000 x2 : ffffab98a9cc3620
[ 4.138248] x1 : a7a7fcee37f9d100 x0 : 0000000000000000
[ 4.143552] Call trace:
[ 4.145991] aqr107_config_init+0x94/0xa8
[ 4.149993] phy_init_hw+0x54/0x70
[ 4.153387] phy_attach_direct+0xec/0x2a8
[ 4.157388] phy_connect_direct+0x24/0x78
[ 4.161391] of_phy_connect+0x4c/0x90
[ 4.165047] memac_init_phy+0x9c/0x138
[ 4.168789] dpa_start+0x2c/0x12c
[ 4.172096] dpa_eth_priv_start+0xb4/0xf4
[ 4.176099] __dev_open+0xc0/0x170
[ 4.179493] __dev_change_flags+0x160/0x1b8
[ 4.183669] dev_change_flags+0x20/0x60
[ 4.187498] ip_auto_config+0x264/0xe64
[ 4.191328] do_one_initcall+0x50/0x190
[ 4.195157] kernel_init_freeable+0x194/0x22c
[ 4.199508] kernel_init+0x10/0x100
[ 4.202988] ret_from_fork+0x10/0x18
[ 4.206555] ---[ end trace f7f7161a46513eb8 ]---

Can anyone help please?

Re: NFS does not connect LS1046ARDB LSDK 1909

Pavel — Wed, 13 May 2020 07:26:01 GMT

Perhaps CentOS and Ubuntu servers try to go to power save mode and it produces loosing of NFS connection.

Have a great day,
Pavel Chubakov

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

topic Re: NFS does not connect LS1046ARDB LSDK 1909 in Layerscape

NFS does not connect LS1046ARDB LSDK 1909

Re: NFS does not connect LS1046ARDB LSDK 1909