Fixed
Created: Nov 23, 2015
Updated: Dec 3, 2018
Resolved Date: Dec 6, 2015
Found In Version: 6.0.0.17
Fix Version: 6.0.0.27
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Kernel
In order to investigate some RCU issues we enabled the RCU debug options, however a conflict seems top exist when lttng2 is also enabled meaning we can't use the tool together with the additional debug.
Don't include lttng2 in the build.
$ configure --enable-board=intel-x86-64 \
--enable-rootfs=glibc_std --enable-kernel=preempt_rt \
--with-template=feature/lttng2 \
--enable-jobs=1 --enable-parallel-pkgbuilds=4 \
--enable-rm-work=yes --enable-rm-oldimgs=yes \
--enable-checkout-all-layers=yes --enable-reconfig \
--enable-ccache=yes --with-ccache-dir=/path/to/ccachedir \
--with-sstate-dir=/path/to/sstatedir --with-rcpl-version=0017
$ make -C build linux-windriver.menuconfig
Enable the following options:
Symbol: SPARSE_RCU_POINTER [=n] ¦
¦ Type : boolean ¦
¦ Prompt: RCU debugging: sparse-based checks for pointer usage ¦
¦ Location: ¦
¦ -> Kernel hacking ¦
¦ (8) -> RCU Debugging
Symbol: RCU_CPU_STALL_VERBOSE [=y] ¦
¦ Type : boolean ¦
¦ Prompt: Print additional per-task information for RCU_CPU_STALL_DETECTO ¦
¦ Location: ¦
¦ -> Kernel hacking ¦
¦ (9) -> RCU Debugging
Symbol: RCU_CPU_STALL_INFO [=n] ¦
¦ Type : boolean ¦
¦ Prompt: Print additional diagnostics on RCU CPU stall ¦
¦ Location: ¦
¦ -> Kernel hacking ¦
¦ (4) -> RCU Debugging
Symbol: RCU_TRACE [=n] ¦
¦ Type : boolean ¦
¦ Prompt: Enable tracing for RCU ¦
¦ Location: ¦
¦ -> Kernel hacking ¦
¦ (4) -> RCU Debugging
$ make -C build linux-windriver
Error:
See attached rcu-trace-error.txt
