Fixed
Created: Jun 8, 2015
Updated: Sep 8, 2018
Resolved Date: Jul 21, 2015
Found In Version: 7.0.0.6
Fix Version: 7.0.0.8
Severity: Standard
Applicable for: Wind River Linux 7
Component/s: unknown
No build or log-in issue, but the target will hang with NFS rootfs issue:
[ OK ] Reached target Login Prompts.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Started Postfix Mail Transport Agent.
[ OK ] Reached target Multi-User System.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.
Wind River Linux 7.0.0.6 SDP_Wildcat_Pass-1 ttyS0
SDP_Wildcat_Pass-1 login:
systemd[1]: Got notification message for unit systemd-timesyncd.service
systemd[1]: systemd-timesyncd.service: Got notification message from PID 522 (STATUS=Idle....)
systemd[1]: systemd-timesyncd.service: got STATUS=Idle.
systemd[1]: Got notification message for unit systemd-logind.service
systemd[1]: systemd-logind.service: Got notification message from PID 602 (WATCHDOG=1...)
systemd[1]: systemd-logind.service: got WATCHDOG=1
systemd[1]: Got notification message for unit systemd-logind.service
systemd[1]: systemd-logind.service: Got notification message from PID 602 (WATCHDOG=1...)
systemd[1]: systemd-logind.service: got WATCHDOG=1
nfs: server 128.224.165.20 not responding, still trying
nfs: server 128.224.165.20 not responding, still trying
systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
1, configure
.../WRL70RCPL/RCPL0006_LX13/wrlinux-7/wrlinux/configure --enable-board=intel-x86-64 --enable-kernel=standard --enable-rootfs=glibc-std --with-template=feature/self-hosted --with-sstate-dir=sstate-dir
2, make fs
3, boot target with NFS rootfs (The default boot method of LVM mananged board)
The issue is encountered on intel Wildcat_Pass (barcode: 20369) target, not sure whether it is reproduced on other boards.
