[Bug 1483343] Comment bridged from LTC Bugzilla

2017-02-06 Thread bugproxy
--- Comment From boqun.f...@cn.ibm.com 2017-02-06 03:07 EDT--- (In reply to comment #71) > Hi, > > Ran runltp on 17.04, and ended up with continuous call traces on console. > > ---uname output--- > Linux ltc-garri1 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC > 2017 ppc64le

[Bug 1483343] Comment bridged from LTC Bugzilla

2017-02-05 Thread bugproxy
--- Comment From poojabsu...@in.ibm.com 2017-02-06 01:36 EDT--- Hi, Ran runltp on 17.04, and ended up with continuous call traces on console. ---uname output--- Linux ltc-garri1 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ---Call

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-10-05 Thread bugproxy
--- Comment From ckuma...@in.ibm.com 2016-10-06 01:24 EDT--- Externalizing comment 61 and 62 - The Same test is causing problem in ubuntu kernel version 4.8.0-17-generic. Got below call traces: [48755.933755] 112-...: (2 ticks this GP) idle=b95/140/0 softirq=11738/11738

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-05-30 Thread bugproxy
--- Comment From ckuma...@in.ibm.com 2016-05-30 01:57 EDT--- (In reply to comment #52) > I'll try to reproduce the bug, so we can perform a reverse bisect and > identify the fix for this bug. > > Does this bug only happen on ppc64le? According to comment #31, this may > also be happening

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-04-18 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2016-04-19 01:25 EDT--- I don't have any machine currently for repeatedly testing with different upstream kernels as and when they are released. Since the test steps are quite simple and straight forward, I think it would be better to re-create the

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-04-06 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2016-04-06 07:38 EDT--- I have installed the 4.6-rc1 test kernel and executed the tests on a Bare Metal Open Power Hardware. I could not see the NMI softlockup call traces occurring. -- You received this bug notification because you are a member of

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-01-16 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2016-01-16 05:05 EDT--- I have copied lock_torture script on to the P8 server with the 3.13 kernel installed. Then executed the test script again in-order to re-create the scenario. root@powerkvmpok002:/opt/ltp/testcases/bin# ./lock_torture.sh

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-01-10 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2016-01-11 01:01 EDT--- I have installed 3.18 kernel provided in the link: https://launchpad.net/ubuntu/+source/linux/3.18.0-8.9/+build/6690705 root@powerkvmpok002:~/6690705# dpkg -i linux-image-3.18.0-8-generic_3.18.0-8.9_ppc64el.deb Selecting

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-01-08 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2016-01-08 08:03 EDT--- I have installed the proposed kernel which you have mentioned on the P8 Hardware. root@powerkvmpok002:~/5613571# dpkg -i linux-image-3.13.0-10-generic_3.13.0-10.30_ppc64el.deb Selecting previously unselected package

[Bug 1483343] Comment bridged from LTC Bugzilla

2016-01-05 Thread bugproxy
--- Comment From cha...@us.ibm.com 2016-01-05 17:08 EDT--- Re-posting most recent comment so Canonical can see it: Similar behaviour is observed in ubuntu 14.04.4 testing. runltp test execution stopped after executing rcu_torture test Fllowing Call trace is observed in "dmesg" output

[Bug 1483343] Comment bridged from LTC Bugzilla

2015-12-11 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2015-12-11 08:36 EDT--- I have downloaded the test kernel as suggested and executed the scenario again. root@powerkvmpok002:~/lp1483343# dpkg -i linux-image-3.19.0-41-generic_3.19.0-41.46~14.04.2_ppc64el.deb Selecting previously unselected package

[Bug 1483343] Comment bridged from LTC Bugzilla

2015-12-10 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2015-12-10 08:00 EDT--- I have installed Ubuntu 14.04.3 ISO on PowerNV 8284-22A P8 Hardware. Then executed the LTP lock_torture tests again on the same. root@powerkvmpok002:~# uname -a Linux powerkvmpok002 3.19.0-39-generic #44~14.04.1-Ubuntu SMP Wed

[Bug 1483343] Comment bridged from LTC Bugzilla

2015-12-10 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2015-12-11 06:16 EDT--- I have downloaded the mainline wily kernel as suggested and executed the scenario again. root@powerkvmpok002:~/mainline# wget

[Bug 1483343] Comment bridged from LTC Bugzilla

2015-08-11 Thread bugproxy
--- Comment From pavsu...@in.ibm.com 2015-08-11 10:13 EDT--- I have installed this kernel on a Power NV Hardware which is installed with Ubuntu 14.04.3. Then executed the tests again on the same OS. root@p7pite26os:~# uname -a Linux p7pite26os 3.19.0-26-generic #27 SMP Mon Aug 10

[Bug 1483343] Comment bridged from LTC Bugzilla

2015-08-11 Thread bugproxy
--- Comment From cha...@us.ibm.com 2015-08-11 16:52 EDT--- (In reply to comment #18) Created attachment 100943 [details] dmesg logs are attached when tests are done with new kernel provided So does the system lockup as before? Also, the dmesg attached doesn't show any softlockups. --