[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-07-26 Thread bugproxy
--- Comment From ppaid...@in.ibm.com 2018-07-26 02:01 EDT---
(In reply to comment #40)
> Could someone please also check that lscpu still works without error on
> amd64? Seems to me that we're fixing an edge case, which is fine, but we
> should also verify the common case functionality. I'd hate to release
> something that breaks the world on amd64 just because nobody checked it.
>
> (please also state the package version strings tested)

Currently we don't have amd64 machines here. Is it possible to test it
from distro side?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-03-07 Thread bugproxy
--- Comment From mainam...@in.ibm.com 2018-03-08 01:15 EDT---
Segmentation fault is may be due to library issue?

Pridhivi,
Can you verify once with upstream build and confirm

(gdb) run(gdb) run
Starting program: /usr/bin/lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported

Program received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
583 strtod_l.c: No such file or directory.
(gdb) bt
#0  __GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
#1  0x77d9607c in __GI_strtod (nptr=, endptr=) at strtod.c:64
#2  0x100060c0 in ?? ()
#3  0x100030e8 in ?? ()
#4  0x77d7309c in generic_start_main (main=0x10001f10, argc=, argv=0x7b18, auxvec=0x7bd0, init=, 
rtld_fini=, stack_end=,
fini=) at ../csu/libc-start.c:291
#5  0x77d73298 in __libc_start_main (argc=, 
argv=, ev=, auxvec=, 
rtld_fini=, stinfo=,
stack_on_entry=) at 
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
#6  0x in ?? ()
(gdb)

Starting program: /usr/bin/lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported

Program received signal SIGSEGV, Segmentation fault.
__GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
583 strtod_l.c: No such file or directory.
(gdb) bt
#0  __GI_strtod_l_internal (nptr=0x0, endptr=0x0, group=, 
loc=0x77f115f0 <_nl_global_locale>) at strtod_l.c:583
#1  0x77d9607c in __GI_strtod (nptr=, endptr=) at strtod.c:64
#2  0x100060c0 in ?? ()
#3  0x100030e8 in ?? ()
#4  0x77d7309c in generic_start_main (main=0x10001f10, argc=, argv=0x7b18, auxvec=0x7bd0, init=, 
rtld_fini=, stack_end=,
fini=) at ../csu/libc-start.c:291
#5  0x77d73298 in __libc_start_main (argc=, 
argv=, ev=, auxvec=, 
rtld_fini=, stinfo=,
stack_on_entry=) at 
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
#6  0x in ?? ()
(gdb)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from 

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-03-06 Thread bugproxy
--- Comment From ppaid...@in.ibm.com 2018-03-06 10:49 EDT---
(In reply to comment #28)
> ppaid...@in.ibm.com what version of the package did you test?  We were
> looking for a verification that the new package does NOT segfault.  It's
> unclear from your comment if you've tested the new version of the package
> and it failed verification, or if you were testing the previous,
> known-broken package.

I have tested with latest proposed package 2.27.1-6ubuntu3.5 and it
segfaults after CPU GUARD test, before test lscpu works fine.

root@ltc-test-ci1:~# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported
Segmentation fault
root@ltc-test-ci1:~# which lscpu
/usr/bin/lscpu
root@ltc-test-ci1:~# dpkg -S /usr/bin/lscpu
util-linux: /usr/bin/lscpu
root@ltc-test-ci1:~# dpkg -l | grep -i util-linux
ii  util-linux  2.27.1-6ubuntu3.5   
   ppc64el  miscellaneous system utilities
root@ltc-test-ci1:~#

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max 

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-03-06 Thread bugproxy
--- Comment From ppaid...@in.ibm.com 2018-03-06 09:23 EDT---
I got access to P8 FSP system today, I have verified that lscpu segfaults after 
first CPU garded.

root@:~# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):72
On-line CPU(s) list:   8-79
Thread(s) per core:8
Core(s) per socket:4
Socket(s): 2
NUMA node(s):  2
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported
Segmentation fault
root@x:~#

dmesg logs below errors:
[   57.463443] lscpu[2057]: unhandled signal 11 at  nip 
7128aba29b60 lr 7128aba29b38 code 30001
[   61.664064] lscpu[2058]: unhandled signal 11 at  nip 
78c241109b60 lr 78c241109b38 code 30001
root@x:~#

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-02-15 Thread bugproxy
--- Comment From mainam...@in.ibm.com 2018-02-15 07:47 EDT---
Pridhivi,
Please verify and update your comments

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   

[Touch-packages] [Bug 1732865] Comment bridged from LTC Bugzilla

2018-01-23 Thread bugproxy
--- Comment From ppaid...@in.ibm.com 2018-01-24 02:09 EDT---
Testcase:
On Host:
#lscpu
#service kdump-tools stop
#echo 10 > /proc/sys/kernel/panic

On FSP:
$ getscom pu.ex 10013100 -all
$ putscom pu.ex 10013100 1000 -n0 -p00 -c6
Here -p00--> Is the chip id, -c6 ---> is the core id under that chip, these 
should be selecte from the output
of the first command "getscom pu.ex 10013100 -all"

Repeat the above process 4 times with each time on a different chip with
master core getting injected.

Then run

lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):88
On-line CPU(s) list:   16-39,48-71,80-95,104-127
Thread(s) per core:8
Core(s) per socket:2
Socket(s): 4
NUMA node(s):  4
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported
CPU max MHz:   (null)
CPU min MHz:   (null)
L1d cache: 64K
L1i cache: 32K
L2 cache:  512K
L3 cache:  8192K
NUMA node0 CPU(s): 16-31
NUMA node1 CPU(s): 32-39,48-63
NUMA node16 CPU(s):64-71,80-95
NUMA node17 CPU(s):104-127

And also there is a automated testcase for this in 
https://github.com/open-power/op-test-framework
1. Clone the above repo.
2. Runt this command to GUARD the cpu.
./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/  --run testcases.OpTestHMIHandling.MalfunctionAlert

Run it multiple times to make multiple CPU's are garded.

This patch makes the customers to easily identify the CPU minimum and
maximum frequencies at which it can run(This happens only when there are
multiple CPU's are Garded.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete
Status in util-linux source package in Xenial:
  Incomplete

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 -