Fixed
Created: May 6, 2014
Updated: Dec 3, 2018
Resolved Date: May 18, 2014
Previous ID: LIN5-18716
Found In Version: 6.0
Fix Version: 6.0.0.7
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Kernel
When booting IDP project , call trace is showed
Call trace info (see the full log in attachment).
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.4.43-grsec-WR5.0.1.13_standard #2
[ 0.000000] Call Trace:
[ 0.000000] [<c15835e9>] spin_dump+0x97/0x9f
[ 0.000000] [<c158360c>] spin_bug+0x1b/0x1f
[ 0.000000] [<c12d74f0>] do_raw_spin_lock+0xf0/0x120
[ 0.000000] [<c1589679>] _raw_spin_lock+0x49/0x50
[ 0.000000] [<c10770cc>] ? init_dl_bw+0x2c/0xa0
[ 0.000000] [<c10770cc>] init_dl_bw+0x2c/0xa0
[ 0.000000] [<c184d545>] ? sched_init+0x1d/0x4a6
[ 0.000000] [<c1062eff>] init_rootdomain+0x1f/0x50
[ 0.000000] [<c184d572>] sched_init+0x4a/0x4a6
[ 0.000000] [<c12d73d2>] ? __raw_spin_lock_init+0x32/0x60
[ 0.000000] [<c1853276>] ? vmalloc_init+0x45/0xbc
[ 0.000000] [<c18395be>] start_kernel+0x192/0x349
[ 0.000000] [<c1839269>] ? repair_env_string+0x51/0x51
[ 0.000000] [<c1839098>] i386_start_kernel+0x98/0x9f
[ 0.000000] Hierarchical RCU implementation.
IDP boot successfuly and the call trace does not affect KTS&BTS test
(1) Config command:
/net/pek-idptest1/buildarea2/idp-dvds/lx05a.12sp-50113_id05.14sp-201-xt/wrlinux-5/wrlinux/configure --enable-board=intel-quark --enable-kernel=standard --enable-rootfs=glibc-idp --enable-addons=wr-idp --enable-jobs=4 --enable-parallel-pkgbuilds=4 --with-layer=wr-intel-support,/buildarea1/GIT/wr-testing/bts,/buildarea1/GIT/wr-testing/kts --with-template=feature/intel-wilkinpeak2 --enable-checkout-all-layers=yes --with-rcpl-version=0013
(2) Deploy command:
sudo ./deploy.sh -f export/intel-quark-glibc-idp-standard-dist-srm.tar.bz2 -d /dev/sdc -D /dev/mmcblk0p2 -b galileo -u
[sudo] password for mdong:
===========================================================
Deploy rootfs and kernel image
===========================================================
INFO: Need to format device firstly. (VFAT + EXT3)
INFO: Clear partition table in "/dev/sdc"
INFO: Creating vfat+ext3 primary partitions in /dev/sdc ...
INFO: Try umount /dev/sdc and create partition again ...
INFO: Unmounting /dev/sdc ...
INFO: Current partition: /dev/sdc1 /dev/sdc2
INFO: Formatting "/dev/sdc1" to vfat ...
INFO: Formatting "/dev/sdc2" to ext3 ...
INFO: Need to mount device node firstly.
INFO: Mounting /dev/sdc2 /tmp/deploy-image-DLBkSMLk/tmp.T4iJioUb9Q ...
INFO: Remove all files in "/tmp/deploy-image-DLBkSMLk/tmp.T4iJioUb9Q"
INFO: Extract rootfs ...
...........................................................................
INFO: Need to mount vfat partition firstly ...
INFO: Mounting /dev/sdc1 /tmp/uefi-partition-YUJErPZy ...
INFO: Deploy UEFI files ...
INFO: Using UEFI grub conf: /tmp/deploy-image-DLBkSMLk/tmp.T4iJioUb9Q/boot/grub/grub-recovery.conf
INFO: Initialize board with extra settings ...
INFO: Unmount all temporary mount point if exist.
INFO: Unmounting /tmp/deploy-image-DLBkSMLk/tmp.T4iJioUb9Q ...
INFO: Unmounting /tmp/uefi-partition-YUJErPZy ...
INFO: Remove all temporary files.
INFO: DONE!
3) boot the target on Galileo
4) dmesg | grep Call_trace
