root@powerkvmpok002:~/6690705# dpkg -i linux-image-3.18.0-8-generic_3.18.0-8.9_ppc64el.deb
Selecting previously unselected package linux-image-3.18.0-8-generic.
(Reading database ... 164194 files and directories currently installed.)
Preparing to unpack linux-image-3.18.0-8-generic_3.18.0-8.9_ppc64el.deb ...
Done.
Unpacking linux-image-3.18.0-8-generic (3.18.0-8.9) ...
Setting up linux-image-3.18.0-8-generic (3.18.0-8.9) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-8-generic /boot/vmlinux-3.18.0-8-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-8-generic /boot/vmlinux-3.18.0-8-generic
update-initramfs: Generating /boot/initrd.img-3.18.0-8-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.18.0-8-generic /boot/vmlinux-3.18.0-8-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-8-generic /boot/vmlinux-3.18.0-8-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.4.0-040400rc4-generic
Found initrd image: /boot/initrd.img-4.4.0-040400rc4-generic
Found linux image: /boot/vmlinux-3.19.0-41-generic
Found initrd image: /boot/initrd.img-3.19.0-41-generic
Found linux image: /boot/vmlinux-3.19.0-39-generic
Found initrd image: /boot/initrd.img-3.19.0-39-generic
Found linux image: /boot/vmlinux-3.18.0-8-generic
Found initrd image: /boot/initrd.img-3.18.0-8-generic
Found linux image: /boot/vmlinux-3.13.0-10-generic
Found initrd image: /boot/initrd.img-3.13.0-10-generic
Found Debian GNU/Linux (8.2) on /dev/sdb2
Found unknown Linux distribution on /dev/mapper/ibmpkvm_vg_root01-ibmpkvm_lv_system
done
root@powerkvmpok002:~# uname -a
Linux powerkvmpok002 3.18.0-8-generic #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
Then executed the lock_torture tests again on the 3.18 Vivid kernel.
root@powerkvmpok002:~# cd /opt/ltp/testcases/bin/
root@powerkvmpok002:/opt/ltp/testcases/bin# ./lock_torture.sh
./lock_torture.sh: 55: ./lock_torture.sh: tst_kvercmp: not found
[ 148.177770] NMI watchdog: BUG: soft lockup - CPU#100 stuck for 23s! [lock_torture_wr:2994]
[ 148.177773] NMI watchdog: BUG: soft lockup - CPU#101 stuck for 23s! [lock_torture_wr:2986]
[ 148.177775] NMI watchdog: BUG: soft lockup - CPU#99 stuck for 23s! [lock_torture_wr:2960]
[ 148.177780] NMI watchdog: BUG: soft lockup - CPU#102 stuck for 23s! [lock_torture_wr:2999]
[ 148.177783] NMI watchdog: BUG: soft lockup - CPU#103 stuck for 23s! [lock_torture_wr:2995]
[ 148.181769] NMI watchdog: BUG: soft lockup - CPU#104 stuck for 23s! [lock_torture_wr:2987]
[ 148.185771] NMI watchdog: BUG: soft lockup - CPU#107 stuck for 23s! [lock_torture_wr:2990]
[ 148.185774] NMI watchdog: BUG: soft lockup - CPU#106 stuck for 23s! [lock_torture_wr:2992]
[ 148.189769] NMI watchdog: BUG: soft lockup - CPU#108 stuck for 23s! [lock_torture_wr:2984]
[ 148.189773] NMI watchdog: BUG: soft lockup - CPU#110 stuck for 23s! [lock_torture_wr:2983]
[ 148.189775] NMI watchdog: BUG: soft lockup - CPU#109 stuck for 23s! [lock_torture_wr:2989]
[ 148.189787] NMI watchdog: BUG: soft lockup - CPU#111 stuck for 23s! [lock_torture_wr:2988]
[ 148.193770] NMI watchdog: BUG: soft lockup - CPU#113 stuck for 23s! [lock_torture_wr:3023]
[ 148.193773] NMI watchdog: BUG: soft lockup - CPU#112 stuck for 23s! [lock_torture_wr:3000]
[ 148.197768] NMI watchdog: BUG: soft lockup - CPU#115 stuck for 23s! [lock_torture_wr:3017]
[ 204.521765] INFO: rcu_sched self-detected stall on CPU
[ 204.521768] INFO: rcu_sched self-detected stall on CPU
[ 204.521780] INFO: rcu_sched self-detected stall on CPU { 71}
[ 204.521793] INFO: rcu_sched self-detected stall on CPU { 39}
[ 204.521794] INFO: rcu_sched self-detected stall on CPU
[ 204.521794] INFO: rcu_sched self-detected stall on CPU
The above messages are displayed immediately on the console once the tests are started.
------- Comment From <email address hidden> 2016-01-11 01:01 EDT------- /launchpad. net/ubuntu/ +source/ linux/3. 18.0-8. 9/+build/ 6690705
I have installed 3.18 kernel provided in the link:
https:/
root@powerkvmpo k002:~/ 6690705# dpkg -i linux-image- 3.18.0- 8-generic_ 3.18.0- 8.9_ppc64el. deb 3.18.0- 8-generic. 3.18.0- 8-generic_ 3.18.0- 8.9_ppc64el. deb ... 3.18.0- 8-generic (3.18.0-8.9) ... 3.18.0- 8-generic (3.18.0-8.9) ... postinst. d. postinst. d/apt-auto- removal 3.18.0-8-generic /boot/vmlinux- 3.18.0- 8-generic postinst. d/initramfs- tools 3.18.0-8-generic /boot/vmlinux- 3.18.0- 8-generic img-3.18. 0-8-generic postinst. d/update- notifier 3.18.0-8-generic /boot/vmlinux- 3.18.0- 8-generic postinst. d/zz-update- grub 3.18.0-8-generic /boot/vmlinux- 3.18.0- 8-generic 4.4.0-040400rc4 -generic img-4.4. 0-040400rc4- generic 3.19.0- 41-generic img-3.19. 0-41-generic 3.19.0- 39-generic img-3.19. 0-39-generic 3.18.0- 8-generic img-3.18. 0-8-generic 3.13.0- 10-generic img-3.13. 0-10-generic ibmpkvm_ vg_root01- ibmpkvm_ lv_system
Selecting previously unselected package linux-image-
(Reading database ... 164194 files and directories currently installed.)
Preparing to unpack linux-image-
Done.
Unpacking linux-image-
Setting up linux-image-
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
update-initramfs: Generating /boot/initrd.
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
Generating grub configuration file ...
Found linux image: /boot/vmlinux-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinux-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinux-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinux-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinux-
Found initrd image: /boot/initrd.
Found Debian GNU/Linux (8.2) on /dev/sdb2
Found unknown Linux distribution on /dev/mapper/
done
root@powerkvmpo k002:~# uname -a
Linux powerkvmpok002 3.18.0-8-generic #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
Then executed the lock_torture tests again on the 3.18 Vivid kernel.
root@powerkvmpo k002:~# cd /opt/ltp/ testcases/ bin/ k002:/opt/ ltp/testcases/ bin# ./lock_torture.sh
root@powerkvmpo
./lock_torture.sh: 55: ./lock_torture.sh: tst_kvercmp: not found
[ 148.177770] NMI watchdog: BUG: soft lockup - CPU#100 stuck for 23s! [lock_torture_ wr:2994] wr:2986] wr:2960] wr:2999] wr:2995] wr:2987] wr:2990] wr:2992] wr:2984] wr:2983] wr:2989] wr:2988] wr:3023] wr:3000] wr:3017]
[ 148.177773] NMI watchdog: BUG: soft lockup - CPU#101 stuck for 23s! [lock_torture_
[ 148.177775] NMI watchdog: BUG: soft lockup - CPU#99 stuck for 23s! [lock_torture_
[ 148.177780] NMI watchdog: BUG: soft lockup - CPU#102 stuck for 23s! [lock_torture_
[ 148.177783] NMI watchdog: BUG: soft lockup - CPU#103 stuck for 23s! [lock_torture_
[ 148.181769] NMI watchdog: BUG: soft lockup - CPU#104 stuck for 23s! [lock_torture_
[ 148.185771] NMI watchdog: BUG: soft lockup - CPU#107 stuck for 23s! [lock_torture_
[ 148.185774] NMI watchdog: BUG: soft lockup - CPU#106 stuck for 23s! [lock_torture_
[ 148.189769] NMI watchdog: BUG: soft lockup - CPU#108 stuck for 23s! [lock_torture_
[ 148.189773] NMI watchdog: BUG: soft lockup - CPU#110 stuck for 23s! [lock_torture_
[ 148.189775] NMI watchdog: BUG: soft lockup - CPU#109 stuck for 23s! [lock_torture_
[ 148.189787] NMI watchdog: BUG: soft lockup - CPU#111 stuck for 23s! [lock_torture_
[ 148.193770] NMI watchdog: BUG: soft lockup - CPU#113 stuck for 23s! [lock_torture_
[ 148.193773] NMI watchdog: BUG: soft lockup - CPU#112 stuck for 23s! [lock_torture_
[ 148.197768] NMI watchdog: BUG: soft lockup - CPU#115 stuck for 23s! [lock_torture_
[ 204.521765] INFO: rcu_sched self-detected stall on CPU
[ 204.521768] INFO: rcu_sched self-detected stall on CPU
[ 204.521780] INFO: rcu_sched self-detected stall on CPU { 71}
[ 204.521793] INFO: rcu_sched self-detected stall on CPU { 39}
[ 204.521794] INFO: rcu_sched self-detected stall on CPU
[ 204.521794] INFO: rcu_sched self-detected stall on CPU
The above messages are displayed immediately on the console once the tests are started.