Fixed
Created: Nov 30, 2015
Updated: Dec 3, 2018
Resolved Date: Dec 16, 2015
Found In Version: 8.0
Fix Version: 8.0.0.1
Severity: Standard
Applicable for: Wind River Linux 8
Component/s: Kernel
o Check the CQ, Is there a duplicate?
No
1. Priority
****************************
2
2. Severity
****************************
Standard
3. Repeatability :
****************************
reproducible
4. Summary:
****************************
5. Faulty Part:
****************************
Kernel
6. Engineering Details (Not Published):
****************************
Environment
======================
Requirement No.: US66801
WRLinux Version: WRLinux8.0 S10
Workbench Version: N/A
Binary/FS From: N/A
BSP/Configuration: fsl-ls20xx-standard-glibc-std HOST OS: RHEL 6.7
7. Symptom Details
****************************
Problem Description
======================
root@ls2085a_rdb-3:~# criu check
Error (cr-check.The pagemap bits 55-60 has changed their meaning! See the linux/Documentation/vm/pagemap.txt for details.
c:602): Kernel dBits 55-60 of /proc/PID/pagemap entries are about to stop being page-shift some time soon. See the linux/Documentation/vm/pagemap.txt for details.
oesn't support PTRACE_O_SUSPEND_SECCOMP
Warn (cr-check.c:619): Dirty tracking is OFF. Memory snapshot will not work.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Logs
======================
http://pek-rth-vm1.wrs.com/publiclog/WASSP_LOG/pek-lpgtest15.wrs.com/WRL8_regression/log_dir/kernel/fsl-ls20xx/S10/LB10/week3/fsl_ls2085a_rdb_standard_glibc_std_WR_systemd_kts/criu/fsl-ls20xx_platform/fsl_ls2085a_rdb.standard.true.glibcstd.lpgbuildcdcWASSP_LINUX_80testcaseswrlinuxutilsfrags/target_22441.platform_B1E1R0_20151130_023609.log
http://pek-rth-vm1.wrs.com/publiclog/WASSP_LOG/pek-lpgtest14.wrs.com/WRL8_regression/log_dir/kernel/xilinx-zynq/S10/LB10/week3/ZYNQ_ZC702_standard_glibc_std_WR_systemd_kts/criu/xilinx-zynq_platform/ZYNQZC702.standard.true.glibcstd.lpgbuildcdcWASSP_LINUX_80testcaseswrlinuxutilsfrags/target_19900.platform_B1E2R0_20151130_143219.log
Expected Behavior
======================
Run "criu check" pass without issue found
8. Steps To Reproduce
****************************
configure --enable-board=fsl-ls20xx --enable-kernel=standard --enable-rootfs=glibc-std --with-layer=wr-testing/kts, wr-testing/ltp --with-template=feature/kts-standard --enable-test=yes --enable-internet-download=yes
make fs
Load image to the target (barcode: 22441) and boot it up
To run the command of "criu check" on the target
9. Workaround
****************************
N/A
10. Failure Scenarios Checking
****************************
(1) Is this defect found by the existing test cases?
Yes
(2) If not, check further this defect is one single failure, or one instance of common failure scenarios?
*If it is just one single failure, no new test cases for it, the subsequent fix verification is fine;
*if it is one instance of common failure scenarios, add / update test cases to cover such failure scenarios;
Enable CONFIG_SECCOMP manually if some enhancement functionality of CRIU is needed.
configure --enable-board=fsl-ls20xx --enable-kernel=standard --enable-rootfs=glibc-std --with-layer=wr-testing/kts, wr-testing/ltp --with-template=feature/kts-standard --enable-test=yes --enable-internet-download=yes
make fs
Load image to the target (barcode: 22441) and boot it up
To run the command of "criu check" on the target
