Comment 12 for bug 1483343

------- Comment From <email address hidden> 2015-12-11 06:16 EDT-------
I have downloaded the mainline wily kernel as suggested and executed the scenario again.

root@powerkvmpok002:~/mainline# wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb
--2015-12-11 00:28:48-- http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb
Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216
Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56391678 (54M) [application/x-debian-package]
Saving to: ?linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb?

100%[===================================================================================================================>] 56,391,678 846KB/s in 66s

2015-12-11 00:29:54 (832 KB/s) - ?linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb? saved [56391678/56391678]

root@powerkvmpok002:~/mainline# dpkg -i linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb
Selecting previously unselected package linux-image-4.4.0-040400rc4-generic.
(Reading database ... 137006 files and directories currently installed.)
Preparing to unpack linux-image-4.4.0-040400rc4-generic_4.4.0-040400rc4.201512061930_ppc64el.deb ...
Done.
Unpacking linux-image-4.4.0-040400rc4-generic (4.4.0-040400rc4.201512061930) ...
Setting up linux-image-4.4.0-040400rc4-generic (4.4.0-040400rc4.201512061930) ...
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 4.4.0-040400rc4-generic /boot/vmlinux-4.4.0-040400rc4-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-040400rc4-generic /boot/vmlinux-4.4.0-040400rc4-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic
W: Possible missing firmware /lib/firmware/ql2700_fw.bin for module qla2xxx
W: Possible missing firmware /lib/firmware/ql8300_fw.bin for module qla2xxx
W: Possible missing firmware /lib/firmware/ql2600_fw.bin for module qla2xxx
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-040400rc4-generic /boot/vmlinux-4.4.0-040400rc4-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-040400rc4-generic /boot/vmlinux-4.4.0-040400rc4-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-39-generic
Found initrd image: /boot/initrd.img-3.19.0-39-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 4.4.0-040400rc4-generic #201512061930 SMP Mon Dec 7 01:14:51 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

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
lock_torture 1 TINFO : estimate time 6.00 min
lock_torture 1 TINFO : spin_lock: running 60 sec...
lock_torture 1 TPASS : spin_lock: completed
lock_torture 2 TINFO : spin_lock_irq: running 60 sec...
lock_torture 2 TPASS : spin_lock_irq: completed
lock_torture 3 TINFO : rw_lock: running 60 sec...
lock_torture 3 TPASS : rw_lock: completed
lock_torture 4 TINFO : rw_lock_irq: running 60 sec...

root@powerkvmpok002:~# [ 614.289969] NMI watchdog: BUG: soft lockup - CPU#150 stuck for 140s! [lock_torture_wr:4325]
[ 619.293972] NMI watchdog: BUG: soft lockup - CPU#23 stuck for 244s! [lock_torture_wr:4399]
[ 619.293987] NMI watchdog: BUG: soft lockup - CPU#98 stuck for 51s! [lock_torture_wr:4387]
[ 627.301973] NMI watchdog: BUG: soft lockup - CPU#39 stuck for 242s! [lock_torture_wr:4403]
[ 669.345931] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 669.346071] 1-...: (2 GPs behind) idle=02f/140000000000000/0 softirq=10477/10480 fqs=2908
[ 669.346162] 8-...: (0 ticks this GP) idle=58f/140000000000000/0 softirq=9878/9878 fqs=2908
[ 669.346290] 11-...: (0 ticks this GP) idle=e0f/140000000000000/0 softirq=10060/10060 fqs=2908
[ 669.346383] 12-...: (0 ticks this GP) idle=3dd/140000000000000/0 softirq=10024/10024 fqs=2908
[ 669.346470] 14-...: (1 GPs behind) idle=141/140000000000000/0 softirq=10118/10118 fqs=2908
[ 669.346560] 19-...: (1 GPs behind) idle=83d/140000000000000/0 softirq=10273/10273 fqs=2908
[ 669.346660] (detected by 104, t=84094 jiffies, g=3980, c=3979, q=7125)
[ 672.213960] NMI watchdog: BUG: soft lockup - CPU#116 stuck for 53s! [lock_torture_wr:4425]
[ 672.213980] NMI watchdog: BUG: soft lockup - CPU#32 stuck for 50s! [lock_torture_wr:4327]
[ 672.214347] rw_lock_irq-torture: Creating lock_torture_writer task
[ 718.977967] NMI watchdog: BUG: soft lockup - CPU#18 stuck for 144s! [lock_torture_wr:4321]
[ 718.977970] NMI watchdog: BUG: soft lockup - CPU#22 stuck for 323s! [lock_torture_wr:4407]
[ 732.409929] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 732.410024] 1-...: (2 GPs behind) idle=02f/140000000000000/0 softirq=10477/10480 fqs=2939
[ 732.410103] 8-...: (0 ticks this GP) idle=58f/140000000000000/0 softirq=9878/9878 fqs=2939
[ 732.410193] 11-...: (0 ticks this GP) idle=e0f/140000000000000/0 softirq=10060/10060 fqs=2939
[ 732.410282] 12-...: (0 ticks this GP) idle=3dd/140000000000000/0 softirq=10024/10024 fqs=2939
[ 732.410370] 14-...: (1 GPs behind) idle=141/140000000000000/0 softirq=10118/10118 fqs=2939
[ 732.410459] 19-...: (1 GPs behind) idle=83d/140000000000000/0 softirq=10273/10273 fqs=2939
[ 732.410546] (detected by 130, t=99860 jiffies, g=3980, c=3979, q=7361)
[ 732.410808] rcu_sched kthread starved for 15047 jiffies! g3980 c3979 f0x0 s3 ->state=0x1
[ 756.157974] NMI watchdog: BUG: soft lockup - CPU#33 stuck for 78s! [lock_torture_wr:4343]
[ 756.159342] rw_lock_irq-torture: lock_torture_writer task started

The problem still occurs with the mainline wily kernel as can be seen above.