open-power / skiboot Goto Github PK

OPAL boot and runtime firmware for POWER

License: Apache License 2.0

Makefile 0.92% C 88.49% Assembly 0.22% C++ 0.50% Shell 5.26% Tcl 0.01% CMake 0.17% Python 0.80% Perl 0.37% SmPL 0.01% GDB 0.02% Roff 0.44% Batchfile 2.79%

openpower firmware bmc kernel c opal linux powerpc ppc64le power8 power9

skiboot's Introduction

skiboot

Firmware for OpenPower systems.

Source: https://github.com/open-power/skiboot

Mailing list: [email protected]

Info/subscribe: https://lists.ozlabs.org/listinfo/skiboot

Archives: https://lists.ozlabs.org/pipermail/skiboot/

Patchwork: http://patchwork.ozlabs.org/project/skiboot/list/

Documentation: http://open-power.github.io/skiboot/doc/index.html

Overview

OPAL firmware (OpenPower Abstraction Layer) comes in several parts.

A simplified flow of what happens when the power button is pressed is:

The baseboard management controller (BMC) powers the system on.
The BMC selects the master chip and releases the self-boot engines (SBEs) on the POWER8 chips, master last.
The BMC relinquishes control of the flexible service interface (FSI) SCAN/SCOM engines.
The hostboot firmware IPLs the system. It initiates a secondary power-on sequence through a digital power systems sweep (DPSS).
The hostboot firmware loads the OPAL image and moves all processors to their execution starting points.

Here, the OPAL image is three parts:

skiboot (includes OPAL runtime services)
skiroot - the bootloader environment
- kernel
- initramfs (containing petitboot bootloader)

They may be all part of one payload or three separate images (depending on platform).

The bootloader will kexec a host kernel (probably linux). The host OS can make OPAL calls. The OPAL API is documented in doc/opal-api/ (there are missing parts, patches are welcome!)

See doc/overview.rst for a more in depth overview of skiboot.

Building

Any host OS can build and test skiboot provided it has a C cross compiler for big endian powerpc64. All good Linux distributions (and several bad ones) provide a packaged compiler that can be installed through the usual package management tools.

To build on Ubuntu:

apt-get install gcc-powerpc64le-linux-gnu gcc valgrind \
	expect libssl-dev device-tree-compiler make \
	xz-utils libmbedtls-dev
CROSS=powerpc64le-linux-gnu- make -j`nproc`

To build on Fedora:

dnf install gcc-powerpc64le-linux-gnu binutils-powerpc64-linux-gnu gcc make \
    diffutils findutils expect valgrind-devel dtc openssl-devel xz \
    mbedtls-devel
CROSS=powerpc64le-linux-gnu- make -j`nproc`

(The little-endian powerpc64le compilers in Ubuntu and Fedora are actually bi-endian and can compile skiboot even though it's big-endian. We recommend installing a little-endian toolchain if you plan on building other projects.)

On any POWER system with a bi-endian system compiler:

CROSS="" make -j`nproc`

Alternatively, pre-built cross compilers for x86 systems can be downloaded from here: https://www.kernel.org/pub/tools/crosstool/ When using these compilers add /opt/cross/gcc-4.8.0-nolibc/powerpc64-linux/bin/ to your PATH. Once this is done skiboot can be compiler by just running make

Building Documentation

We use Sphinx to produce various documentation from reStructuredText (preferred) and Markdown. The Sphinx documentation has a useful primer for reStructuredText here. And the docutils website has a nice quick reference for the basic constructes.

Building on Fedora

dnf install python3-sphinx python3-recommonmark.noarch
pip install -r doc/requirements.txt
make -C doc/ html SPHINXBUILD=sphinx-build-3

On Ubuntu:

Patches welcome!

View the output using doc/_build/html/index.html

Testing

Skiboot comes with a set of unit tests that can be run on your desktop. They can can be run with:

make check

To test in a simulator, install the IBM POWER8 Functional Simulator from: http://www-304.ibm.com/support/customercare/sas/f/pwrfs/home.html Also see external/mambo/README.md

Qemu as of version 2.8 implements the 'powernv' machine model and is sufficient to run skiboot:

qemu-system-ppc64 -M powernv -m 3G -nographic -L /path/to/skiboot/

To run a boot-to-bootloader test you need a Linux kernel image 'zImage.epapr'. Build one using the opal_defconfig config for op-build. See https://github.com/open-power/op-build/ on how to build, or download one from https://github.com/open-power/op-build/releases/ .

Drop zImage.epapr in the skiboot directory and the skiboot test suite will automatically pick it up. You can also run a combined skiboot and Linux test in Qemu (version 3.0+):

qemu-system-ppc64 -M powernv -m 3G -nographic -kernel zImage.epapr -L /path/to/skiboot/

See opal-ci/README for further testing instructions.

To test on real hardware, you will need to understand how to flash new skiboot onto your system. This will vary from platform to platform.

You may want to start with external/boot-tests/boot_test.sh as it can (provided the correct usernames/passwords) automatically flash a new skiboot onto ASTBMC based OpenPower machines.

Hacking

All patches should be sent to the mailing list with linux-kernel style 'Signed-Off-By'. The following git commands are your friends:

git commit -s
git format-patch

You probably want to read the linux https://kernel.org/doc/html/latest/process/submitting-patches.html as much of it applies to skiboot.

Output files

The Skiboot build process produces a bunch of different outputs. This is what they are, and where you should use them:

skiboot.elf: The output of the linker. Don't flash to a system, but useful when debugging

skiboot.lid: The raw binary object, named .lid because IBM. Flash this on really old P8 systems, the POWER Functional Simulator (mambo), or FSP systems

skiboot.lid.stb: Lid wrapped with secure boot header. Use on FSP systems

skiboot.lid.xz: Compressed raw binary. Use this on a OpenPower P8

skiboot.lid.xz.stb: Compressed raw binary wrapped with a secure boot header. Use this on OpenPower P9 systems

License

See LICENSE

skiboot's People

Contributors

Stargazers

Watchers

Forkers

qiumike stewartsmith wlbjcn gdhh shenki ddstreet apopple fatsweetfish jk-ozlabs ploetzma dcrowell77 legoater mikey cyrilbur-ibm svaidy mpe hegdevasant sharkcz frank-yujiang kamalesh-babulal joeyang4 csmart vaibhav92 bogatseng sambltc maddy-kerneldev liufujun135 rlippert rainhata glassrose shilpasri anoo1 tomjoseph83 ruscur bsingharora darkstarsword k0da maheshsal ajdlinux srideviramesh 1312mukesh spartan0007 pridhiviraj shreyasbp oohal kencheniec antonblanchard leitao r4f4 mukeshojha fbarrat robin903230 rpgrimm ryanwyluo tk-wfischer saqibkh jimsmc stevelinch over-enthusiastic konglay amboar jnider m-brow zhiminwu vrbagalkote jjscheel wak-google deadbeefh bryzikm ibm-op-release jeffv03 mfoliveira nailanawshaba a-barrera asowani ghatwala aik iam41xin toshywoshy rashmicag liyi-ibm sammj rarbab fspbld anjutsudhakar maxpoliak hramrach clombi the-real-meoba geissonator jeffkellington madscientist159 debmc wistron-corporation erichte-ibm balamuruhans hankchang power-gem5 lili-lilili daxtens

skiboot's Issues

NVRAM cleanups

The prlogs look a bit strange these days. See skiboot-5.4.0 booting for the first time on a Palmetto below.

We should create a pre-initialised NVRMA partition in the PNOR to save us doing this at boot.

The downside of that would be we don't test this code path as often. Do we have some tests that make sure skiboot's NVRAM always works?

    2.356072633,5] NVRAM: Size is 576 KB
[    3.032408733,3] NVRAM: Partition at offset 0x0 has incorrect 0 length
[    3.032505627,3] NVRAM: Re-initializing (size: 0x00090000)
[    3.032590744,7] NVRAM: Created 'ibm,skiboot' partition at 0x00000000 for size 0x00000100 with cksum 0xb5
[    3.032593479,7] NVRAM: Created 'common' partition at 0x00001000 for size 0x00001000 with cksum 0x0c
[    3.032595759,7] NVRAM: Created 'wwwwwwwwwwww' partition at 0x00011000 for size 0x00007f00 with cksum 0x98
[    3.032598677,7] LIBFLASH: Smart writing to 0x1961000..019f1000...
[    3.032600250,7] LIBFLASH:   reading page 0x01961000..0x01962000...[    3.033912391,7]  need erase !
[    3.033913150,7] LIBFLASH: Erasing 0x1961000..01962000...
[    3.046019920,7] LIBFLASH: Writing to 0x01961000..001962000...
[    3.056795837,7] LIBFLASH: Verifying...
[    3.058110804,7] LIBFLASH:   reading page 0x01962000..0x01963000...[    3.059415278,7]  need erase !
[    3.059416015,7] LIBFLASH: Erasing 0x1962000..01963000...
[    3.071446756,7] LIBFLASH: Writing to 0x01962000..001963000...
[    3.082213923,7] LIBFLASH: Verifying...
[    3.083533976,7] LIBFLASH:   reading page 0x01963000..0x01964000...[    3.084846885,7]  same !
[    3.084847533,7] LIBFLASH:   reading page 0x01964000..0x01965000...[    3.086164489,7]  same !
[    3.086165132,7] LIBFLASH:   reading page 0x01965000..0x01966000...[    3.087483695,7]  same !
[    3.087484334,7] LIBFLASH:   reading page 0x01966000..0x01967000...[    3.088808559,7]  same !
[    3.088809217,7] LIBFLASH:   reading page 0x01967000..0x01968000...[    3.090125179,7]  same !
[    3.090125828,7] LIBFLASH:   reading page 0x01968000..0x01969000...[    3.091441530,7]  same !
[    3.091442191,7] LIBFLASH:   reading page 0x01969000..0x0196a000...[    3.092759873,7]  same !
[    3.092760514,7] LIBFLASH:   reading page 0x0196a000..0x0196b000...[    3.094077946,7]  same !
[    3.094078587,7] LIBFLASH:   reading page 0x0196b000..0x0196c000...[    3.095399679,7]  same !
[    3.095400316,7] LIBFLASH:   reading page 0x0196c000..0x0196d000...[    3.096721227,7]  same !
[    3.096721884,7] LIBFLASH:   reading page 0x0196d000..0x0196e000...[    3.098038551,7]  same !
[    3.098039225,7] LIBFLASH:   reading page 0x0196e000..0x0196f000...[    3.099352147,7]  same !
[    3.099352803,7] LIBFLASH:   reading page 0x0196f000..0x01970000...[    3.100677126,7]  same !
[    3.100677823,7] LIBFLASH:   reading page 0x01970000..0x01971000...[    3.101992381,7]  same !
[    3.101993061,7] LIBFLASH:   reading page 0x01971000..0x01972000...[    3.103308025,7]  same !
[    3.103308751,7] LIBFLASH:   reading page 0x01972000..0x01973000...[    3.104619847,7]  need erase !
[    3.104620655,7] LIBFLASH: Erasing 0x1972000..01973000...
[    3.118555259,7] LIBFLASH: Writing to 0x01972000..001973000...
[    3.129326977,7] LIBFLASH: Verifying...
[    3.130639846,7] LIBFLASH:   reading page 0x01973000..0x01974000...[    3.131960441,7]  same !
[    3.131961125,7] LIBFLASH:   reading page 0x01974000..0x01975000...[    3.133282046,7]  same !
[    3.133282726,7] LIBFLASH:   reading page 0x01975000..0x01976000...[    3.134602066,7]  same !
[    3.134602735,7] LIBFLASH:   reading page 0x01976000..0x01977000...[    3.135929113,7]  same !
[    3.135929802,7] LIBFLASH:   reading page 0x01977000..0x01978000...[    3.137245456,7]  same !
[    3.137246127,7] LIBFLASH:   reading page 0x01978000..0x01979000...[    3.138569489,7]  same !
[    3.138570182,7] LIBFLASH:   reading page 0x01979000..0x0197a000...[    3.139889260,7]  same !
[    3.139889939,7] LIBFLASH:   reading page 0x0197a000..0x0197b000...[    3.141210302,7]  same !
[    3.141210994,7] LIBFLASH:   reading page 0x0197b000..0x0197c000...[    3.142529233,7]  same !
[    3.142529909,7] LIBFLASH:   reading page 0x0197c000..0x0197d000...[    3.143852148,7]  same !
[    3.143852830,7] LIBFLASH:   reading page 0x0197d000..0x0197e000...[    3.145173647,7]  same !
[    3.145174324,7] LIBFLASH:   reading page 0x0197e000..0x0197f000...[    3.146497744,7]  same !
[    3.146498418,7] LIBFLASH:   reading page 0x0197f000..0x01980000...[    3.147816563,7]  same !
[    3.147817233,7] LIBFLASH:   reading page 0x01980000..0x01981000...[    3.149141047,7]  same !
[    3.149141711,7] LIBFLASH:   reading page 0x01981000..0x01982000...[    3.150458250,7]  same !
[    3.150458929,7] LIBFLASH:   reading page 0x01982000..0x01983000...[    3.151775017,7]  same !
[    3.151775689,7] LIBFLASH:   reading page 0x01983000..0x01984000...[    3.153096193,7]  same !
[    3.153096871,7] LIBFLASH:   reading page 0x01984000..0x01985000...[    3.154416767,7]  same !
[    3.154417464,7] LIBFLASH:   reading page 0x01985000..0x01986000...[    3.155739500,7]  same !
[    3.155740180,7] LIBFLASH:   reading page 0x01986000..0x01987000...[    3.157056575,7]  same !
[    3.157057247,7] LIBFLASH:   reading page 0x01987000..0x01988000...[    3.158374501,7]  same !
[    3.158375191,7] LIBFLASH:   reading page 0x01988000..0x01989000...[    3.159695165,7]  same !
[    3.159695843,7] LIBFLASH:   reading page 0x01989000..0x0198a000...[    3.161016244,7]  same !
[    3.161016915,7] LIBFLASH:   reading page 0x0198a000..0x0198b000...[    3.162334426,7]  same !
[    3.162335119,7] LIBFLASH:   reading page 0x0198b000..0x0198c000...[    3.163649226,7]  same !
[    3.163649903,7] LIBFLASH:   reading page 0x0198c000..0x0198d000...[    3.164969647,7]  same !
[    3.164970335,7] LIBFLASH:   reading page 0x0198d000..0x0198e000...[    3.166286834,7]  same !
[    3.166287515,7] LIBFLASH:   reading page 0x0198e000..0x0198f000...[    3.167609847,7]  same !
[    3.167610537,7] LIBFLASH:   reading page 0x0198f000..0x01990000...[    3.168927878,7]  same !
[    3.168928546,7] LIBFLASH:   reading page 0x01990000..0x01991000...[    3.170244771,7]  same !
[    3.170245455,7] LIBFLASH:   reading page 0x01991000..0x01992000...[    3.171567400,7]  same !
[    3.171568078,7] LIBFLASH:   reading page 0x01992000..0x01993000...[    3.172881843,7]  same !
[    3.172882538,7] LIBFLASH:   reading page 0x01993000..0x01994000...[    3.174197583,7]  same !
[    3.174198271,7] LIBFLASH:   reading page 0x01994000..0x01995000...[    3.175512356,7]  same !
[    3.175513058,7] LIBFLASH:   reading page 0x01995000..0x01996000...[    3.176826715,7]  same !
[    3.176827389,7] LIBFLASH:   reading page 0x01996000..0x01997000...[    3.178143287,7]  same !
[    3.178143980,7] LIBFLASH:   reading page 0x01997000..0x01998000...[    3.179462558,7]  same !
[    3.179463220,7] LIBFLASH:   reading page 0x01998000..0x01999000...[    3.180780071,7]  same !
[    3.180780743,7] LIBFLASH:   reading page 0x01999000..0x0199a000...[    3.182103386,7]  same !
[    3.182104064,7] LIBFLASH:   reading page 0x0199a000..0x0199b000...[    3.183423748,7]  same !
[    3.183424455,7] LIBFLASH:   reading page 0x0199b000..0x0199c000...[    3.184740527,7]  same !
[    3.184741214,7] LIBFLASH:   reading page 0x0199c000..0x0199d000...[    3.186060751,7]  same !
[    3.186061451,7] LIBFLASH:   reading page 0x0199d000..0x0199e000...[    3.187375837,7]  same !
[    3.187376520,7] LIBFLASH:   reading page 0x0199e000..0x0199f000...[    3.188692959,7]  same !
[    3.188693675,7] LIBFLASH:   reading page 0x0199f000..0x019a0000...[    3.190016413,7]  same !
[    3.190017091,7] LIBFLASH:   reading page 0x019a0000..0x019a1000...[    3.191335087,7]  same !
[    3.191335767,7] LIBFLASH:   reading page 0x019a1000..0x019a2000...[    3.192653988,7]  same !
[    3.192654680,7] LIBFLASH:   reading page 0x019a2000..0x019a3000...[    3.193974071,7]  same !
[    3.193974754,7] LIBFLASH:   reading page 0x019a3000..0x019a4000...[    3.195297135,7]  same !
[    3.195297836,7] LIBFLASH:   reading page 0x019a4000..0x019a5000...[    3.196613823,7]  same !
[    3.196614499,7] LIBFLASH:   reading page 0x019a5000..0x019a6000...[    3.197936870,7]  same !
[    3.197937559,7] LIBFLASH:   reading page 0x019a6000..0x019a7000...[    3.199260833,7]  same !
[    3.199261520,7] LIBFLASH:   reading page 0x019a7000..0x019a8000...[    3.200580517,7]  same !
[    3.200581183,7] LIBFLASH:   reading page 0x019a8000..0x019a9000...[    3.201898767,7]  same !
[    3.201899443,7] LIBFLASH:   reading page 0x019a9000..0x019aa000...[    3.203217799,7]  same !
[    3.203218503,7] LIBFLASH:   reading page 0x019aa000..0x019ab000...[    3.204538258,7]  same !
[    3.204538943,7] LIBFLASH:   reading page 0x019ab000..0x019ac000...[    3.205855338,7]  same !
[    3.205856020,7] LIBFLASH:   reading page 0x019ac000..0x019ad000...[    3.207173545,7]  same !
[    3.207174207,7] LIBFLASH:   reading page 0x019ad000..0x019ae000...[    3.208491536,7]  same !
[    3.208492219,7] LIBFLASH:   reading page 0x019ae000..0x019af000...[    3.209809447,7]  same !
[    3.209810129,7] LIBFLASH:   reading page 0x019af000..0x019b0000...[    3.211123151,7]  same !
[    3.211123823,7] LIBFLASH:   reading page 0x019b0000..0x019b1000...[    3.212440568,7]  same !
[    3.212441250,7] LIBFLASH:   reading page 0x019b1000..0x019b2000...[    3.213762754,7]  same !
[    3.213763422,7] LIBFLASH:   reading page 0x019b2000..0x019b3000...[    3.215081667,7]  same !
[    3.215082338,7] LIBFLASH:   reading page 0x019b3000..0x019b4000...[    3.216398967,7]  same !
[    3.216399647,7] LIBFLASH:   reading page 0x019b4000..0x019b5000...[    3.217717815,7]  same !
[    3.217718494,7] LIBFLASH:   reading page 0x019b5000..0x019b6000...[    3.219040564,7]  same !
[    3.219041256,7] LIBFLASH:   reading page 0x019b6000..0x019b7000...[    3.220359359,7]  same !
[    3.220360043,7] LIBFLASH:   reading page 0x019b7000..0x019b8000...[    3.221679257,7]  same !
[    3.221679935,7] LIBFLASH:   reading page 0x019b8000..0x019b9000...[    3.222993596,7]  same !
[    3.222994266,7] LIBFLASH:   reading page 0x019b9000..0x019ba000...[    3.224314094,7]  same !
[    3.224314782,7] LIBFLASH:   reading page 0x019ba000..0x019bb000...[    3.225632383,7]  same !
[    3.225633059,7] LIBFLASH:   reading page 0x019bb000..0x019bc000...[    3.226950031,7]  same !
[    3.226950719,7] LIBFLASH:   reading page 0x019bc000..0x019bd000...[    3.228266503,7]  same !
[    3.228267183,7] LIBFLASH:   reading page 0x019bd000..0x019be000...[    3.229586863,7]  same !
[    3.229587541,7] LIBFLASH:   reading page 0x019be000..0x019bf000...[    3.230898542,7]  same !
[    3.230899246,7] LIBFLASH:   reading page 0x019bf000..0x019c0000...[    3.232218687,7]  same !
[    3.232219364,7] LIBFLASH:   reading page 0x019c0000..0x019c1000...[    3.233533359,7]  same !
[    3.233534034,7] LIBFLASH:   reading page 0x019c1000..0x019c2000...[    3.234856895,7]  same !
[    3.234857579,7] LIBFLASH:   reading page 0x019c2000..0x019c3000...[    3.236171314,7]  same !
[    3.236172083,7] LIBFLASH:   reading page 0x019c3000..0x019c4000...[    3.237489195,7]  same !
[    3.237489905,7] LIBFLASH:   reading page 0x019c4000..0x019c5000...[    3.238810141,7]  same !
[    3.238810823,7] LIBFLASH:   reading page 0x019c5000..0x019c6000...[    3.240127500,7]  same !
[    3.240128175,7] LIBFLASH:   reading page 0x019c6000..0x019c7000...[    3.241449309,7]  same !
[    3.241449986,7] LIBFLASH:   reading page 0x019c7000..0x019c8000...[    3.242766358,7]  same !
[    3.242767031,7] LIBFLASH:   reading page 0x019c8000..0x019c9000...[    3.244080643,7]  same !
[    3.244081327,7] LIBFLASH:   reading page 0x019c9000..0x019ca000...[    3.245402636,7]  same !
[    3.245403303,7] LIBFLASH:   reading page 0x019ca000..0x019cb000...[    3.246722198,7]  same !
[    3.246722867,7] LIBFLASH:   reading page 0x019cb000..0x019cc000...[    3.248037864,7]  same !
[    3.248038541,7] LIBFLASH:   reading page 0x019cc000..0x019cd000...[    3.249355853,7]  same !
[    3.249356534,7] LIBFLASH:   reading page 0x019cd000..0x019ce000...[    3.250670622,7]  same !
[    3.250671311,7] LIBFLASH:   reading page 0x019ce000..0x019cf000...[    3.251990817,7]  same !
[    3.251991530,7] LIBFLASH:   reading page 0x019cf000..0x019d0000...[    3.253310639,7]  same !
[    3.253311319,7] LIBFLASH:   reading page 0x019d0000..0x019d1000...[    3.254629243,7]  same !
[    3.254629919,7] LIBFLASH:   reading page 0x019d1000..0x019d2000...[    3.255949476,7]  same !
[    3.255950146,7] LIBFLASH:   reading page 0x019d2000..0x019d3000...[    3.257267529,7]  same !
[    3.257268270,7] LIBFLASH:   reading page 0x019d3000..0x019d4000...[    3.258592821,7]  same !
[    3.258593540,7] LIBFLASH:   reading page 0x019d4000..0x019d5000...[    3.259914370,7]  same !
[    3.259915071,7] LIBFLASH:   reading page 0x019d5000..0x019d6000...[    3.261233393,7]  same !
[    3.261234091,7] LIBFLASH:   reading page 0x019d6000..0x019d7000...[    3.262551678,7]  same !
[    3.262552363,7] LIBFLASH:   reading page 0x019d7000..0x019d8000...[    3.263869806,7]  same !
[    3.263870518,7] LIBFLASH:   reading page 0x019d8000..0x019d9000...[    3.265188515,7]  same !
[    3.265189197,7] LIBFLASH:   reading page 0x019d9000..0x019da000...[    3.266505302,7]  same !
[    3.266505982,7] LIBFLASH:   reading page 0x019da000..0x019db000...[    3.267824002,7]  same !
[    3.267824698,7] LIBFLASH:   reading page 0x019db000..0x019dc000...[    3.269141541,7]  same !
[    3.269142209,7] LIBFLASH:   reading page 0x019dc000..0x019dd000...[    3.270457247,7]  same !
[    3.270457935,7] LIBFLASH:   reading page 0x019dd000..0x019de000...[    3.271775630,7]  same !
[    3.271776303,7] LIBFLASH:   reading page 0x019de000..0x019df000...[    3.273093299,7]  same !
[    3.273093973,7] LIBFLASH:   reading page 0x019df000..0x019e0000...[    3.274412899,7]  same !
[    3.274413575,7] LIBFLASH:   reading page 0x019e0000..0x019e1000...[    3.275731571,7]  same !
[    3.275732242,7] LIBFLASH:   reading page 0x019e1000..0x019e2000...[    3.277053855,7]  need write !
[    3.277054678,7] LIBFLASH: Writing to 0x019e1000..0019e2000...
[    3.287839967,7] LIBFLASH: Verifying...
[    3.289158010,7] LIBFLASH:   reading page 0x019e2000..0x019e3000...[    3.290474045,7]  need write !
[    3.290474813,7] LIBFLASH: Writing to 0x019e2000..0019e3000...
[    3.301254926,7] LIBFLASH: Verifying...
[    3.302569836,7] LIBFLASH:   reading page 0x019e3000..0x019e4000...[    3.303895407,7]  need write !
[    3.303896191,7] LIBFLASH: Writing to 0x019e3000..0019e4000...
[    3.314664152,7] LIBFLASH: Verifying...
[    3.315978543,7] LIBFLASH:   reading page 0x019e4000..0x019e5000...[    3.317302509,7]  need write !
[    3.317303279,7] LIBFLASH: Writing to 0x019e4000..0019e5000...
[    3.328077405,7] LIBFLASH: Verifying...
[    3.329387875,7] LIBFLASH:   reading page 0x019e5000..0x019e6000...[    3.330705923,7]  need write !
[    3.330706718,7] LIBFLASH: Writing to 0x019e5000..0019e6000...
[    3.341483775,7] LIBFLASH: Verifying...
[    3.342796223,7] LIBFLASH:   reading page 0x019e6000..0x019e7000...[    3.344116438,7]  need write !
[    3.344117219,7] LIBFLASH: Writing to 0x019e6000..0019e7000...
[    3.354885392,7] LIBFLASH: Verifying...
[    3.356196311,7] LIBFLASH:   reading page 0x019e7000..0x019e8000...[    3.357515655,7]  need write !
[    3.357516454,7] LIBFLASH: Writing to 0x019e7000..0019e8000...
[    3.368296154,7] LIBFLASH: Verifying...
[    3.369611076,7] LIBFLASH:   reading page 0x019e8000..0x019e9000...[    3.370928764,7]  need write !
[    3.370929541,7] LIBFLASH: Writing to 0x019e8000..0019e9000...
[    3.381705167,7] LIBFLASH: Verifying...
[    3.383021352,7] LIBFLASH:   reading page 0x019e9000..0x019ea000...[    3.384343519,7]  need write !
[    3.384344294,7] LIBFLASH: Writing to 0x019e9000..0019ea000...
[    3.395124199,7] LIBFLASH: Verifying...
[    3.396433951,7] LIBFLASH:   reading page 0x019ea000..0x019eb000...[    3.397753294,7]  need write !
[    3.397754047,7] LIBFLASH: Writing to 0x019ea000..0019eb000...
[    3.408529949,7] LIBFLASH: Verifying...
[    3.409846911,7] LIBFLASH:   reading page 0x019eb000..0x019ec000...[    3.411164337,7]  need write !
[    3.411165151,7] LIBFLASH: Writing to 0x019eb000..0019ec000...
[    3.421941022,7] LIBFLASH: Verifying...
[    3.423254212,7] LIBFLASH:   reading page 0x019ec000..0x019ed000...[    3.424577255,7]  need write !
[    3.424578057,7] LIBFLASH: Writing to 0x019ec000..0019ed000...
[    3.435353823,7] LIBFLASH: Verifying...
[    3.436668102,7] LIBFLASH:   reading page 0x019ed000..0x019ee000...[    3.437983951,7]  need write !
[    3.437984763,7] LIBFLASH: Writing to 0x019ed000..0019ee000...
[    3.448756850,7] LIBFLASH: Verifying...
[    3.450069369,7] LIBFLASH:   reading page 0x019ee000..0x019ef000...[    3.451394713,7]  need write !
[    3.451395519,7] LIBFLASH: Writing to 0x019ee000..0019ef000...
[    3.462165246,7] LIBFLASH: Verifying...
[    3.463479391,7] LIBFLASH:   reading page 0x019ef000..0x019f0000...[    3.464798597,7]  need write !
[    3.464799368,7] LIBFLASH: Writing to 0x019ef000..0019f0000...
[    3.475577535,7] LIBFLASH: Verifying...
[    3.476885948,7] LIBFLASH:   reading page 0x019f0000..0x019f1000...[    3.478202881,7]  need write !
[    3.478203646,7] LIBFLASH: Writing to 0x019f0000..0019f1000...
[    3.488981066,7] LIBFLASH: Verifying...

OPALCI: PCI: built-in device not found: Network Mezz (loc: 10)

cat /sys/firmware/opal/msglog | grep -i skiboot
[ 46.119285813,5] SkiBoot e5477ad starting...

cat /sys/firmware/opal/msglog | grep -i ,3

[    5.309108639,3] PHB#0000: Base location code not found !
[    7.030317466,3] PHB#0001: Base location code not found !
[    8.231482927,3] PHB#0002: Base location code not found !
[   13.310374630,3] FLASH: No ROOTFS partition
[   17.069198739,3] PCI: built-in device not found: Network Mezz (loc: 10)

lspci
0000:00:00.0 PCI bridge: IBM Device 03dc
0000:01:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
0000:01:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
0001:00:00.0 PCI bridge: IBM Device 03dc
0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:0a.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:10.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:02:11.0 PCI bridge: PLX Technology, Inc. PEX 8748 48-Lane, 12-Port PCI Express Gen 3 (8 GT/s) Switch, 27 x 27mm FCBGA (rev ca)
0001:08:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller (rev 11)
0001:09:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02)
0001:0a:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03)
0001:0b:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)
0001:0c:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
0001:0c:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
0001:0c:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
0001:0c:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
0002:00:00.0 PCI bridge: IBM Device 03dc
0002:01:00.0 RAID bus controller: Adaptec Series 8 12G SAS/PCIe 3 (rev 01)

PCI SLOT Table in Failed condition(Where the message seen):

[   17.069382375,5] PHB#0000:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot3 
[   17.091008644,5] PHB#0000:01:00.0 [EP  ] 14e4 168e R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   17.109598415,5] PHB#0000:01:00.1 [EP  ] 14e4 168e R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   17.142674143,5] PHB#0001:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..11 SLOT=Backplane PLX 
[   17.170699338,5] PHB#0001:01:00.0 [SWUP] 10b5 8748 R:ca C:060400 B:02..11 LOC_CODE=Backplane PLX
[   17.201709901,5] PHB#0001:02:01.0 [SWDN] 10b5 8748 R:ca C:060400 B:03..07 SLOT=Network Mezz 
[   17.225853589,5] PHB#0001:02:08.0 [SWDN] 10b5 8748 R:ca C:060400 B:08..08 SLOT=Storage Mezz 
[   17.258334281,5] PHB#0001:08:00.0 [LGCY] 1b4b 9235 R:11 C:010601 (          sata) LOC_CODE=Storage Mezz
[   17.309228487,5] PHB#0001:02:09.0 [SWDN] 10b5 8748 R:ca C:060400 B:09..09 SLOT=Backplane USB 
[   17.319427565,5] PHB#0001:09:00.0 [EP  ] 104c 8241 R:02 C:0c0330 (      usb-xhci) LOC_CODE=Backplane USB
[   17.352579889,5] PHB#0001:02:0a.0 [SWDN] 10b5 8748 R:ca C:060400 B:0a..0b SLOT=Backplane BMC 
[   17.356115475,5] PHB#0001:0a:00.0 [ETOX] 1a03 1150 R:03 C:060400 B:0b..0b LOC_CODE=Backplane BMC
[   17.406221174,5] PHB#0001:0b:00.0 [PCID] 1a03 2000 R:30 C:030000 (           vga) LOC_CODE=Backplane BMC
[   17.434170287,5] PHB#0001:02:10.0 [SWDN] 10b5 8748 R:ca C:060400 B:0c..0c SLOT=Slot2 
[   17.462803667,5] PHB#0001:0c:00.0 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
[   17.488542543,5] PHB#0001:0c:00.1 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
[   18.000624471,5] PHB#0001:0c:00.2 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
[   18.023915229,5] PHB#0001:0c:00.3 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
[   18.063615917,5] PHB#0001:02:11.0 [SWDN] 10b5 8748 R:ca C:060400 B:0d..11 SLOT=Slot1 
[   18.101210514,5] PHB#0002:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot4 
[   18.155857714,5] PHB#0002:01:00.0 [EP  ] 9005 028d R:01 C:010400 (          raid) LOC_CODE=Slot4

PCI SLOT Table in Working condition(Where the message not seen):

07:38:39 [   15.035227690,5] PHB#0000:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot3 
07:38:39 [   15.041566803,5] PHB#0000:01:00.0 [EP  ] 14e4 168e R:10 C:020000 (      ethernet) LOC_CODE=Slot3
07:38:39 [   15.080866922,5] PHB#0000:01:00.1 [EP  ] 14e4 168e R:10 C:020000 (      ethernet) LOC_CODE=Slot3
07:38:39 [   15.148525068,5] PHB#0001:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..11 SLOT=Backplane PLX 
07:38:39 [   15.173491418,5] PHB#0001:01:00.0 [SWUP] 10b5 8748 R:ca C:060400 B:02..11 LOC_CODE=Backplane PLX
07:38:39 [   15.254674442,5] PHB#0001:02:01.0 [SWDN] 10b5 8748 R:ca C:060400 B:03..07 SLOT=Network Mezz 
07:38:39 [   15.265485164,5] PHB#0001:02:08.0 [SWDN] 10b5 8748 R:ca C:060400 B:08..08 SLOT=Storage Mezz 
07:38:39 [   15.365108159,5] PHB#0001:08:00.0 [LGCY] 1b4b 9235 R:11 C:010601 (          sata) LOC_CODE=Storage Mezz
07:38:39 [   15.379607674,5] PHB#0001:02:09.0 [SWDN] 10b5 8748 R:ca C:060400 B:09..09 SLOT=Backplane USB 
07:38:39 [   15.473336354,5] PHB#0001:09:00.0 [EP  ] 104c 8241 R:02 C:0c0330 (      usb-xhci) LOC_CODE=Backplane USB
07:38:39 [   16.009020823,5] PHB#0001:02:0a.0 [SWDN] 10b5 8748 R:ca C:060400 B:0a..0b SLOT=Backplane BMC 
07:38:39 [   16.075619566,5] PHB#0001:0a:00.0 [ETOX] 1a03 1150 R:03 C:060400 B:0b..0b LOC_CODE=Backplane BMC
07:38:39 [   16.198482509,5] PHB#0001:0b:00.0 [PCID] 1a03 2000 R:30 C:030000 (           vga) LOC_CODE=Backplane BMC
07:38:39 [   16.230003307,5] PHB#0001:02:10.0 [SWDN] 10b5 8748 R:ca C:060400 B:0c..0c SLOT=Slot2 
07:38:39 [   16.286269061,5] PHB#0001:0c:00.0 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
07:38:39 [   16.474850589,5] PHB#0001:0c:00.1 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
07:38:39 [   17.055440983,5] PHB#0001:0c:00.2 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
07:38:39 [   17.080778044,5] PHB#0001:0c:00.3 [EP  ] 14e4 1657 R:01 C:020000 (      ethernet) LOC_CODE=Slot2
07:38:39 [   17.172248811,5] PHB#0001:02:11.0 [SWDN] 10b5 8748 R:ca C:060400 B:0d..11 SLOT=Slot1 
07:38:39 [   17.198615960,5] PHB#0002:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot4 
07:38:39 [   17.311650977,5] PHB#0002:01:00.0 [EP  ] 9005 028d R:01 C:010400 (          raid) LOC_CODE=Slot4

FSPCT: No centaur memory detected after cold reset

No centaur memory was detected after doing a cold reset of the BMC:

System Info:
BMC ip address= 9.41.164.80 name=habcap10.aus.stglabs.ibm.com

OS ip address=9.41.164.12 name=habcap10p1.aus.stglabs.ibm.com

Following is a list of commands that were executed and their outcome:

HOST OS: $ sudo /home/tyan/skiboot/external/xscom-utils/getscom -l
[sudo] password for tyan:

Chip ID	Rev	Chip type
80000005	DD2.0	Centaur memory buffer
80000004	DD2.0	Centaur memory buffer
80000001	DD2.0	Centaur memory buffer
80000000	DD2.0	Centaur memory buffer
00000000	DD2.0	P8 (Venice) processor

ipmitool -H habcap10 -I lanplus -U ${Userid} -P ${Password} mc cold reset

HOST OS: $ sudo /home/tyan/skiboot/external/xscom-utils/getscom -l
[sudo] password for tyan:

Chip ID	Rev	Chip type
00000000	DD2.0	P8 (Venice) processor <=========== No Centaur Memory

Also attached is an output obtained from the serial port, which shows that the BMC was unable to write/detect these memory.

Host wont boot after injecting checktsop [Barreleye]

Driver Info

VERSION_ID="v1.99.3-42-ge8c604b"
Build version- 20170306191603

Test result description:

OS won't boot and state in HOST_BOOTING after injecting checktsop on OS.

Expectation:

OS should auto reboot after injecting check stop through OS.

Procedure:

Enable auto_reboot as shown below
curl -c cjar -b cjar -k -H "Content-Type: application/json" -d "{"data": "yes"}" -X PUT https://XX.XX.XX.XX/org/openbmc/settings/host0/attr/auto_reboot
{
"data": null,
"message": "200 OK",
"status": "ok"
On HOST OS inject below checkstop using opal-utils as shown below
putscom -c 0x0 0x1d01080D 0x0A00000000000000
Petitboot console logs:

Please find dmesg, serial_port, petitboot, FFDC logs in the attachments
20170307040841664165_MyFFDCLogs.zip
dmesg_barreleye_logs.txt
journal_bmc_logs.txt
petitboot_logs.txt

OPAL Console issue on fsp platforms.

Below test steps causes the console messages are not coming on fsp ipmi console.

Connect ipmi sol console
Power OFF/ON the system
IPL messages will be coming to ipmi console
Trigger system dump from FSP
Wait for system dump to finish & immediately IPL starts automatically.
System IPL happening & boots to host OS, but all this IPL messages are not coming into active ipmi
console which was activated at the start of test.
Issue is coming with latest skiboot code.

Observed xscom write errors during an HMI Error injection tests.

Install a OpenPower Firestone system with firestone_update.pnor which is built from op-build master-next branch. HMI error injection tests results in xscom write errors.

Timer facility error injection test:
./putscom -c 00000008 14013281 0003080000000000;echo $?
22:38:48 [911178433037,3] XSCOM: write error gcid=0x0 pcb_addr=0x14013281 stat=0x3
22:38:48 [911178448677,6] IPMI: dropping non severe PEL event
22:38:48 [911178451611,3] XSCOM: Write failed, ret = -6
22:38:48 Error -5 writing XSCOM

HMI Malfunction alert(Core checkstop) error injection:
./putscom -c 00000008 1b013100 1000000000000000
22:38:48 [3048108888610,3] XSCOM: write error gcid=0x0 pcb_addr=0x1b013100 stat=0x3
22:38:48 [3048108904555,6] IPMI: dropping non severe PEL event
22:38:48 [3048108907750,3] XSCOM: Write failed, ret = -6
22:38:48 Error -5 writing XSCOM

Firmware version: PNOR level
System Firmware (ID 47)
Product Name : OpenPOWER Firmware
Product Version : open-power-firestone-23bdc73
Product Extra : buildroot-81b8d98
Product Extra : skiboot-5.3.1
Product Extra : hostboot-d9ee1a1-be2f697
Product Extra : linux-4.4.18-openpower1-5906f7a
Product Extra : petitboot-v1.2.2-7fc085b
Product Extra : firestone-xml-783df1f
Product Extra : occ-bb092e9
Product Extra : hostboot-binaries-7f593a3
Product Extra : capp-u

BMC FW level:
cat /proc/ractrends/Helper/FwInfo
FW_VERSION=2.13.98117
FW_DATE=Jun 15 2016
FW_BUILDTIME=11:26:40 CDT
FW_DESC=8335 SRC BUILD RR9 06152016
FW_PRODUCTID=1
FW_RELEASEID=RR9
FW_CODEBASEVERSION=2.X

Latest skiboot does not IPL in op-build

I merged this today.

open-power/op-build@a050b4c

We get this failure on habanero and palmetto when booting. Guess I'll revert it op-build.

[893214895,5] BT: Interface intialized, IO 0x00e4
[1354480573,4] SLW: HB-provided idle states property found
[1354583151,5] NVRAM: Size is 576 KB
[1594800654,3] NVRAM: Partition at offset 0xffff0 extends beyond end of nvram !
[1594947972,3] NVRAM: Re-initializing
[1596889455,5] Chip 0 Found PBCQ2 at /xscom@3fc0000000000/pbcq@2012800
[1597059022,5] Chip 0 Found PBCQ1 at /xscom@3fc0000000000/pbcq@2012400
[1598002147,5] Chip 0 Found PBCQ0 at /xscom@3fc0000000000/pbcq@2012000
[1599125400,3] PHB0: Base location code not found !
LOCK ERROR: Invalid recursive lock @0x30101a48 (state: 0x0000006000000001)
[1660968927,0] Aborting!
CPU 0060 Backtrace:
S: 0000000031b83870 R: 000000003001351c mambo_write+0xe94
S: 0000000031b83900 R: 00000000300172a0 mambo_write+0x4c18
S: 0000000031b83970 R: 0000000030015ea8 mambo_write+0x3820
S: 0000000031b839f0 R: 0000000030015f64 mambo_write+0x38dc
S: 0000000031b83a70 R: 0000000030025228 mambo_write+0x12ba0
S: 0000000031b83b50 R: 0000000030021da0 mambo_write+0xf718
S: 0000000031b83bc0 R: 000000003003b898 mambo_write+0x29210
S: 0000000031b83c90 R: 00000000300413c8 mambo_write+0x2ed40
S: 0000000031b83e30 R: 0000000030014214 mambo_write+0x1b8c
S: 0000000031b83f00 R: 0000000030002524 boot_entry+0x18c

OPAL flash API can't access ECC protected partitions (e.g. gard tool is not listing hardware gard entries)

Install a OpenPower habanero system with latest skiboot 5.4 rc2 and clone latest skiboot in host OS.
And try to list hardware gard entries. It is failing with below error.

skiboot/external/gard# ./gard list all
[ 516.062048471,3] ECC data length must be 8 byte aligned length:2d
[ 423.849745] mtd mtd0: opal_flash_async_op(op=0) failed (rc -6)
[ 423.849745] mtd mtd0: opal_flash_async_op(op=0) failed (rc -6)
Does not appear to be sane gard data
A libflash/libffs error has occurred 15

opal-gard list all
[ 330.123050527,3] ECC data length must be 8 byte aligned length:2d
[ 237.968901] mtd mtd0: opal_flash_async_op(op=0) failed (rc -6)
[ 237.968901] mtd mtd0: opal_flash_async_op(op=0) failed (rc -6)
Does not appear to be sane gard data
A libflash/libffs error has occurred 15

[ 47.065304451,5] SkiBoot skiboot-5.4.0-rc2 starting...

occ's are not initialized properly in fast-reboot path, for the disabled OCC's

On a fast-reboot enabled system if OCC's are disabled, then next reboot is not making up disabled OCC's

Disable OCC's by doing occ reset for more than 3 times
[root@localhost ~]# opal-prd occ reset
[root@localhost ~]# opal-prd occ reset
[root@localhost ~]# opal-prd occ reset
[root@localhost ~]# opal-prd occ reset
[root@localhost ~]# opal-prd occ reset
=feeling-luckyt ~]# nvram -p ibm,skiboot --update-config experimental-fast-reset
[root@localhost ~]# reboot
[ OK ] Started Show Plymouth Reboot Screen.

[root@localhost ~]# dmesg | grep -i powernv
[ 0.000000] Using PowerNV machine description
[ 0.750966] EEH: PowerNV platform initialized
[ 4.971226] powernv-rng: Registering arch random hook.
[ 6.938154] powernv-cpufreq: cpufreq pstate min -43 nominal -17 max 0
[ 6.954201] powernv-cpufreq: Pstate set to safe frequency
[ 6.968361] powernv-cpufreq: Frequency Control disabled from OS
[ 6.986228] powernv-cpufreq: PMSR = d5d5807fc8000000
[ 7.003352] powernv-cpufreq: CPU Frequency could be throttled
[ 7.135968] powernv_idle_driver registered
[ 7.136065] nx_compress_powernv: coprocessor found on chip 0, CT 3 CI 1
[ 19.451572] powernv_rng: Registered powernv hwrng.
[ 19.476582] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x000000, prod_id: 0x0000, dev_id: 0x00)
[root@localhost ~]# ipmitool sdr elist | grep -i occ
OCC Active | 08h | ok | 210.0 | Device Disabled

After fast-reboot, still OCC's are disabled that means there is no power management, user need to do a full IPL

OPAL spec, constrains on OPAL calls

opal-spec.txt should probably describe the expected machine state across an OPAL call a bit better, in that (from reading Linux kernel code and skiboot):

r1 is preserved, r12 is scratch, r13-r31 preserved
64-bit HV real mode
big-endian (this is already mentioned)
external interrupts disabled

Witherspoon: Unable to boot Ubuntu on w37

[ 9.021567] Unable to handle kernel paging request for data at address 0x00002260
[ 9.021567] Unable to handle kernel paging request for data at address 0x00002260
[ 9.022501] Faulting instruction address: 0xc0000000006c7770
[ 9.022501] Faulting instruction address: 0xc0000000006c7770
[ 9.023105] Oops: Kernel access of bad area, sig: 11 [#1]
[ 9.023105] Oops: Kernel access of bad area, sig: 11 [#1]
[ 9.023674] SMP NR_CPUS=2048
[ 9.023674] SMP NR_CPUS=2048
[ 9.023676] NUMA
[ 9.023676] NUMA
[ 9.023970] PowerNV
[ 9.023970] PowerNV
[ 9.024372] Modules linked in: ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd uio_pdrv_genirq uio vmx_crypto ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crc32c_vpmsum fb_sys_fops drm ahci libahci tg3
[ 9.024372] Modules linked in: ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd uio_pdrv_genirq uio vmx_crypto ip_tables x_tables autofs4 ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crc32c_vpmsum fb_sys_fops drm ahci libahci tg3
[ 9.027146] CPU: 15 PID: 354 Comm: kworker/u64:2 Not tainted 4.10.0-8-generic #10-Ubuntu
[ 9.027146] CPU: 15 PID: 354 Comm: kworker/u64:2 Not tainted 4.10.0-8-generic #10-Ubuntu
[ 9.027978] Workqueue: events_unbound flush_to_ldisc
[ 9.027978] Workqueue: events_unbound flush_to_ldisc
[ 9.028468] task: c0000016a7758c00 task.stack: c0000000fd084000
[ 9.028468] task: c0000016a7758c00 task.stack: c0000000fd084000
[ 9.029055] NIP: c0000000006c7770 LR: c0000000006c7758 CTR: c0000000006c84b0
[ 9.029055] NIP: c0000000006c7770 LR: c0000000006c7758 CTR: c0000000006c84b0
[ 9.029767] REGS: c0000000fd0878c0 TRAP: 0300 Not tainted (4.10.0-8-generic)
[ 9.029767] REGS: c0000000fd0878c0 TRAP: 0300 Not tainted (4.10.0-8-generic)
[ 9.030520] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>
[ 9.030520] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>
[ 9.030537] CR: 28002888 XER: 00000000
[ 9.030537] CR: 28002888 XER: 00000000
[ 9.031579] CFAR: c000000000b3e20c DAR: 0000000000002260 DSISR: 40000000 SOFTE: 1
[ 9.031579] GPR00: c0000000006c7758 c0000000fd087b40 c00000000143c900 0000000000000000
[ 9.031579] GPR04: c000000002ac8c20 c000000002ac8d20 0000000000000100 0000000000000001
[ 9.031579] GPR08: c0000016ae0ebcc0 0000000000000001 c00000000139a5a0 c0000016a7758ca8
[ 9.031579] GPR12: 0000000028002888 c00000000fb88700 c0000000000f6668 c0000016b4b7e3c0
[ 9.031579] GPR16: c0000016c90322d8 c0000016c9032090 c0000016c9032020 0000000000000001
[ 9.031579] GPR20: 0000000000000000 0000000000000000 c000000001335ce9 0000000100000000
[ 9.031579] GPR24: 0000000000000000 0000000000000000 c000000002ac8c20 c0000016b4f932a0
[ 9.031579] GPR28: c000000002ac8d20 0000000000000100 c0000016a8dca608 c0000016ae0ebc00
[ 9.031579] CFAR: c000000000b3e20c DAR: 0000000000002260 DSISR: 40000000 SOFTE: 1
[ 9.031579] GPR00: c0000000006c7758 c0000000fd087b40 c00000000143c900 0000000000000000
[ 9.031579] GPR04: c000000002ac8c20 c000000002ac8d20 0000000000000100 0000000000000001
[ 9.031579] GPR08: c0000016ae0ebcc0 0000000000000001 c00000000139a5a0 c0000016a7758ca8
[ 9.031579] GPR12: 0000000028002888 c00000000fb88700 c0000000000f6668 c0000016b4b7e3c0
[ 9.031579] GPR16: c0000016c90322d8 c0000016c9032090 c0000016c9032020 0000000000000001
[ 9.031579] GPR20: 0000000000000000 0000000000000000 c000000001335ce9 0000000100000000
[ 9.031579] GPR24: 0000000000000000 0000000000000000 c000000002ac8c20 c0000016b4f932a0
[ 9.031579] GPR28: c000000002ac8d20 0000000000000100 c0000016a8dca608 c0000016ae0ebc00
[ 9.038511] NIP [c0000000006c7770] n_tty_receive_buf_common+0xb0/0xdf0
[ 9.038511] NIP [c0000000006c7770] n_tty_receive_buf_common+0xb0/0xdf0
[ 9.039139] LR [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0
[ 9.039139] LR [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0
[ 9.039766] Call Trace:
[ 9.039766] Call Trace:
[ 9.040009] [c0000000fd087b40] [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0 (unreliable)
[ 9.040009] [c0000000fd087b40] [c0000000006c7758] n_tty_receive_buf_common+0x98/0xdf0 (unreliable)
[ 9.040868] [c0000000fd087c10] [c0000000006cc524] tty_ldisc_receive_buf+0x44/0xe0
[ 9.040868] [c0000000fd087c10] [c0000000006cc524] tty_ldisc_receive_buf+0x44/0xe0
[ 9.041595] [c0000000fd087c40] [c0000000006ccd9c] flush_to_ldisc+0x13c/0x160
[ 9.041595] [c0000000fd087c40] [c0000000006ccd9c] flush_to_ldisc+0x13c/0x160
[ 9.042265] [c0000000fd087c90] [c0000000000ed8c0] process_one_work+0x2b0/0x5a0
[ 9.042265] [c0000000fd087c90] [c0000000000ed8c0] process_one_work+0x2b0/0x5a0
[ 9.042955] [c0000000fd087d20] [c0000000000edc58] worker_thread+0xa8/0x650
[ 9.042955] [c0000000fd087d20] [c0000000000edc58] worker_thread+0xa8/0x650
[ 9.043625] [c0000000fd087dc0] [c0000000000f67b4] kthread+0x154/0x1a0
[ 9.043625] [c0000000fd087dc0] [c0000000000f67b4] kthread+0x154/0x1a0
[ 9.044245] [c0000000fd087e30] [c00000000000b4e8] ret_from_kernel_thread+0x5c/0x74
[ 9.044245] [c0000000fd087e30] [c00000000000b4e8] ret_from_kernel_thread+0x5c/0x74
[ 9.044964] Instruction dump:
[ 9.044964] Instruction dump:
[ 9.045281] eb3f0260 7c9a2378 7cbc2b78 7cdd3378 f8e10030 48476a55 60000000 3b000000
[ 9.045281] eb3f0260 7c9a2378 7cbc2b78 7cdd3378 f8e10030 48476a55 60000000 3b000000
[ 9.046128] 7af783e4 60000000 60000000 60420000 7c2004ac e8d90000 80ff0110
[ 9.046128] 7af783e4 60000000 60000000 60420000 7c2004ac e8d90000 80ff0110
[ 9.047044] ---[ end trace 6b3bf4b72485f95c ]---
[ 9.047044] ---[ end trace 6b3bf4b72485f95c ]---
[ 9.047485]
[ 9.047485]

I used to see this once in a while. But. on w37 it fails every IPL.

Failed to get chip id using getscom tool

getscom tool failed to identify the Chip ID on garrrison system, with the latest code

System Info:
bmc --> g68.aus.stglabs.ibm.com
lpar --> g68L.aus.stglabs.ibm.com
Build Level: 20151211n

from BMC:
cat /proc/ractrends/Helper/FwInfo
FW_VERSION=2.13.85625
FW_DATE=Dec 10 2015
FW_BUILDTIME=15:32:56 CDT
FW_DESC=8335-GTB SRC BUILD RR9 12102015
FW_PRODUCTID=1
FW_RELEASEID=RR9
FW_CODEBASEVERSION=2.X

tyan@g68L:~$ sudo /home/tyan/skiboot/external/xscom-utils/getscom -l

Chip ID	Rev	Chip type
80000015	DD2.0	Centaur memory buffer
80000014	DD2.0	Centaur memory buffer
80000005	DD2.0	Centaur memory buffer
80000004	DD2.0	Centaur memory buffer
00000001	DD1.0	Unknown ID 0xd3 <--- Failed to identify chip type
00000000	DD1.0	Unknown ID 0xd3 <--- Failed to identify chip type

skiboot fails to build on RHEL6.

[ HOSTCC ] extract-gcov.c
cc1: error: unrecognized command line option "-Wjump-misses-init"
cc1: error: unrecognized command line option
"-Wsuggest-attribute=const"
cc1: error: unrecognized command line option
"-Wsuggest-attribute=noreturn"
cc1: error: unrecognized command line option "-Wstack-usage=1024"

We get the following failure on RHEL6 when doing an op-build because of using compiler warning options that do not exist. The compiler options are fine for TARGET-CC but not HOST-CC. In op-build(buildroot), the original /usr/bin/gcc is used for HOST-CC while the cross-compiler is used for TARGET-CC.

ipmitool fru PNOR version info missing capp-ucode- version.

ipmi fru info for pnor version, missing capp-ucode version.

How to reproduce:
Build a habanero_update.pnor image using op-build master-next branch, Flash this image on OpenPower habanero machine.
Read ipmitool fru print 43 for PNOR version info.
ipmitool fru print 43
Product Name : OpenPOWER Firmware
Product Version : open-power-habanero-6ec4e33
Product Extra : buildroot-d78ccc1
Product Extra : skiboot-5.2.1
Product Extra : hostboot-e189edd-9824b9f
Product Extra : linux-4.4.8-openpower1-bd9161a
Product Extra : petitboot-v1.0.1-8f13d5f
Product Extra : habanero-xml-5a2a541-cb4e251
Product Extra : occ-19a3ebc
Product Extra : hostboot-binaries-7f593a3
Product Extra : c

Try reading PNOR VERSION partition using ipmitool.
ipmitool raw 0x3a 0x0b 0x56 0x45 0x52 0x53 0x49 0x4f 0x4e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 | xxd -r -p
open-power-habanero-6ec4e33
buildroot-d78ccc1
skiboot-5.2.1
hostboot-e189edd-9824b9f
linux-4.4.8-openpower1-bd9161a
petitboot-v1.0.1-8f13d5f
habanero-xml-5a2a541-cb4e251
occ-19a3ebc
hostboot-binaries-7f593a3
capp-ucode-105cb8f

We can observe from above two outputs, ipmitool fru print 43 is missing app-ucode-105cb8f which is a version of capp-ucode.

contact: [email protected]

Failure to inject system checkstop error on all cores

System returned an error when trying to inject a system checkstop error on some of the cores.
Note: Not all cores had this issue

System info:
bmc --> habcap10.aus.stglabs.ibm.com
lpar ---> habcap10p1.aus.stglabs.ibm.com

from BMC:
cat /proc/ractrends/Helper/FwInfo
FW_VERSION=2.16.85627.65366
FW_DATE=Dec 7 2015
FW_BUILDTIME=13:40:23 CDT
FW_DESC=8348 P2 SRC RR9 12072015
FW_PRODUCTID=1
FW_RELEASEID=RR9
FW_CODEBASEVERSION=2.X

khansa@habcap11p1:~$ ipmitool -H habcap10 -I lanplus -U ADMIN -P admin fru print 43
Product Name : OpenPOWER Firmware
Product Version : IBM-habanero-ibm-OP8_v1.7_1.17
Product Extra : hostboot-bc98d0b-5463ef4
Product Extra : occ-0362706-9e016d2
Product Extra : skiboot-5.1.9-ada75ff
Product Extra : hostboot-binaries-43d5a59
Product Extra : habanero-xml-a71550e-85cdcb7
Product Extra : capp-ucode-105cb8f

Following is a list of step that were executed on the partition and the output received.
tyan@habcap10p1:~$ cat /sys/firmware/opal/msglog | grep -i chip | grep -i core
[7261039858,7] OCC: Chip 0 Core 1 PPMSR d1d1ca0008000000
[7261557077,7] OCC: Chip 0 Core 4 PPMSR dadaca0008000000
[7262073389,7] OCC: Chip 0 Core 5 PPMSR e3e3ca0008000000
[7262589628,7] OCC: Chip 0 Core 6 PPMSR ebebca0008000000
[7263107075,7] OCC: Chip 0 Core a PPMSR f0f0ca0008000000
[7263622298,7] OCC: Chip 0 Core c PPMSR f0f0ca0008000000
[7264137165,7] OCC: Chip 0 Core d PPMSR f0f0ca0008000000
[7264651994,7] OCC: Chip 0 Core e PPMSR f0f0ca0008000000

tyan@habcap10p1:~$ sudo /home/tyan/skiboot/external/xscom-utils/getscom -l

Chip ID	Rev	Chip type
80000005	DD2.0	Centaur memory buffer
80000004	DD2.0	Centaur memory buffer
80000001	DD2.0	Centaur memory buffer
80000000	DD2.0	Centaur memory buffer
00000000	DD2.0	P8 (Venice) processor

tyan@habcap10p1:$ sudo /home/tyan/skiboot/external/xscom-utils//putscom -c 0x00000000 0x1e012800 0x0100000000000000 <---------- Checkstop detected at core # e
Error -5 writing XSCOM
tyan@habcap10p1:$ sudo /home/tyan/skiboot/external/xscom-utils//putscom -c 0x00000000 0x1d012800 0x0100000000000000 <---------- Checkstop not detected at core # d
Error -5 writing XSCOM
tyan@habcap10p1:~$ sudo /home/tyan/skiboot/external/xscom-utils//putscom -c 0x00000000 0x1c012800 0x0100000000000000 <---------- Checkstop detected at core # c

Switching from golden side pnor boot to primary side pnor boot is not happening for habanero machine.

Problem statement:
Install a habanero system with OpenPower Firmware, and do a golden side pnor boot. After further reboots system still booting always from golden side pnor firmware, and it is not booting from primary side pnor firmware.

How to Reproduce:
1.Install a Habanero system with latest OpenPower Firmware.

ipmitool sensor list | grep -i "boot count"
Boot Count | 0x0 | discrete | 0x0280| na | na | na | na | na | na
initially boot count =0x02

Do a Power ON followed by immediate power off(To make sure boot fail early)
check for boot count sensor value, it should be decremented by 1
ipmitool sensor list | grep -i "boot count"
Boot Count | 0x0 | discrete | 0x0180| na | na | na | na | na | na
Do a Power ON followed by immediate power off for 2nd time(To make sure boot fail early)
check for boot count sensor value, it should be decremented by 1
ipmitool sensor list | grep -i "boot count"
Boot Count | 0x0 | discrete | 0x0080| na | na | na | na | na | na
Do a Power ON Operation to boot the system from golden side PNOR(Because boot count =0x00)

ipmitool sensor list | grep -i golden
BIOS Golden Side | 0x0 | discrete | 0x0180| na | na | na | na | na | na
BMC Golden Side | 0x0 | discrete | 0x0080| na | na | na | na | na | na

cd /sys/firmware/devicetree/base/xscom@3fc0000000000/isa@b0020/pnor@fc000000
lsprop *-tocs
active-image-tocs
02000000 03ff8000
alternate-image-tocs
00000000 01ff8000
golden-image-tocs
02000000 03ff8000
Here we can observe at this stage system booted from golden side

Reboot the sytem again.
reboot
[ OK ] Started Show Plymouth Reboot Screen.
[ OK ] Stopped Virtualization daemon.
Stopping D-Bus System Message Bus...

After completion of reboot check again system boot side still it is in golden side of pnor.
cd /sys/firmware/devicetree/base/xscom@3fc0000000000/isa@b0020/pnor@fc000000
lsprop *-tocs
active-image-tocs
02000000 03ff8000
alternate-image-tocs
00000000 01ff8000
golden-image-tocs
02000000 03ff8000

ipmitool sensor list | grep -i golden
BIOS Golden Side | 0x0 | discrete | 0x0180| na | na | na | na | na | na
BMC Golden Side | 0x0 | discrete | 0x0080| na | na | na | na | na | na

Further subsequent reboots also system is not booting from primary side of pnor, and it is always booting from golden side of pnor.

How to switch from golden side pnor to primary side pnor manually:

On BMC Busy box execute below command.
/etc/init.d/boot_into_primary
Do a ipmi hard power reset to boot the system into primary.
ipmitool power reset.

Firmware levels:
When system is in primary side:
open-power-habanero-6ec4e33
buildroot-d78ccc1
skiboot-5.2.1
hostboot-e189edd-9824b9f
linux-4.4.8-openpower1-bd9161a
petitboot-v1.0.1-8f13d5f
habanero-xml-5a2a541-cb4e251
occ-19a3ebc
hostboot-binaries-7f593a3
capp-ucode-105cb8f

When system is in golden side:
Product Name : OpenPOWER Firmware
Product Version : TN71-BP012-810.1611.20160406a
Product Extra : hostboot-bc98d0b-3f66050
Product Extra : occ-0362706-805fe5a
Product Extra : skiboot-5.1.13
Product Extra : hostboot-binaries-43d5a59
Product Extra : habanero-xml-5a2a541-228a675
Product Extra : capp-ucode-105cb8f

Support for AST2500 flash registers needed.

We discovered that libflash / pflash do not currently support the new register layout for the AST2500. Is this work planned to be done in the near future? We have systems coming on-line soon that are going to require this support and we need to integrate it back into openbmc.

Please see openbmc/openbmc#538 and openbmc/openbmc#541 for additional background.

Boot not stopping at petitboot as requested

See issue openbmc/openbmc#1150

OpenBMC team analyzed the IPMI data during boot and did not see OPAL firmware requesting the boot flags on a P9 Witherspoon system. This would most likely be why the system always tries to boot the OS.

This function seems to work fine on barreleye, and I assume the code is mostly common? We're just bringing up the host IPMI interface on P9 so lots of opportunities for bugs on OpenBMC side here. If nothing obvious on OPAL side then we'll continue looking on OBMC side.

We're running latest op-build code from master-next as of this week.

	buildroot-6b9fd80
	skiboot-8c51fda
	hostboot-6782606
	linux-4.9.8-4863d7c
	petitboot-v1.4.1-fe60185
	witherspoon-xml-3fd670a
	occ-4141b5f
	hostboot-binaries-541a2bd
	capp-ucode-1bb7503

max args to an opal call

opal_entry (and opal-spec.txt) claim 9 arguments may be passed in r3..r11, yet the OpenPower ABI mentions (2.2.1.1 Register Roles) that r11 is not used for parameter passing, and again in 2.2.3 (Parameter Passing in Registers) that only 8 registers are available, with the rest spilling to stack.

A simple test confirms:

    2001021c:   09 00 20 39     li      r9,9
    20010220:   60 00 21 f9     std     r9,96(r1)
    20010224:   0a 00 20 39     li      r9,10
    20010228:   68 00 21 f9     std     r9,104(r1)
    2001022c:   0b 00 20 39     li      r9,11
    20010230:   70 00 21 f9     std     r9,112(r1)
    20010234:   0c 00 20 39     li      r9,12
    20010238:   78 00 21 f9     std     r9,120(r1)
    2001023c:   01 00 60 38     li      r3,1
    20010240:   02 00 80 38     li      r4,2
    20010244:   03 00 a0 38     li      r5,3
    20010248:   04 00 c0 38     li      r6,4
    2001024c:   05 00 e0 38     li      r7,5
    20010250:   06 00 00 39     li      r8,6
    20010254:   07 00 20 39     li      r9,7
    20010258:   08 00 40 39     li      r10,8
    2001025c:   9d fe ff 4b     bl      200100f8 <foo>

If OPAL really does support 9 arguments, the opal_entry logic should be reflected (fetching arg 9 from client stack, yuck)... To me it seems mostly a typo (i.e. OPAL really supports only 8 args, not counting the token in r0), but then r11 manipulation for OPAL_TRACE_ENTRY should be avoided.

Use or get rid of systemd socket

Looking at the opal-prd code, I noticed the systemd-created socket is not being used. The code just handles its own socket and ignores systemd's one. There are 2 ways to solve that:

don't use systemd sockets. opal-prd already does all the socket handling. That means the file opal-prd.socket can be removed and opal-prd.service depency on it, dropped.
ask systemd to hand over the socket it created with opal-prd.socket. If there is no need to support non-systemd systems, the whole socket handling part can be removed from the code and the function 'sd_listen_fds' from systemd can be used to retrieve the socket's fd. A code snippet for that can be seen in [1]. In case there is any interest in this, I can work on a patch.

[1] http://0pointer.de/blog/projects/socket-activation.html

support skiboot as a git submodule: fix version detection

Without this you will get

andreiw-lnx:~/src/ppc64le_hello/skiboot/ make
    [CC]  version.o
version.c:1:2: error: #error You need to set SKIBOOT_VERSION environment variable
 #error You need to set SKIBOOT_VERSION environment variable
  ^
make: *** [version.o] Error 1
andreiw-lnx:~/src/ppc64le_hello/skiboot/

Here's the patch:

From 84d72666ec130a4724e8765e7f1b27a8d6101c06 Mon Sep 17 00:00:00 2001
From: Andrei Warkentin <[email protected]>
Date: Tue, 12 May 2015 06:47:54 -0400
Subject: [PATCH] skiboot: detect version correctly as a git submodule

When checked-out as a submodule, .git is a file, not a dir.

Signed-off-by: Andrei Warkentin <[email protected]>

---
 make_version.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/make_version.sh b/make_version.sh
index 1dfbe4c..860c124 100755
--- a/make_version.sh
+++ b/make_version.sh
@@ -1,6 +1,6 @@
 #!/bin/bash

-if test -d .git;
+if test -e .git;
 then
    version=`git describe --exact-match 2>/dev/null`
    if [ -z "$version" ];
-- 
1.9.1

pflash support for 4K erase block on mx66l51235f

Attempting to clear the HBEL partition on Zaius via the BMC fails complaining about the erase block size mismatch:

root@zaius:~# pflash -f -c -P HBEL
About to erase and set ECC bits in region 0x000a0000 to 0x000c4000
About to erase 0x000a0000..0x000c4000 !
Erasing...
[============================================ ] 88%blocklevel_erase: len (0x4096) is not erase block (0x00010000) aligned
Error 4 erasing 0x000c0000

This chip does support 4KB erase blocks but I'm not sure if the pflash support for it has been tested yet.

assertion in mem_region_release_unused-gcov test

Running skiboot-5.2.4 (65e436a), built withgcc (Ubuntu 5.4.0-6ubuntu1) 5.4.0 20160609:

$ gdb core/test/run-mem_region_release_unused-gcov
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Reading symbols from core/test/run-mem_region_release_unused-gcov...done.
(gdb) r
Starting program: /home/joel/dev/skiboot/core/test/run-mem_region_release_unused-gcov 
MEM: parsing reserved memory from reserved-names/-ranges properties
Releasing unused memory:
    ibm,firmware-heap: 0/4096 used
    ibm,firmware-allocs-memory@7ffff7ecc010: 1040/1048576 used
run-mem_region_release_unused-gcov: core/test/run-mem_region_release_unused.c:166: main: Assertion `r->start == other->start + other->len' failed.

Program received signal SIGABRT, Aborted.
0x00007ffff7a43418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0  0x00007ffff7a43418 in __GI_raise (sig=sig@entry=6)
    at ../sysdeps/unix/sysv/linux/raise.c:54
        resultvar = 0
        pid = 10725
        selftid = 10725
#1  0x00007ffff7a4501a in __GI_abort () at abort.c:89
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0x4, sa_sigaction = 0x4}, sa_mask = {
            __val = {93824992245216, 140737488346800, 140737488346192, 0, 140737354092544, 
              93824992298416, 166, 93824992299189, 0, 0, 140737348442812, 140737349540392, 
              140737349554032, 93824994436000, 140737349540392, 93824992298416}}, 
          sa_flags = -134262784, sa_restorer = 0x5555555645b0}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2  0x00007ffff7a3bbd7 in __assert_fail_base (fmt=<optimised out>, 
    assertion=assertion@entry=0x5555555645b0 "r->start == other->start + other->len", 
    file=file@entry=0x555555564460 "core/test/run-mem_region_release_unused.c", 
    line=line@entry=166, 
    function=function@entry=0x5555555648b5 <__PRETTY_FUNCTION__.5091> "main") at assert.c:92
        str = 0x55555576e9c0 "run-mem_region_release_unused-gcov: core/test/run-mem_region_release_unused.c:166: main: Assertion `r->start == other->start + other->len' failed.\n"
        total = 4096
#3  0x00007ffff7a3bc82 in __GI___assert_fail (
    assertion=0x5555555645b0 "r->start == other->start + other->len", 
    file=0x555555564460 "core/test/run-mem_region_release_unused.c", line=166, 
    function=0x5555555648b5 <__PRETTY_FUNCTION__.5091> "main") at assert.c:101
No locals.
#4  0x00005555555612c3 in main () at core/test/run-mem_region_release_unused.c:166
        i = 8
        r = 0x55555576e340
        other = 0x55555576e280
        other_mem = 0x7ffff7ecc010
        last = 0x7fffffffdeb0 "\001"
        __PRETTY_FUNCTION__ = "main"

No failure report during the RAS- VPD not updated in RAS function test.

DIMMs during IPL( RAS: Pulling out one dimm at IPL time brings all of 8 dimms under CPU2 offline #76 ).
Summary of issues :

Powered on the system with 2 Bad drams.
training failed and issued reconfig loop.
memdiag failed and created logs saying both spare and chip mark used.

| PRD Signature : 0x000D0002 0xFFFF0043 |

Signature Description : mba(n0p1c0) () RDR: Both spare and chip mark used

Memdiag issues reconfig loop and failed again at 12.4 mss_eff_config complaining about DIMM plugging rules
| Created by : hwpf |
| HwpReturnCode : RC_MSS_EFF_GROUPING_UNABLE_TO_GROUP_MCS |
| HWP Error description : mss_eff_grouping found an MCS that could not be gr|
| : ouped. This is a memory plugging error. Refer to m|
| : emory plugging rules. The attached Memory Buffer C|

: hip is deconfigured as a result

User Defined Data

: hip is deconfigured as a result
User Defined Data

This issues reconfig loop and taking out total of 8 DIMMs
5. powered off the system, removed tape on the DIMM and moved to new slot . Removed gard and powered on the system again.
There is no training fail and no memdiag fail. Its a clean IPL, which proves VPD is not updated
--- Procedure and output files --------------------
I added all results for taped 8DQs and followed this procedure.

Power off
populated with all good DIMM.
Clear vpd.
Power on
Power off
test mode
Power on --> 1'st IPL log : file name --> 1stIPL
Power off
Taped 8DQ pin on the DIMM
Power on --> 2'nd IPL : file name --> 2ndIPL_taped_8DQs
get sel list --> file name --> taped_8DQs_g_sel_list
get eSEL log --> file name --> taped_8DQs_eSEL_log_p05_NBA0p0.txt
13.Power off the system
Downlaod two logs before power off to Ubuntu hard disk
Remove 8 DQ TAPE on the DIMM
Move next slot
Power on and save tee istep -> file name --> 3IPL_removed_8DQ_p5_NBA0_p1
Sel list and copy output -> file name --> removed_8DQ_sel_list.txt
Run esel .pl and get log -> file name --> removed_8DQ_eSEL_log.txt

Also Added 2 log files gard list, gard show data.

1stIPL.txt
2ndIPL_taped_8DQs.txt
3IPL_removed_8DQ_p5_NBA0_p1.txt
removed_8DQ_eSEL_log.txt
removed_8DQ_sel_list.txt
syslog1_taped_8DQs.txt
taped_8DQs_eSEL_log_p05_NBA0p0.txt
taped_8DQs_g_sel_list.txt
msglog1_taped_8DQs.txt
syslog1_taped_8DQs.txt

FWTS Device-tree Errors

Executed FWTS Tests on Ubuntu 16.10 with latest Skiboot Level. Below are the errors it got while executing.

mem_info: OPAL MEM Info

Test 1 of 1: OPAL MEM Info

STARTING checks of MEM devices

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM0" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM0".

DTPrintableProperty "part-number" with a string value of "HMT42GR7BFR4A-PB" passed
PASSED: Test 1, DTPrintableProperty "part-number" passed
PASSED: Test 1, OPAL MEM Info Property of "part-number" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,0" is
"HMT42GR7BFR4A-PB".

FAILED [LOW] DTPrintablePropertyInvalid: Test 1, property "serial-number"
contains unprintable characters
PASSED: Test 1, OPAL MEM Info Property of "serial-number" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,0" is "��".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "status" with a string value of "okay" passed
PASSED: Test 1, DTPrintableProperty "status" passed
PASSED: Test 1, OPAL MEM Info Property of "status" for "/sys/firmware/devicetree
/base/memory-buffer@3e00000000000/mba@0/dimm@0,0" is "okay".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM1" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM1".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM2" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM2".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM3" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM3".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM4" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM4".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM5" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM5".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM6" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM6".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM7" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM7".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM8" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM8".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM9" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM9".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM10" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM10".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM11" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM11".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM12" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM12".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM13" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM13".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM14" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM14".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM15" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM15".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM16" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM16".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM17" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM17".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM18" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM18".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM19" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM19".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM20" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM20".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM21" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM21".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM22" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM22".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM23" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM23".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM24" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM24".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM25" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM25".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM26" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM26".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM27" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM27".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM28" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,0" is
"Physical:/Sys0/Node0/DIMM28".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM29" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" is
"Physical:/Sys0/Node0/DIMM29".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM30" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,0" is
"Physical:/Sys0/Node0/DIMM30".

PASSED: Test 1, OPAL MEM Info Property of "manufacturer-id" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,0" is "0x0000AD80".

DTPrintableProperty "ibm,slot-location-code" with a string value of "Physical:/Sys0/Node0/DIMM31" passed
PASSED: Test 1, DTPrintableProperty "ibm,slot-location-code" passed
PASSED: Test 1, OPAL MEM Info Property of "ibm,slot-location-code" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" is
"Physical:/Sys0/Node0/DIMM31".

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "part-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "serial-number" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "manufacturer-id" for "/sys
/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not
able to be retrieved. Check the installation for the MEM device config for
missing nodes in the device tree if you expect MEM devices.

FAILED [CRITICAL] OPAL MEM Info: Test 1, Property of "status" for "/sys/firmware
/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not able to be
retrieved. Check the installation for the MEM device config for missing nodes in
the device tree if you expect MEM devices.

ENDING checks of MEM devices

================================================================================
160 passed, 80 failed, 0 warning, 0 aborted, 0 skipped, 0 info only.

Test Failure Summary

Critical failures: 64
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e00000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e02000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e08000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@0/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@0,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "part-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "serial-number" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "manufacturer-id" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.
mem_info: Property of "status" for "/sys/firmware/devicetree/base/memory-buffer@3e0a000000000/mba@1/dimm@1,1" was not able to be retrieved. Check the installation for the MEM device config for missing nodes in the device tree if you expect MEM devices.

High failures: NONE

Medium failures: 1
dt_base: dtc reports warnings from device tree:Warning (reg_format): "reg" property in /ibm,opal/flash@0 has invalid length (8 bytes) (#address-cells == 0, #size-cells == 0)

Low failures: 1
mem_info: property "serial-number" contains unprintable characters

Other failures: NONE

Test |Pass |Fail |Abort|Warn |Skip |Info |
---------------+-----+-----+-----+-----+-----+-----+
bmc_info | 1| | | | | |
cpu_info | 10| | | | | |
cpufreq | 5| | | | 2| |
dt_base | 2| 1| | | | |
dt_sysinfo | 15| | | | | |
klog | | | | | | |
maxreadreq | 1| | | | | |
mem_info | 160| 80| | | | |
mtd_info | 1| | | | | |
olog | 1| | | | | |
oops | 2| | | | | |
prd_info | 1| | | | | |
version | | | | | | 3|
---------------+-----+-----+-----+-----+-----+-----+
Total: | 199| 81| 0| 0| 2| 3|
---------------+-----+-----+-----+-----+-----+-----+

How to execute:
https://github.com/open-power/op-test-framework/blob/master/testcases/fwts_execution.sh

There are two types of errors it is throwing:

DT Unprintable errors
Not able to retrieve some memory buffer and dimm properties.

PRD for POWER9

Fix OPAL_REINIT_CPUS with HILE_LE on Mambo systemsim

PVR_VERS_MAJ(mfspr(SPR_PVR)) for Mambo systemsim with processor/type P8
has major version 1, yet core/cpu.c sets hile_supported is set for version 2.

However, HID0.HILE does work correctly in P8 systemsim. I've verified that setting the bit causes exception code with MSR.HV=1 to be treated as little-endian. Thus, the following patch introduces another chip quirk (QUIRK_HAVE_HILE).

Before:

[19244603,3] OPAL: Trying a CPU re-init with flags: 0x2
[19250136,3] SLW: Not found on chip 0
[19257911,3] ELOG: Error getting buffer to log error

(and LE exception handlers don't work)

After:

[19244603,3] OPAL: Trying a CPU re-init with flags: 0x2

(and LE exception handlers do work)

Patch:

From 3996b2f40efadfd53d9bdf9a77638ed36aaed40b Mon Sep 17 00:00:00 2001
From: Andrei Warkentin <[email protected]>
Date: Sun, 17 May 2015 01:49:53 -0400
Subject: [PATCH] OPAL: enable opal_reinit_cpus(OPAL_REINIT_CPUS_HILE_LE) to
 work on Mambo systemsim

PVR_VERS_MAJ(mfspr(SPR_PVR)) for Mambo systemsim with processor/type P8
has major version 1, however HID0.HILE does seem to work correctly,
so add a chip quirk for Mambo.

Signed-off-by: Andrei Warkentin <[email protected]>

---
 core/chip.c    | 2 +-
 core/cpu.c     | 2 +-
 include/chip.h | 1 +
 3 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/core/chip.c b/core/chip.c
index 2ba7b6e..09ea825 100644
--- a/core/chip.c
+++ b/core/chip.c
@@ -71,7 +71,7 @@ void init_chips(void)
    if (dt_find_by_path(dt_root, "/mambo")) {
        proc_chip_quirks |= QUIRK_NO_CHIPTOD | QUIRK_MAMBO_CALLOUTS
            | QUIRK_NO_F000F | QUIRK_NO_PBA | QUIRK_NO_OCC_IRQ
-           | QUIRK_DISABLE_NAP;
+           | QUIRK_DISABLE_NAP | QUIRK_HAVE_HILE;
        prlog(PR_NOTICE, "CHIP: Detected Mambo simulator\n");
    }
    if (dt_node_is_compatible(dt_root, "qemu,powernv")) {
diff --git a/core/cpu.c b/core/cpu.c
index 4775883..670d7e9 100644
--- a/core/cpu.c
+++ b/core/cpu.c
@@ -742,7 +742,7 @@ static int64_t opal_reinit_cpus(uint64_t flags)
     * use the HID bit. We use the PVR (we could use the EC level in
     * the chip but the PVR is more readily available).
     */
-   if (hile_supported &&
+   if ((hile_supported || chip_quirk(QUIRK_HAVE_HILE)) &&
        (flags & (OPAL_REINIT_CPUS_HILE_BE | OPAL_REINIT_CPUS_HILE_LE))) {
        bool hile = !!(flags & OPAL_REINIT_CPUS_HILE_LE);

diff --git a/include/chip.h b/include/chip.h
index 0547902..2288d29 100644
--- a/include/chip.h
+++ b/include/chip.h
@@ -98,6 +98,7 @@ enum proc_chip_quirks {
    QUIRK_NO_PBA        = 0x00000008,
    QUIRK_NO_OCC_IRQ        = 0x00000010,
    QUIRK_DISABLE_NAP   = 0x00000020,
+   QUIRK_HAVE_HILE     = 0x00000040,
 } proc_chip_quirks;

 static inline bool chip_quirk(unsigned int q)
-- 
1.9.1

pflash build has a parallel build race condition.

| NOTE: make -j 32 CROSS_COMPILE=arm-openbmc-linux-gnueabi- SKIBOOT_VERSION=5.2.4 PFLASH_VERSION=5.2.4 V=1 -C external/pflash all LINKAGE=dynamic
| make: Entering directory `/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/work/armv5e-openbmc-linux-gnueabi/pflash/5.2.4-r0/git/external/pflash'
| ln -sf ../../libflash ./libflash
| ln -sf ../../ccan ./ccan
| ln -sf ../common ./common
| arm-openbmc-linux-gnueabi-gcc  -march=armv5e -marm --sysroot=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/barreleye  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/work/armv5e-openbmc-linux-gnueabi/pflash/5.2.4-r0=/usr/src/debug/pflash/5.2.4-r0 -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/barreleye=  -O2 -Wall -I. -c pflash.c -o pflash.o
| arm-openbmc-linux-gnueabi-gcc  -march=armv5e -marm --sysroot=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/barreleye  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/work/armv5e-openbmc-linux-gnueabi/pflash/5.2.4-r0=/usr/src/debug/pflash/5.2.4-r0 -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/tmp/openbmc.612a6908196e60ee1251a072ba621e167614170f.66UDBxA3/build/tmp/sysroots/barreleye=  -O2 -Wall -I. -c progress.c -o progress.o
| make: *** No rule to make target `../shared/libflash.so.skiboot-5.2.4', needed by `pflash'.  Stop.
| make: *** Waiting for unfinished jobs....

Sometimes we are failing with this.

OS failed to boot after injecting L2 Directory Read UE system checkstop through OS [barreleye]

Issue:

OS failed to boot after injecting L2 Directory Read UE system checkstop through OS

Expectation:

After error injection power off and on HOST.
OS should boot and gard records should be created

Procedure:

Disable auto_reboot setting
Disable cpu state through OS as shown below

sudo sh -c 'for i in /sys/devices/system/cpu/cpu*/cpuidle/state1/disable; do echo 1 > $i; done'
sudo sh -c 'for i in /sys/devices/system/cpu/cpu*/cpuidle/state2/disable; do echo 1 > $i; done'

Inject L2 Directory Read UE System Checkstop through OS as shown below

   putscom -c 0x00000000 0x11012800 0x0100000000000000

Check if HOST has reached quiesced state
Power off & on the HOST
check if OS is booted and gard records are created

System Info:

cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="v1.99.3-68"
VERSION_ID="v1.99.3-68-g35f91b9"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) v1.99.3-68"
BUILD_ID="v1.99.3"

Obmc console log info:

~# putscom -c 0x00000000 0x11012800 0x0100000000000000
  3.80115|ISTEP  6. 3
  4.17419|ISTEP  6. 4
  4.17507|ISTEP  6. 5
  9.39173|HWAS|PRESENT> DIMM[03]=A0A0A0A0A0A0A0A0
  9.39174|HWAS|PRESENT> Membuf[04]=CCCC000000000000
  9.39174|HWAS|PRESENT> Proc[05]=C000000000000000
  9.57253|ISTEP  6. 6
 10.68340|================================================
 10.68340|Error reported by unknown (0xE500)
 10.68340|  <none>
 10.68341|  ModuleId   0x0b unknown
 10.68341|  ReasonCode 0xe504 unknown
 10.68341|  UserData1  unknown : 0x0006000000000101
 10.68342|  UserData2  unknown : 0xe89b000700000000
 10.68342|User Data Section 0, type UD
 10.68342|  Subsection type 0x04
 10.68343|  ComponentId errl (0x0100)
 10.68343|User Data Section 1, type UD
 10.68343|  Subsection type 0x06
 10.68344|  ComponentId errl (0x0100)
 10.68344|  CALLOUT
 10.68344|  HW CALLOUT
 10.68344|  Reporting CPU ID: 12
 10.68345|  Called out entity:
 10.68345|User Data Section 2, type UD
 10.68345|  Subsection type 0x33
 10.68346|  ComponentId unknown (0xe500)
 10.68346|User Data Section 3, type UD
 10.68346|  Subsection type 0x01
 10.68347|  ComponentId unknown (0xe500)
 10.68347|  STRING
 10.68347|
 10.68347|User Data Section 4, type UD
 10.68348|  Subsection type 0x15
 10.68348|  ComponentId hb-trace (0x3100)
 10.68348|User Data Section 5, type UD
 10.68349|  Subsection type 0x01
 10.68349|  ComponentId unknown (0xe500)
 10.68349|  STRING
 10.68349|
 10.68350|User Data Section 6, type UD
 10.68350|  Subsection type 0x03
 10.68350|  ComponentId errl (0x0100)
 10.68350|User Data Section 7, type UD
 10.68351|  Subsection type 0x01
 10.68351|  ComponentId errl (0x0100)
 10.68351|  STRING
 10.68352|  Hostboot Build ID: hostboot-fe5c556/hbicore.bin
 10.68352|User Data Section 8, type UD
 10.68352|  Subsection type 0x04
 10.68352|  ComponentId errl (0x0100)
 10.68353|================================================
 31.74248|System Shutting Down To Perform Reconfiguration
 31.74249|IPMI: Initiate power cycle
 31.74340|Stopping istep dispatcher
 47.37376|IPMI: shutdown complete

Find the attached journal, dmesg, serial port, FFDC logs
barreleye_serial_port_logs.txt
20170313064435575811_MyFFDCLogs.zip
barreleye_dmseg.txt
barreleye_journal.txt

PCI Hotplug Support

Does Skiboot/Opal support hotplug of PCIe cards?

With latest skiboot code on a firenze system failed to boot during p8_i2c_init.

Not sure what is exactly the cause for this failure, But tried same skiboot lid one time it is worked and later on boot is aborting in skiboot code.
[ 83.344371236,5] SkiBoot skiboot-5.3.2-191-g69a9337 starting...
[ 83.344378129,5] initial console log level: memory 7, driver 5
[ 83.344381077,6] CPU: P8 generation processor(max 8 threads/core)
[ 83.344383798,7] CPU: Boot CPU PIR is 0x0870 PVR is 0x004b0201
[ 83.344386757,7] CPU: Initial max PIR set to 0x1fff
[ 83.345046793,5] OPAL table: 0x300b6e40 .. 0x300b7310, branch table: 0x30002000
[ 83.345053589,7] Parsing HDAT...
[ 83.345055592,5] SPIRA-S found.
[ 83.345061239,6] Got PCIA !
[ 83.345064476,6] CORE[0]: HW_PROC_ID=2 PROC_CHIP_ID=0 EC=0x21 OK
[ 83.345068323,6] CORE[0]: PIR=48 RES=48 OK (8 threads)
[ 83.345071816,6] Cache: I=32 D=64/512/8192/0
[ 83.345124160,6] CORE[1]: HW_PROC_ID=3 PROC_CHIP_ID=0 EC=0x21 OK
[ 83.345127666,6] CORE[1]: PIR=96 RES=96 OK (8 threads)
[ 83.345130847,6] Cache: I=32 D=64/512/8192/0
[ 83.345183008,6] CORE[2]: HW_PROC_ID=4 PROC_CHIP_ID=0 EC=0x21 OK
[ 83.345186506,6] CORE[2]: PIR=104 RES=104 OK (8 threads)
[ 83.345189800,6] Cache: I=32 D=64/512/8192/0
[ 83.345243971,6] CORE[3]: HW_PROC_ID=5 PROC_CHIP_ID=0 EC=0x21 OK
[ 83.345247410,6] CORE[3]: PIR=112 RES=112 OK (8 threads)
[ 83.345250727,6] Cache: I=32 D=64/512/8192/0
[ 83.345306459,6] CORE[4]: HW_PROC_ID=6 PROC_CHIP_ID=1 EC=0x21 OK
[ 83.345309943,6] CORE[4]: PIR=160 RES=160 OK (8 threads)
[ 83.345313210,6] Cache: I=32 D=64/512/8192/0
[ 83.345370978,6] CORE[5]: HW_PROC_ID=8 PROC_CHIP_ID=1 EC=0x21 OK
[ 83.345374363,6] CORE[5]: PIR=176 RES=176 OK (8 threads)
[ 83.345377532,6] Cache: I=32 D=64/512/8192/0
[ 83.345437230,6] CORE[6]: HW_PROC_ID=9 PROC_CHIP_ID=1 EC=0x21 OK
[ 83.345440672,6] CORE[6]: PIR=224 RES=224 OK (8 threads)
[ 83.345443952,6] Cache: I=32 D=64/512/8192/0
[ 83.345506142,6] CORE[7]: HW_PROC_ID=11 PROC_CHIP_ID=1 EC=0x21 OK
[ 83.345509699,6] CORE[7]: PIR=240 RES=240 OK (8 threads)
[ 83.345512998,6] Cache: I=32 D=64/512/8192/0
[ 83.345577243,6] CORE[8]: HW_PROC_ID=12 PROC_CHIP_ID=2 EC=0x21 OK
[ 83.345580866,6] CORE[8]: PIR=2080 RES=2080 OK (8 threads)
[ 83.345584245,6] Cache: I=32 D=64/512/8192/0
[ 83.345650462,6] CORE[9]: HW_PROC_ID=13 PROC_CHIP_ID=2 EC=0x21 OK
[ 83.345653998,6] CORE[9]: PIR=2088 RES=2088 OK (8 threads)
[ 83.345657241,6] Cache: I=32 D=64/512/8192/0
[ 83.345725430,6] CORE[10]: HW_PROC_ID=14 PROC_CHIP_ID=2 EC=0x21 OK
[ 83.345728954,6] CORE[10]: PIR=2096 RES=2096 OK (8 threads)
[ 83.345732321,6] Cache: I=32 D=64/512/8192/0
[ 83.345802194,6] CORE[11]: HW_PROC_ID=17 PROC_CHIP_ID=2 EC=0x21 OK
[ 83.345805742,6] CORE[11]: PIR=2160 RES=2160 OK [boot](8 threads)
[ 83.345809567,6] Cache: I=32 D=64/512/8192/0
[ 83.345881043,6] CORE[12]: HW_PROC_ID=18 PROC_CHIP_ID=3 EC=0x21 OK
[ 83.345884583,6] CORE[12]: PIR=2208 RES=2208 OK (8 threads)
[ 83.345888000,6] Cache: I=32 D=64/512/8192/0
[ 83.345962527,6] CORE[13]: HW_PROC_ID=19 PROC_CHIP_ID=3 EC=0x21 OK
[ 83.345966109,6] CORE[13]: PIR=2216 RES=2216 OK (8 threads)
[ 83.345969454,6] Cache: I=32 D=64/512/8192/0
[ 83.346045787,6] CORE[14]: HW_PROC_ID=20 PROC_CHIP_ID=3 EC=0x21 OK
[ 83.346049357,6] CORE[14]: PIR=2224 RES=2224 OK (8 threads)
[ 83.346052787,6] Cache: I=32 D=64/512/8192/0
[ 83.346131208,6] CORE[15]: HW_PROC_ID=21 PROC_CHIP_ID=3 EC=0x21 OK
[ 83.346134797,6] CORE[15]: PIR=2272 RES=2272 OK (8 threads)
[ 83.346138123,6] Cache: I=32 D=64/512/8192/0
[ 83.346230153,6] IPLPARAMS: 1 serial ports in array
[ 83.346233762,6] IPLPARAMS: Serial 0 rsrc: 2a00 loc: U78CB.001.WZS002B-P1-C1-T1
[ 83.346246288,7] MS VPD: is at 0x31202ca0
[ 83.346248727,7] MS VPD: MSAC is at 0x31202d10
[ 83.346251619,7] MS VPD: TCMS is at 0x31202d2c
[ 83.346254049,7] MS VPD: Maximum configured address: 0x8000002fffffffff
[ 83.346257237,7] MS VPD: Maximum possible address: 0x8000002fffffffff
[ 83.346260669,7] MS VPD: 0x31202ca0, area 0: installed functional shared
[ 83.346477059,7] Range: 0x0000002000000000..0x0000002800000000 on Chip 0x0 mattr: 0xa0000
[ 83.346498710,7] MS VPD: 0x31202ca0, area 1: installed functional shared
[ 83.346521324,7] Range: 0x0000002000000000..0x0000002800000000 on Chip 0x0 mattr: 0xa0000
[ 83.346534671,7] MS VPD: 0x31202ca0, area 2: installed functional shared
[ 83.346558078,7] Range: 0x0000000000000000..0x0000001000000000 on Chip 0x1 mattr: 0xa0000
[ 83.346578809,7] MS VPD: 0x31202ca0, area 3: installed functional shared
[ 83.346601842,7] Range: 0x0000000000000000..0x0000001000000000 on Chip 0x1 mattr: 0xa0000
[ 83.346614848,7] MS VPD: 0x31202ca0, area 4: installed functional shared
[ 83.346638786,7] Range: 0x0000002800000000..0x0000003000000000 on Chip 0x10 mattr: 0xa0000
[ 83.346661199,7] MS VPD: 0x31202ca0, area 5: installed functional shared
[ 83.346685304,7] Range: 0x0000002800000000..0x0000003000000000 on Chip 0x10 mattr: 0xa0000
[ 83.346699118,7] MS VPD: 0x31202ca0, area 6: installed functional shared
[ 83.346724262,7] Range: 0x0000001000000000..0x0000002000000000 on Chip 0x11 mattr: 0xa0000
[ 83.346747071,7] MS VPD: 0x31202ca0, area 7: installed functional shared
[ 83.346772342,7] Range: 0x0000001000000000..0x0000002000000000 on Chip 0x11 mattr: 0xa0000
[ 83.346785678,6] MS VPD: Total MB of RAM: 0x30000
[ 83.346788992,6] XSCOM: Found HW ID 0x0 (PCID 0x0) @ 0x3fc0000000000
[ 83.346817719,4] VPD: CCIN desc not available for : 54E5
[ 83.346972196,6] XSCOM: Found HW ID 0x1 (PCID 0x1) @ 0x3fc0800000000
[ 83.347001758,4] VPD: CCIN desc not available for : 54E5
[ 83.347157033,6] XSCOM: Found HW ID 0x10 (PCID 0x2) @ 0x3fc8000000000
[ 83.347186848,4] VPD: CCIN desc not available for : 54E5
[ 83.347341075,6] XSCOM: Found HW ID 0x11 (PCID 0x3) @ 0x3fc8800000000
[ 83.347371632,4] VPD: CCIN desc not available for : 54E5
[ 83.347533416,6] FSP #0: FSP HW version 2, SW version 1, chip DD1.0
[ 83.347540550,7] FSP #0: Found 2 IO PATH
[ 83.347542932,7] FSP #0: IO PATH 0 is Active PSI Link, GXHB at 8003fffe80000000
[ 83.347596919,7] FSP #0: IO PATH 1 is Backup PSI Link, GXHB at 8003fffe80100000
[ 83.347678374,7] CHIPTOD: Found on chip 0x0 [primary]
[ 83.347714015,7] CHIPTOD: Found on chip 0x1
[ 83.347750158,7] CHIPTOD: Found on chip 0x10 [secondary]
[ 83.347788450,7] CHIPTOD: Found on chip 0x11
[ 83.347928522,6] CEC: HUB FRU 0 is CPU Card
[ 83.347931393,6] CEC: 2 chips in FRU
[ 83.347933658,7] CEC: IO Hub Chip #0 OK
[ 83.347935859,7] CEC: PChip: 0 HUB ID: 0001 [EC=0x21] Hub#=0)
[ 83.347939097,6] CEC: Murano !
[ 83.347941022,6] CEC: HW CHIP=0x0, HW TOPO=0x0000
[ 83.347976807,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C32 (SLCA rsrc 0x1000)
[ 83.347989730,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C32 (SLCA rsrc 0x1000)
[ 83.347997622,7] CEC: IO Hub Chip #1 OK
[ 83.347999764,7] CEC: PChip: 1 HUB ID: 0001 [EC=0x21] Hub#=1)
[ 83.348002952,6] CEC: Murano !
[ 83.348004947,6] CEC: HW CHIP=0x1, HW TOPO=0x0010
[ 83.348041820,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C32 (SLCA rsrc 0x1000)
[ 83.348054718,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C32 (SLCA rsrc 0x1000)
[ 83.348064398,7] CEC: ibm,io-base-loc-code: U78CB.001.WZS002B-P1 (SLCA rsrc 0x800)
[ 83.348072097,7] CEC: LXRn=0 LXR=3100040100300042
[ 83.348074969,7] CEC: LX Info added to 30300010
[ 83.348078084,6] CEC: HUB FRU 1 is CPU Card
[ 83.348080786,6] CEC: 2 chips in FRU
[ 83.348082942,7] CEC: IO Hub Chip #0 OK
[ 83.348085123,7] CEC: PChip: 2 HUB ID: 0001 [EC=0x21] Hub#=2)
[ 83.348088348,6] CEC: Murano !
[ 83.348090391,6] CEC: HW CHIP=0x10, HW TOPO=0x0100
[ 83.348130117,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C33 (SLCA rsrc 0x1002)
[ 83.348138142,7] CEC: IO Hub Chip #1 OK
[ 83.348140274,7] CEC: PChip: 3 HUB ID: 0001 [EC=0x21] Hub#=3)
[ 83.348143541,6] CEC: Murano !
[ 83.348145605,6] CEC: HW CHIP=0x11, HW TOPO=0x0110
[ 83.348187442,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C33 (SLCA rsrc 0x1002)
[ 83.348200122,7] CEC: ibm,loc-code: U78CB.001.WZS002B-P1-C33 (SLCA rsrc 0x1002)
[ 83.348209011,7] CEC: ibm,io-base-loc-code: U78CB.001.WZS002B-P1 (SLCA rsrc 0x800)
[ 83.348216700,7] CEC: LXRn=0 LXR=3100040100300042
[ 83.348219552,7] CEC: LX Info added to 30300010
[ 83.348264438,4] VPD: Model name 8284-22A not known
[ 83.348302045,4] VPD: CCIN desc not available for : 2B08
[ 83.348359473,7] HBRT: Found mini-DT at 0x0x3140aae8 size: 0x00001000
[ 83.348431712,6] Parsing HDAT...done
[ 83.348532276,5] XSCOM: chip 0x0 at 0x3fc0000000000 [P8E DD2.1]
[ 83.348539101,5] XSCOM: chip 0x1 at 0x3fc0800000000 [P8E DD2.1]
[ 83.348545622,5] XSCOM: chip 0x10 at 0x3fc8000000000 [P8E DD2.1]
[ 83.348552081,5] XSCOM: chip 0x11 at 0x3fc8800000000 [P8E DD2.1]
[ 83.348557942,6] XSTOP: ibm,sw-checkstop-fir prop not found
[ 83.348560793,6] MFSI 0:0: Initialized
[ 83.348563052,6] MFSI 0:2: Initialized
[ 83.348565242,6] MFSI 0:1: Initialized
[ 83.348567744,6] MFSI 1:0: Initialized
[ 83.348569975,6] MFSI 1:2: Initialized
[ 83.348572155,6] MFSI 1:1: Initialized
[ 83.348574642,6] MFSI 10:0: Initialized
[ 83.348576881,6] MFSI 10:2: Initialized
[ 83.348579142,6] MFSI 10:1: Initialized
[ 83.348581594,6] MFSI 11:0: Initialized
[ 83.348583785,6] MFSI 11:2: Initialized
[ 83.348585958,6] MFSI 11:1: Initialized
[ 83.348845504,6] MEM: parsing reserved memory from reserved-names/-ranges properties
[ 83.348851933,7] HOMER: Init chip 0
[ 83.348855174,7] PBA BAR0 : 0x0000000000000000
[ 83.348857808,7] PBA MASK0: 0x0000000000000000
[ 83.348861224,7] PBA BAR2 : 0x4000002ffda00000
[ 83.348863964,7] PBA MASK2: 0x0000000000000000
[ 83.348866566,7] SLW Image at 0x2ffda00000 size 1MB
[ 83.348869740,4] SLW image is not reserved! Reserving
[ 83.348874470,7] PBA BAR3 : 0x0000000003b00000
[ 83.348877143,7] PBA MASK3: 0x0000000000000000
[ 83.348879692,7] OCC Common Area at 0x3b00000 size 1MB
[ 83.348882530,7] HOMER: Init chip 1
[ 83.348885406,7] PBA BAR0 : 0x0000000000000000
[ 83.348887908,7] PBA MASK0: 0x0000000000000000
[ 83.348891340,7] PBA BAR2 : 0x4000002ffde00000
[ 83.348894087,7] PBA MASK2: 0x0000000000000000
[ 83.348896708,7] SLW Image at 0x2ffde00000 size 1MB
[ 83.348899539,4] SLW image is not reserved! Reserving
[ 83.348904342,7] PBA BAR3 : 0x0000000000000000
[ 83.348906933,7] PBA MASK3: 0x0000000000000000
[ 83.348909628,7] HOMER: Init chip 16
[ 83.348912512,7] PBA BAR0 : 0x0000000000000000
[ 83.348914980,7] PBA MASK0: 0x0000000000000000
[ 83.348918391,7] PBA BAR2 : 0x4000002ffe200000
[ 83.348921092,7] PBA MASK2: 0x0000000000000000
[ 83.348923687,7] SLW Image at 0x2ffe200000 size 1MB
[ 83.348926517,4] SLW image is not reserved! Reserving
[ 83.348931357,7] PBA BAR3 : 0x0000000000000000
[ 83.348933918,7] PBA MASK3: 0x0000000000000000
[ 83.348936493,7] HOMER: Init chip 17
[ 83.348939394,7] PBA BAR0 : 0x0000000000000000
[ 83.348941890,7] PBA MASK0: 0x0000000000000000
[ 83.348945287,7] PBA BAR2 : 0x4000002ffe600000
[ 83.348947940,7] PBA MASK2: 0x0000000000000000
[ 83.348950441,7] SLW Image at 0x2ffe600000 size 1MB
[ 83.348953348,4] SLW image is not reserved! Reserving
[ 83.348958239,7] PBA BAR3 : 0x0000000000000000
[ 83.348960778,7] PBA MASK3: 0x0000000000000000
[ 83.358874291,7] HBRT: Chip 0 HOMER base 0000002001400000 : 00400000
[ 83.358879889,7] HBRT: OCC common base 0000002000800000 : 00800000
[ 83.364026696,7] HBRT: Chip 1 HOMER base 000000003a000000 : 00400000
[ 83.364038909,7] HBRT: OCC common base 0000002000800000 : 00800000
[ 83.369990270,7] HBRT: Chip 16 HOMER base 0000002800400000 : 00400000
[ 83.370001552,7] HBRT: OCC common base 0000002000800000 : 00800000
[ 83.375962319,7] HBRT: Chip 17 HOMER base 0000001000400000 : 00400000
[ 83.375970429,7] HBRT: OCC common base 0000002000800000 : 00800000
[ 83.375989846,7] CPU idle state device tree init
[ 83.375996870,4] SLW: HB-provided idle states property found
[ 83.376185592,5] PLAT: Detected Firenze platform
[ 83.376192111,6] CPU: CPU from DT PIR=0x0030 Server#=0x30 State=3
[ 83.376201415,6] CPU: 8 secondary threads
[ 83.376205496,6] CPU: CPU from DT PIR=0x0060 Server#=0x60 State=3
[ 83.376213745,6] CPU: 8 secondary threads
[ 83.376217815,6] CPU: CPU from DT PIR=0x0068 Server#=0x68 State=3
[ 83.376225988,6] CPU: 8 secondary threads
[ 83.376230180,6] CPU: CPU from DT PIR=0x0070 Server#=0x70 State=3
[ 83.376238411,6] CPU: 8 secondary threads
[ 83.376242475,6] CPU: CPU from DT PIR=0x00a0 Server#=0xa0 State=3
[ 83.376250722,6] CPU: 8 secondary threads
[ 83.376254739,6] CPU: CPU from DT PIR=0x00b0 Server#=0xb0 State=3
[ 83.376262879,6] CPU: 8 secondary threads
[ 83.376266859,6] CPU: CPU from DT PIR=0x00e0 Server#=0xe0 State=3
[ 83.376275011,6] CPU: 8 secondary threads
[ 83.376279131,6] CPU: CPU from DT PIR=0x00f0 Server#=0xf0 State=3
[ 83.376287237,6] CPU: 8 secondary threads
[ 83.376291289,6] CPU: CPU from DT PIR=0x0820 Server#=0x820 State=3
[ 83.376299877,6] CPU: 8 secondary threads
[ 83.376303958,6] CPU: CPU from DT PIR=0x0828 Server#=0x828 State=3
[ 83.376312285,6] CPU: 8 secondary threads
[ 83.376316295,6] CPU: CPU from DT PIR=0x0830 Server#=0x830 State=3
[ 83.376324667,6] CPU: 8 secondary threads
[ 83.376328832,6] CPU: CPU from DT PIR=0x0870 Server#=0x870 State=3
[ 83.376336891,6] CPU: 8 secondary threads
[ 83.376341023,6] CPU: CPU from DT PIR=0x08a0 Server#=0x8a0 State=3
[ 83.376349346,6] CPU: 8 secondary threads
[ 83.376353401,6] CPU: CPU from DT PIR=0x08a8 Server#=0x8a8 State=3
[ 83.376361677,6] CPU: 8 secondary threads
[ 83.376365683,6] CPU: CPU from DT PIR=0x08b0 Server#=0x8b0 State=3
[ 83.376373894,6] CPU: 8 secondary threads
[ 83.376378004,6] CPU: CPU from DT PIR=0x08e0 Server#=0x8e0 State=3
[ 83.376386377,6] CPU: 8 secondary threads
[ 83.376392710,7] CPU: New max PIR set to 0x8e7
[ 83.386559240,7] IRQ: Registering 0010..0015 ops @0x3008eea0 (data 0x30360740)
[ 83.386579817,5] PSI[0x000]: Found PSI bridge [active=1]
[ 83.386586952,5] PSI[0x001]: Working chip not found
[ 83.386596327,7] IRQ: Registering 20010..20015 ops @0x3008eea0 (data 0x30360ad8)
[ 83.386609822,5] PSI[0x010]: Found PSI bridge [active=0]
[ 83.386617011,5] PSI[0x011]: Working chip not found
[ 83.386620300,6] CPU: Setting up secondary CPU state
[ 83.386623190,6] CPU: Calling in all processors...
[ 83.386626057,7] INIT: CPU PIR 0x0871 called in
[ 83.386626314,7] INIT: CPU PIR 0x0876 called in
[ 83.386626229,7] INIT: CPU PIR 0x0877 called in
[ 83.392892226,7] INIT: CPU PIR 0x0074 called in
[ 83.392892221,7] INIT: CPU PIR 0x0071 called in
[ 83.392892227,7] INIT: CPU PIR 0x0072 called in
[ 83.385250535,7] INIT: CPU PIR 0x0037 called in
[ 83.385250450,7] INIT: CPU PIR 0x0034 called in
[ 83.392892228,7] INIT: CPU PIR 0x0076 called in
[ 83.398216522,7] INIT: CPU PIR 0x00f1 called in
[ 83.391118910,7] INIT: CPU PIR 0x006c called in
[ 83.387647328,7] INIT: CPU PIR 0x08a5 called in
[ 83.387647328,7] INIT: CPU PIR 0x08a2 called in
[ 83.387647329,7] INIT: CPU PIR 0x08a7 called in
[ 83.391269512,7] INIT: CPU PIR 0x00e5 called in
[ 83.398216010,7] INIT: CPU PIR 0x00f6 called in
[ 83.387647323,7] INIT: CPU PIR 0x08a0 called in
[ 83.394239529,7] INIT: CPU PIR 0x08ae called in
[ 83.396606711,7] INIT: CPU PIR 0x0836 called in
[ 83.385250527,7] INIT: CPU PIR 0x0035 called in
[ 83.399901020,7] INIT: CPU PIR 0x00a3 called in
[ 83.392892230,7] INIT: CPU PIR 0x0073 called in
[ 83.400881818,7] INIT: CPU PIR 0x08b5 called in
[ 83.400881808,7] INIT: CPU PIR 0x08b0 called in
[ 83.400637749,7] INIT: CPU PIR 0x0063 called in
[ 83.400637031,7] INIT: CPU PIR 0x0065 called in
[ 83.385250896,7] INIT: CPU PIR 0x0031 called in
[ 83.392892527,7] INIT: CPU PIR 0x0075 called in
[ 83.394239359,7] INIT: CPU PIR 0x08af called in
[ 83.391269510,7] INIT: CPU PIR 0x00e7 called in
[ 83.391269507,7] INIT: CPU PIR 0x00e3 called in
[ 83.390072994,7] INIT: CPU PIR 0x00b6 called in
[ 83.391118767,7] INIT: CPU PIR 0x006b called in
[ 83.389746515,7] INIT: CPU PIR 0x0828 called in
[ 83.389746520,7] INIT: CPU PIR 0x0829 called in
[ 83.396607527,7] INIT: CPU PIR 0x0830 called in
[ 83.400637436,7] INIT: CPU PIR 0x0066 called in
[ 83.400637138,7] INIT: CPU PIR 0x0060 called in
[ 83.388362617,7] INIT: CPU PIR 0x0823 called in
[ 83.400637444,7] INIT: CPU PIR 0x0062 called in
[ 83.398216741,7] INIT: CPU PIR 0x00f5 called in
[ 83.399901017,7] INIT: CPU PIR 0x00a7 called in
[ 83.390636904,7] INIT: CPU PIR 0x08e7 called in
[ 83.390636903,7] INIT: CPU PIR 0x08e6 called in
[ 83.390636975,7] INIT: CPU PIR 0x08e4 called in
[ 83.387647331,7] INIT: CPU PIR 0x08a1 called in
[ 83.394239196,7] INIT: CPU PIR 0x08aa called in
[ 83.387647331,7] INIT: CPU PIR 0x08a4 called in
[ 83.400881809,7] INIT: CPU PIR 0x08b4 called in
[ 83.392893400,7] INIT: CPU PIR 0x0077 called in
[ 83.388362396,7] INIT: CPU PIR 0x0821 called in
[ 83.396606712,7] INIT: CPU PIR 0x0834 called in
[ 83.392892225,7] INIT: CPU PIR 0x0070 called in
[ 83.385250517,7] INIT: CPU PIR 0x0030 called in
[ 83.385250626,7] INIT: CPU PIR 0x0032 called in
[ 83.386626071,7] INIT: CPU PIR 0x0874 called in
[ 83.400881827,7] INIT: CPU PIR 0x08b2 called in
[ 83.400881814,7] INIT: CPU PIR 0x08b1 called in
[ 83.385250541,7] INIT: CPU PIR 0x0036 called in
[ 83.390072938,7] INIT: CPU PIR 0x00b1 called in
[ 83.385250876,7] INIT: CPU PIR 0x0033 called in
[ 83.398216012,7] INIT: CPU PIR 0x00f3 called in
[ 83.399901249,7] INIT: CPU PIR 0x00a1 called in
[ 83.391269508,7] INIT: CPU PIR 0x00e4 called in
[ 83.398216015,7] INIT: CPU PIR 0x00f2 called in
[ 83.400637446,7] INIT: CPU PIR 0x0067 called in
[ 83.390073148,7] INIT: CPU PIR 0x00b4 called in
[ 83.390072926,7] INIT: CPU PIR 0x00b0 called in
[ 83.389746519,7] INIT: CPU PIR 0x082b called in
[ 83.388362397,7] INIT: CPU PIR 0x0820 called in
[ 83.388362908,7] INIT: CPU PIR 0x0825 called in
[ 83.387647327,7] INIT: CPU PIR 0x08a3 called in
[ 83.387647330,7] INIT: CPU PIR 0x08a6 called in
[ 83.391269511,7] INIT: CPU PIR 0x00e6 called in
[ 83.391269509,7] INIT: CPU PIR 0x00e2 called in
[ 83.396606722,7] INIT: CPU PIR 0x0837 called in
[ 83.399901019,7] INIT: CPU PIR 0x00a0 called in
[ 83.386626072,7] INIT: CPU PIR 0x0873 called in
[ 83.386626063,7] INIT: CPU PIR 0x0872 called in
[ 83.400637443,7] INIT: CPU PIR 0x0061 called in
[ 83.390636901,7] INIT: CPU PIR 0x08e5 called in
[ 83.399901013,7] INIT: CPU PIR 0x00a6 called in
[ 83.391269510,7] INIT: CPU PIR 0x00e0 called in
[ 83.388362438,7] INIT: CPU PIR 0x0827 called in
[ 83.388363136,7] INIT: CPU PIR 0x0822 called in
[ 83.394239192,7] INIT: CPU PIR 0x08a8 called in
[ 83.396607476,7] INIT: CPU PIR 0x0832 called in
[ 83.390072928,7] INIT: CPU PIR 0x00b2 called in
[ 83.390072931,7] INIT: CPU PIR 0x00b5 called in
[ 83.398216011,7] INIT: CPU PIR 0x00f0 called in
[ 83.399901745,7] INIT: CPU PIR 0x00a5 called in
[ 83.394239192,7] INIT: CPU PIR 0x08ac called in
[ 83.391119844,7] INIT: CPU PIR 0x006f called in
[ 83.391269714,7] INIT: CPU PIR 0x00e1 called in
[ 83.399901016,7] INIT: CPU PIR 0x00a4 called in
[ 83.396606716,7] INIT: CPU PIR 0x0833 called in
[ 83.396607949,7] INIT: CPU PIR 0x0835 called in
[ 83.390072943,7] INIT: CPU PIR 0x00b7 called in
[ 83.391118747,7] INIT: CPU PIR 0x006a called in
[ 83.390636905,7] INIT: CPU PIR 0x08e1 called in
[ 83.394239373,7] INIT: CPU PIR 0x08a9 called in
[ 83.394239189,7] INIT: CPU PIR 0x08ad called in
[ 83.394239352,7] INIT: CPU PIR 0x08ab called in
[ 83.400881812,7] INIT: CPU PIR 0x08b3 called in
[ 83.386626321,7] INIT: CPU PIR 0x0875 called in
[ 83.390636906,7] INIT: CPU PIR 0x08e0 called in
[ 83.400881833,7] INIT: CPU PIR 0x08b7 called in
[ 83.400637466,7] INIT: CPU PIR 0x0064 called in
[ 83.400881813,7] INIT: CPU PIR 0x08b6 called in
[ 83.389746517,7] INIT: CPU PIR 0x082c called in
[ 83.389746521,7] INIT: CPU PIR 0x082a called in
[ 83.398216013,7] INIT: CPU PIR 0x00f7 called in
[ 83.390636985,7] INIT: CPU PIR 0x08e3 called in
[ 83.398216010,7] INIT: CPU PIR 0x00f4 called in
[ 83.399901018,7] INIT: CPU PIR 0x00a2 called in
[ 83.390636978,7] INIT: CPU PIR 0x08e2 called in
[ 83.391118762,7] INIT: CPU PIR 0x0068 called in
[ 83.391118735,7] INIT: CPU PIR 0x0069 called in
[ 83.391118754,7] INIT: CPU PIR 0x006d called in
[ 83.389746522,7] INIT: CPU PIR 0x082e called in
[ 83.388362395,7] INIT: CPU PIR 0x0824 called in
[ 83.396608253,7] INIT: CPU PIR 0x0831 called in
[ 83.388362439,7] INIT: CPU PIR 0x0826 called in
[ 83.389746518,7] INIT: CPU PIR 0x082d called in
[ 83.389746520,7] INIT: CPU PIR 0x082f called in
[ 83.390072942,7] INIT: CPU PIR 0x00b3 called in
[ 83.391118741,7] INIT: CPU PIR 0x006e called in
[ 83.389916655,5] CPU: All 128 processors called in...
[ 83.389920823,6] CPU: enabling power management
[ 83.389948335,6] CHIPTOD: Calculated MCBS is 0x4d (Cfreq=4157000000 Tfreq=32000000)
[ 83.389950137,7] CHIPTOD: Base TFMR=0x4d12000000000000
[ 83.388574402,7] CHIPTOD: Master sync on CPU PIR 0x0030...
[ 83.444933551,7] CHIPTOD: Slave sync on CPU PIR 0x0060...
[ 83.476384424,7] CHIPTOD: Slave sync on CPU PIR 0x0068...
[ 84.7127758,7] CHIPTOD: Slave sync on CPU PIR 0x0070...
[ 84.55105771,7] CHIPTOD: Slave sync on CPU PIR 0x00a0...
[ 84.86246833,7] CHIPTOD: Slave sync on CPU PIR 0x00b0...
[ 84.128413477,7] CHIPTOD: Slave sync on CPU PIR 0x00e0...
[ 84.176329644,7] CHIPTOD: Slave sync on CPU PIR 0x00f0...
[ 84.207477558,7] CHIPTOD: Slave sync on CPU PIR 0x0820...
[ 84.249830712,7] CHIPTOD: Slave sync on CPU PIR 0x0828...
[ 84.297658213,7] CHIPTOD: Slave sync on CPU PIR 0x0830...
[ 84.328648090,7] CHIPTOD: Slave sync on CPU PIR 0x0870...
[ 84.365760435,7] CHIPTOD: Slave sync on CPU PIR 0x08a0...
[ 84.413592283,7] CHIPTOD: Slave sync on CPU PIR 0x08a8...
[ 84.461473388,7] CHIPTOD: Slave sync on CPU PIR 0x08b0...
[ 84.492467875,7] CHIPTOD: Slave sync on CPU PIR 0x08e0...
[ 1.135475609,7] CHIPTOD: PIR 0x0030 TB=2697b190
[ 1.140597493,7] CHIPTOD: PIR 0x0060 TB=26e5d8ec
[ 1.145718830,7] CHIPTOD: PIR 0x0068 TB=2733fe25
[ 1.150840107,7] CHIPTOD: PIR 0x0070 TB=27822322
[ 1.155962292,7] CHIPTOD: PIR 0x00a0 TB=27d04bab
[ 1.161083636,7] CHIPTOD: PIR 0x00b0 TB=281e70ec
[ 1.166205599,7] CHIPTOD: PIR 0x00e0 TB=286c9896
[ 1.171327053,7] CHIPTOD: PIR 0x00f0 TB=28babe43
[ 1.176477805,7] CHIPTOD: PIR 0x0820 TB=29095663
[ 1.181598874,7] CHIPTOD: PIR 0x0828 TB=29577a91
[ 1.186720072,7] CHIPTOD: PIR 0x0830 TB=29a59f3d
[ 1.191841664,7] CHIPTOD: PIR 0x0870 TB=29f3c576
[ 1.191845273,7] CHIPTOD: PIR 0x08a0 TB=29f3d390
[ 1.196966356,7] CHIPTOD: PIR 0x08a8 TB=2a41f7cb
[ 1.202087738,7] CHIPTOD: PIR 0x08b0 TB=2a901d30
[ 1.207209751,7] CHIPTOD: PIR 0x08e0 TB=2ade450e
[ 1.212343017,7] CHIPTOD: TOD Topology in Use: Primary
[ 1.212344512,7] CHIPTOD: Primary configuration:
[ 1.212345636,7] CHIPTOD: Chip id: 0, Role: MDMT, Status: Active Master
[ 1.212347195,7] CHIPTOD: Secondary configuration:
[ 1.212348252,7] CHIPTOD: Chip id: 16, Role: MDMT, Status: Backup Master
[ 1.212366090,3] DT: Unexpected property length /xscom@3fc0000000000/i2cm@a0020/clock-frequency
[ 1.212369108,3] DT: Expected len: 4 got len: 8
[ 1.212370117,0] Assert fail: core/device.c:603:0
[ 1.212371550,0] Aborting!
CPU 0870 Backtrace:
S: 0000000033dc39e0 R: 0000000030013758 .backtrace+0x24
S: 0000000033dc3a60 R: 0000000030018e0c ._abort+0x4c
S: 0000000033dc3ae0 R: 0000000030018e88 .assert_fail+0x34
S: 0000000033dc3b60 R: 0000000030023da4 .dt_require_property+0xb4
S: 0000000033dc3bf0 R: 000000003002403c .dt_prop_get_u32+0x14
S: 0000000033dc3c60 R: 000000003004e884 .p8_i2c_init+0x12c
S: 0000000033dc3e30 R: 0000000030014684 .main_cpu_entry+0x4a8
S: 0000000033dc3f00 R: 00000000300025a0 boot_entry+0x198

extract-gcov.c not 64-bit clean

The way this tool is written (i.e. struct gcov_info with pointers) assumes it can only be compiled on 64-bit hosts, while the build system neither enforces a 64-bit build nor ensures the host system is sane. Building on hosts with default 32-bit targets causes bunch of errors around padding/casting.

Seen on: Debian 8 on a PowerMac G5 (user space is mostly 32-bit, kernel is 64, gcc takes -m64 to create 64-bit bins).

The simplest fix I could see is passing -m64 to HOSTCC.

diff --git a/Makefile.main b/Makefile.main
index 86a54be..78804ec 100644
--- a/Makefile.main
+++ b/Makefile.main
@@ -33,7 +33,7 @@ CWARNS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \

Host tools and options

HOSTCC=gcc
HOSTEND=$(shell uname -m | sed -e 's/^i.86$$/LITTLE/' -e 's/^x86./LITTLE/' -e 's/^ppc64le/LITTLE/' -e 's/^ppc.*/BIG/')
-HOSTCFLAGS=-O1 $(CWARNS) -DHAVE_$(HOSTEND)ENDIAN -MMD
+HOSTCFLAGS=-O1 $(CWARNS) -DHAVE$(HOSTEND)_ENDIAN -MMD -m64
HOSTCFLAGS += $(call try-cflag,$(HOSTCC),-std=gnu11)
HOSTCFLAGS += $(call try-cflag,$(HOSTCC),-Wjump-misses-init)
$(call try-cflag,$(HOSTCC),-Wsuggest-attribute=const) \

Chassis and Host state services show incorrect states when targets exit

The chassis and host code monitors for certain targets to reach "JobRemoved" to know when a target has completed. This works great initially when the target is run. But later, when the target is stopped, we get this same event. This doesn't really hurt anything but it's confusing in the journal because you're stopping the target (i.e. powering down) and you see a journal log indicating we powered on. Later in the power down process, we get the correct journal entries but still confusing initially.

Test 'run-mem_region_reservations' SIGABRT when tried with AFL instrumentation

Error Description:
make check is failing with the following error.
[ RUN-TEST ] core/test/run-mem_region_reservations
run-mem_region_reservations: core/test/../mem_region.c:472: void mem_free(struct mem_region *, void *, const char ): Assertion `mem < region_start(region) + region->len' failed.
./test/run.sh: line 7: 20971 Aborted (core dumped) $ 2>&1 > $t
MEM: parsing reserved memory from reserved-names/-ranges properties
Releasing unused memory:
ibm,firmware-heap: 1192/4096 used
ibm,firmware-allocs-memory@5204170: 0/1048576 used
Reserved regions:
0x000000004000..000000004fff : test.3
/home/rnsastry/skiboot/core/test/Makefile.check:49: recipe for target 'core/test/run-mem_region_reservations-check' failed
make: *** [core/test/run-mem_region_reservations-check] Error 134

The above created a file named vgcore.20971 (13MB)

Steps to re-produce:

On a Ubuntu 16.04 guest running on Mac.

AFL Setup:
apt-get install build-essential wget git llvm clang flex bison
# mkdir $HOME/afl
# cd $HOME/afl
# wget -N http://lcamtuf.coredump.cx/afl/releases/afl-latest.tgz
# tar xz afl-latest.tgz
# make
# cd llvm_mode
# make

skiboot Setup:
# git clone https://github.com/open-power/skiboot
# cd skiboot
In Makefile.main change HOSTCC=gcc to HOSTCC=afl-clang-fast
comment out "CWARNS"
To eliminate 'make check' error, Did a little hack to file libc/string/strdup.c line # 16:
char *strdup(const char *src) changed to char *(strdup)(const char *src)

# make
# make check

$ gdb core/test/run-mem_region_reservations vgcore.20971
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from core/test/run-mem_region_reservations...done.

warning: core file may not match specified executable file.
[New LWP 20971]
Core was generated by `'.
Program terminated with signal SIGABRT, Aborted.
#0 0x0000000004e6f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x0000000004e6f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x0000000004e7102a in __GI_abort () at abort.c:89
#2 0x0000000004e67bd7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x4131bb "mem < region_start(region) + region->len",
file=file@entry=0x4130d2 "core/test/../mem_region.c", line=line@entry=472,
function=function@entry=0x413157 "void mem_free(struct mem_region *, void *, const char *)") at assert.c:92
#3 0x0000000004e67c82 in __GI___assert_fail (assertion=0x4131bb "mem < region_start(region) + region->len", file=0x4130d2 "core/test/../mem_region.c", line=472,
function=0x413157 "void mem_free(struct mem_region *, void *, const char *)") at assert.c:101
#4 0x0000000000402073 in mem_free (region=, mem=, location=0xb4 <error: Cannot access memory at address 0xb4>)
at core/test/../mem_region.c:472
#5 0x0000000000408069 in __free (p=0x5305420, location=) at core/test/../malloc.c:43
#6 mem_region_add_dt_reserved_node (parent=, region=) at core/test/../mem_region.c:1122
#7 mem_region_add_dt_reserved () at core/test/../mem_region.c:1178
#8 0x00000000004118fc in main () at core/test/run-mem_region_reservations.c:218

(gdb) i r
rax 0x0 0
rbx 0x4028000 67272704
rcx 0x4e6f428 82244648
rdx 0x6 6
rsi 0x51eb 20971
rdi 0x51eb 20971
rbp 0x4131bb 0x4131bb
rsp 0xfff000658 0xfff000658
r8 0xb4 180
r9 0x0 0
r10 0x8 8
r11 0x5305730 87054128
r12 0x1d8 472
r13 0x413157 4272471
r14 0x7 7
r15 0x5305420 87053344
rip 0x4e6f428 0x4e6f428 <__GI_raise+56>
eflags 0x44 [ PF ZF ]
cs 0x0 0
ss 0x0 0
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0

please let me know if you need more information. Thank you.

Parallel build is broken

When trying to build with multiple jobs, build will fail..

commit 9997117 just workarounds in spec file, while the situation when developer will want to look into it is really rare. IMO dependencies just needs to be fixed

XSCOM for POWER9

long wait in IPMI device interface

Hangs for a long time on

IPMI message handler version 39.2
IPMI device interface

for palmetto with the ipmid on the BMC running. It will eventually get past it but wait for > 30secs

skiboot-2e3bcfe490bb2ae0e3fbe5c062677026d2096093.tar.gz

Support N25Qx256Ax NOR flash

Commit 71c2d6b added support for N25Q256Ax which is what IBM is using, but Foxconn is using N25Qx256Ax for their Barreleye systems. So need to add N25Qx256Ax to pflash.

fast-reboot got aborted after an IPMI PNOR Reprovisioning in an OpenPower habanero system.

Enable fast-reboot.
Do a IPMI PNOR Re-provisioning
Issue a reboot command in host OS

ipmitool raw 0x3a 0x1c

[ 732.350825805,5] IPMI: PNOR access requested

[ 755.012809365,5] IPMI: PNOR access released

ipmitool raw 0x3a 01x1d

ipmitool raw 0x3a 0x1d

nvram --print-config=experimental-fast-reset -p ibm,skiboot

feeling-lucky

reboot

�[-1;-1f�[-1;-1fUbuntu 16.10�[-1;-1f. . . .��[-1;-1fUbuntu 16.10�[-1;-1f. . . .�[-1;-1fUbuntu 16.10�[-1;-1f. . . .�[-1;-1fUbuntu 16.10�[-1;-1f. . . .[ 383.343956] reboot: Restarting system
[ 383.343956] reboot: Restarting system
[ 828.392118244,5] OPAL: Reboot request...
[ 828.392165074,5] RESET: Initiating fast reboot 2...
[ 829.091601733,5] FLASH: Queueing preload of 0/0
[ 829.091656945,5] FLASH: Queueing preload of 1/0
[ 829.091740869,5] PSI: Hot reset!
[ 829.091755903,6] FFS: Flash header not found. Code: 100
[ 829.091756976,3] FLASH: Can't open ffs handle
[ 829.091804429,6] FFS: Flash header not found. Code: 100
[ 829.091805298,3] FLASH: Can't open ffs handle
[ 829.146283503,5] PCI: Clearing all devices...
[ 829.147063592,5] PCI: Resetting PHBs...
[ 831.250490342,5] PCI: Probing slots...
[ 834.456861275,5] PHB#0000:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot3
[ 834.456997176,5] PHB#0000:01:00.0 [EP ] 14e4 168e R:10 C:020000 ( ethernet) LOC_CODE=Slot3
[ 834.459799128,5] PHB#0000:01:00.1 [EP ] 14e4 168e R:10 C:020000 ( ethernet) LOC_CODE=Slot3
[ 834.473437301,5] PHB#0001:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..11 SLOT=Backplane PLX
[ 834.482408512,5] PHB#0001:01:00.0 [SWUP] 10b5 8748 R:ca C:060400 B:02..11 LOC_CODE=Backplane PLX
[ 834.496526873,5] PHB#0001:02:01.0 [SWDN] 10b5 8748 R:ca C:060400 B:03..07 SLOT=Network Mezz
[ 834.500856183,5] PHB#0001:02:08.0 [SWDN] 10b5 8748 R:ca C:060400 B:08..08 SLOT=Storage Mezz
[ 835.003118296,5] PHB#0001:08:00.0 [LGCY] 1b4b 9235 R:11 C:010601 ( sata) LOC_CODE=Storage Mezz
[ 835.006168734,5] PHB#0001:02:09.0 [SWDN] 10b5 8748 R:ca C:060400 B:09..09 SLOT=Backplane USB
[ 835.026572642,5] PHB#0001:09:00.0 [EP ] 104c 8241 R:02 C:0c0330 ( usb-xhci) LOC_CODE=Backplane USB
[ 835.036587601,5] PHB#0001:02:0a.0 [SWDN] 10b5 8748 R:ca C:060400 B:0a..0b SLOT=Backplane BMC
[ 835.039215199,5] PHB#0001:0a:00.0 [ETOX] 1a03 1150 R:03 C:060400 B:0b..0b LOC_CODE=Backplane BMC
[ 835.053166383,5] PHB#0001:0b:00.0 [PCID] 1a03 2000 R:30 C:030000 ( vga) LOC_CODE=Backplane BMC
[ 835.063544213,5] PHB#0001:02:10.0 [SWDN] 10b5 8748 R:ca C:060400 B:0c..0c SLOT=Slot2
[ 835.086009589,5] PHB#0001:0c:00.0 [EP ] 14e4 1657 R:01 C:020000 ( ethernet) LOC_CODE=Slot2
[ 835.088915295,5] PHB#0001:0c:00.1 [EP ] 14e4 1657 R:01 C:020000 ( ethernet) LOC_CODE=Slot2
[ 835.105122109,5] PHB#0001:0c:00.2 [EP ] 14e4 1657 R:01 C:020000 ( ethernet) LOC_CODE=Slot2
[ 835.107720710,5] PHB#0001:0c:00.3 [EP ] 14e4 1657 R:01 C:020000 ( ethernet) LOC_CODE=Slot2
[ 835.125780497,5] PHB#0001:02:11.0 [SWDN] 10b5 8748 R:ca C:060400 B:0d..11 SLOT=Slot1
[ 835.128820124,5] PHB#0002:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot4
[ 835.136405431,5] PHB#0002:01:00.0 [EP ] 9005 028d R:01 C:010400 ( raid) LOC_CODE=Slot4
[ 835.148190035,5] IPMI: Resetting boot count on successful boot
[ 835.215797508,5] INIT: Waiting for kernel...
[ 835.262653478,5] INIT: platform wait for kernel load failed
[ 835.279700076,5] INIT: Assuming kernel at 0x20000000
[ 835.279756621,5] INIT: Kernel loaded, size: 4096 bytes (0 = unknown preload)
[ 835.354325014,5] INIT: ELF header not found. Assuming raw binary.
[ 835.375301725,5] Free space in HEAP memory regions:
[ 835.405121386,5] Region ibm,firmware-heap free: a226a8
[ 835.444796100,5] Region ibm,firmware-allocs-memory@0 free: 10cd70
[ 835.459925631,5] Total free: 11727896
[ 835.459985310,5] INIT: Starting kernel at 0x20010000, fdt at 0x305655c0 (size 0x15868)
[ 835.502261501,3] ***********************************************
[ 835.508522821,3] Unexpected exception e40 !
[ 835.508587112,3] SRR0 : 0000000030002700 SRR1 : 90000000001a1000
[ 836.031794429,3] HSRR0: 0000000020010000 HSRR1: 9000000000001000
[ 836.051538751,3] LR : 2001000030090896 CTR : 2001000000000000
[ 836.059701452,3] CFAR : 000000003000519c
[ 836.059760655,3] CR : 24084482 XER: 20000000
[ 836.067437364,3] GPR00: 0000000030014374 GPR16: c00000000152efb0
[ 836.081424921,3] GPR01: 0000000031dc3bb0 GPR17: 0000000000000008
[ 836.089287782,3] GPR02: 00000000300c7900 GPR18: c000003c8e030000
[ 836.096855734,3] GPR03: 00000000305655c0 GPR19: c00000000144dbc8
[ 836.104780774,3] GPR04: 0000000000000000 GPR20: c000003c8e030080
[ 836.114096238,3] GPR05: 0000000000000000 GPR21: c000000001438f68
[ 836.121974014,3] GPR06: 0000000065504150 GPR22: c000003c8e030000
[ 836.129358925,3] GPR07: 0000000040000001 GPR23: c000003ffd221c40
[ 836.141237695,3] GPR08: 0000000030000000 GPR24: 000000003021c5b8
[ 836.148247263,3] GPR09: 00000000300050b0 GPR25: 0000000000000001
[ 836.155874985,3] GPR10: 00000000000050b0 GPR26: 0000000040000000
[ 836.162949842,3] GPR11: 0000000000000000 GPR27: 0000000000000001
[ 836.185082352,3] GPR12: 0000000044084482 GPR28: 0000000000000000
[ 836.195715571,3] GPR13: 0000000031dc0000 GPR29: 0000000000000000
[ 836.210944338,3] GPR14: 0000000000000001 GPR30: 000000003021c590
[ 836.217309755,3] GPR15: c000000001041c38 GPR31: 000000003021c580
[ 836.223766973,0] Aborting!
CPU 0070 Backtrace:
S: 0000000031dc3a20 R: 000000003001379c .backtrace+0x24
S: 0000000031dc3aa0 R: 0000000030018ff0 ._abort+0x4c
S: 0000000031dc3b20 R: 000000003002551c .exception_entry+0x114
S: 0000000031dc3bb0 R: 0000000000001f00 * +0x1f00
S: 0000000031dc3d80 R: 0000000030014374 .load_and_boot_kernel+0x9c4
S: 0000000031dc3e60 R: 000000003002356c .fast_reboot_entry+0x46c
S: 0000000031dc3f00 R: 0000000030002840 fast_reset_entry+0x2c

GARD tool on non open-power systems output is not clear

I ran gard tool on fsp system where the /proc/device-tree/chosen/ibm,system-flash node doesn't exist. So output should be more clear and straight forward. Even i ran under root user, still it says "are you running under root"
[root@..... gard]# ./gard list
Couldn't open '/proc/device-tree/chosen/ibm,system-flash' FDT attribute to determine which flash device to use
Is your skiboot new enough to expose the flash through the device tree?
Do you have permission? Are you root?
Can't open MTD Device. Are you root?
[root@...... gard]#

pflash fails to read Macronix chips when using slow timings

In the rare event that flash chip is fully erased before pflash initialises, pflash will use conservative settings and timings.
For Macronix chips it appears these settings/timings permit correct writes but slightly corrupt reads which prevents pflash from verifying its writes causing aborts and rendering chips unwritable.

A fix is being refined.

This bug has existed since the very beginning of pflash.

I2C for POWER9

xscom-utils and gard tool build failure on OpenPower Machine.

xscom-utils and gard tool are both failed to build in this environment
habanero Hardware, PowerKVM 3.1.0 and below gcc level.

rpm -qf /bin/gcc
gcc-4.8.3-9.el7_1.ibm.3.ppc64le

cd skiboot/external/xscom-utils/
[root@localhost xscom-utils]# make 
    CC  xscom.o
    CC  version.o
  LINK  getscom
    CC  putscom.o
  LINK  putscom
    CC  getsram.o
    CC  sram.o
  LINK  getsram
[root@localhost xscom-utils]# ls
Makefile   getsram.c  sram.c  version.c  xscom.h
getscom.c  putscom.c  sram.h  xscom.c
[root@localhost xscom-utils]# cd ../gard/
[root@localhost gard]# make
cc -O2 -Wall -Werror -I. -c version.c -o version.o
cc -O2 -Wall -Werror -I. -c gard.c -o gard.o
cc -O2 -Wall -Werror -I. -c libflash/file.c -o libflash-file.o
cc -O2 -Wall -Werror -I. -c libflash/libflash.c -o libflash-libflash.o
cc -O2 -Wall -Werror -I. -c libflash/libffs.c -o libflash-libffs.o
cc -O2 -Wall -Werror -I. -c libflash/ecc.c -o libflash-ecc.o
cc -O2 -Wall -Werror -I. -c libflash/blocklevel.c -o libflash-blocklevel.o
    CC  common-arch_flash_common.o
    CC  common-arch_flash_powerpc.o
ld -r common-arch_flash_common.o common-arch_flash_powerpc.o -o common-arch_flash.o
ld: cannot find common-arch_flash_common.o: No such file or directory
ld: cannot find common-arch_flash_powerpc.o: No such file or directory
make: *** [common-arch_flash.o] Error 1

And tried with make clean also, hitting the same issue.

cd skiboot/external/xscom-utils/
 make clean
rm -rf *.[od] getscom putscom getsram
make
    CC  xscom.o
    CC  version.o
  LINK  getscom
    CC  putscom.o
  LINK  putscom
    CC  getsram.o
    CC  sram.o
  LINK  getsram
ls
getscom.c  getsram.c  Makefile  putscom.c  sram.c  sram.h  version.c  xscom.c  xscom.h

Object and executable files are not getting created.

FW Level
 Product Name          : OpenPOWER Firmware
 Product Version       : open-power-habanero-3b7310d
 Product Extra         :    buildroot-bc248fa
 Product Extra         :    skiboot-5.2.2
 Product Extra         :    hostboot-15bb028-9824b9f
 Product Extra         :    linux-4.4.9-openpower1-cbbfd90
 Product Extra         :    petitboot-v1.0.1-8f13d5f
 Product Extra         :    habanero-xml-5a2a541-cb4e251
 Product Extra         :    occ-19a3ebc
 Product Extra         :    hostboot-binaries-7f593a3
 Product Extra         :    c

Memory Frequency Control Through OPAL

Hi,

Any help would be appreciated!

I am trying to dynamically control the memory frequency through OPAL on a Power8 machine. This feature is mentioned (http://openpowerfoundation.org/press-releases/occ-firmware-code-is-now-open-source) to be available on this system. I noticed that dimm frequency interface has been added into this repo recently.

However, it seems to be only available on FSP-based Power8 machine. The Power8 machine we have right now is OpenPower version which does not have FSP but BMC. In this case, can we still control memory frequency through OPAL? or are there any other interface available on OpenPower version system to users?

Thank you very much for any suggestions!

Best regards,
Bo

Skiboot 5.4.1 - OCC got disabled.

from 'sdr elist' grepping for occ
...
OCC Active | 08h | ok | 210.0 | Device Disabled
...
The above is for single socket system, output from Habanero

In the case of two socket system, OCC Active 2 is disabled, output from SMC
...
OCC Active 1 | 08h | ok | 210.0 | Device Enabled
OCC Active 2 | 09h | ok | 210.1 | Device Disabled
...

Full list:
ipmitool -H HOSTNAME -I lanplus -U ADMIN -P admin sdr elist
DIMM Func 0 | 1Eh | ok | 32.0 | Presence Detected
DIMM Func 1 | 1Fh | ok | 32.1 |
DIMM Func 2 | 20h | ok | 32.2 | Presence Detected
DIMM Func 3 | 21h | ok | 32.3 |
DIMM Func 5 | 23h | ok | 32.5 |
DIMM Func 4 | 22h | ok | 32.4 | Presence Detected
DIMM Func 6 | 24h | ok | 32.6 | Presence Detected
DIMM Func 7 | 25h | ok | 32.7 |
DIMM Func 8 | 26h | ok | 32.8 | Presence Detected
DIMM Func 9 | 27h | ok | 32.9 |
DIMM Func 10 | 28h | ok | 32.10 | Presence Detected
DIMM Func 11 | 29h | ok | 32.11 |
DIMM Func 13 | 2Bh | ok | 32.13 |
DIMM Func 12 | 2Ah | ok | 32.12 | Presence Detected
DIMM Func 14 | 2Ch | ok | 32.14 | Presence Detected
DIMM Func 15 | 2Dh | ok | 32.15 |
DIMM Func 17 | 2Fh | ok | 32.17 |
DIMM Func 16 | 2Eh | ok | 32.16 | Presence Detected
DIMM Func 18 | 30h | ok | 32.18 | Presence Detected
DIMM Func 19 | 31h | ok | 32.19 |
DIMM Func 21 | 33h | ok | 32.21 |
DIMM Func 20 | 32h | ok | 32.20 | Presence Detected
DIMM Func 22 | 34h | ok | 32.22 | Presence Detected
DIMM Func 23 | 35h | ok | 32.23 |
DIMM Func 25 | 37h | ok | 32.25 |
DIMM Func 24 | 36h | ok | 32.24 | Presence Detected
DIMM Func 26 | 38h | ok | 32.26 | Presence Detected
DIMM Func 27 | 39h | ok | 32.27 |
DIMM Func 28 | 3Ah | ok | 32.28 | Presence Detected
DIMM Func 29 | 3Bh | ok | 32.29 |
DIMM Func 30 | 3Ch | ok | 32.30 | Presence Detected
DIMM Func 31 | 3Dh | ok | 32.31 |
CPU Core Func 1 | 3Eh | ok | 208.0 | Presence detected
CPU Core Func 2 | 3Fh | ok | 208.1 | Presence detected
CPU Core Func 3 | 40h | ok | 208.2 | Presence detected
CPU Core Func 4 | 41h | ok | 208.3 | Presence detected
CPU Core Func 5 | 42h | ok | 208.4 | Presence detected
CPU Core Func 6 | 43h | ok | 208.5 |
CPU Core Func 7 | 44h | ok | 208.6 | Presence detected
CPU Core Func 8 | 45h | ok | 208.7 | Presence detected
CPU Core Func 9 | 46h | ok | 208.8 |
CPU Core Func 10 | 47h | ok | 208.9 | Presence detected
CPU Core Func 11 | 48h | ok | 208.10 | Presence detected
CPU Core Func 12 | 49h | ok | 208.11 | Presence detected
CPU Func | 4Eh | ok | 3.0 | Presence detected
Membuf Func 0 | 4Ah | ok | 7.0 | Presence Detected
Membuf Func 1 | 4Bh | ok | 7.1 | Presence Detected
Membuf Func 2 | 4Ch | ok | 7.2 | Presence Detected
Membuf Func 3 | 4Dh | ok | 7.3 | Presence Detected
Host Status | 04h | ok | 35.0 | S0/G0: working
FW Boot Progress | 05h | ok | 34.0 | Unknown Progress
PCI | 5Bh | ok | 35.0 |
OS Boot | 5Ah | ok | 35.0 |
OCC Active | 08h | ok | 210.0 | Device Disabled
Boot Count | 50h | ok | 34.0 |
Ambient Temp | 0Ah | ok | 7.0 | 24 degrees C
CPU Diode Sensor | 0Bh | ok | 3.0 | 26 degrees C
Quick Power Drop | 0Dh | ok | 19.0 |
All PGood | 1Ch | ok | 19.0 | Power off/down
Checkstop | 0Ch | ok | 217.0 |
CPU Temp | 64h | ns | 3.0 | No Reading
Membuf Temp 0 | 65h | ns | 7.0 | No Reading
DIMM Temp 0 | 69h | ns | 32.0 | No Reading
DIMM Temp 1 | 6Ah | ns | 32.1 | No Reading
DIMM Temp 2 | 6Bh | ns | 32.2 | No Reading
DIMM Temp 3 | 6Ch | ns | 32.3 | No Reading
DIMM Temp 4 | 6Dh | ns | 32.4 | No Reading
DIMM Temp 5 | 6Eh | ns | 32.5 | No Reading
DIMM Temp 6 | 6Fh | ns | 32.6 | No Reading
DIMM Temp 7 | 70h | ns | 32.7 | No Reading
Membuf Temp 1 | 66h | ns | 7.1 | No Reading
DIMM Temp 8 | 71h | ns | 32.8 | No Reading
DIMM Temp 9 | 72h | ns | 32.9 | No Reading
DIMM Temp 10 | 73h | ns | 32.10 | No Reading
DIMM Temp 11 | 74h | ns | 32.11 | No Reading
DIMM Temp 12 | 75h | ns | 32.12 | No Reading
DIMM Temp 13 | 76h | ns | 32.13 | No Reading
DIMM Temp 14 | 77h | ns | 32.14 | No Reading
DIMM Temp 15 | 78h | ns | 32.15 | No Reading
Membuf Temp 2 | 67h | ns | 7.2 | No Reading
DIMM Temp 16 | 79h | ns | 32.16 | No Reading
DIMM Temp 17 | 7Ah | ns | 32.17 | No Reading
DIMM Temp 18 | 7Bh | ns | 32.18 | No Reading
DIMM Temp 19 | 7Ch | ns | 32.19 | No Reading
DIMM Temp 20 | 7Dh | ns | 32.20 | No Reading
DIMM Temp 21 | 7Eh | ns | 32.21 | No Reading
DIMM Temp 22 | 7Fh | ns | 32.22 | No Reading
DIMM Temp 23 | 80h | ns | 32.23 | No Reading
Membuf Temp 3 | 68h | ns | 7.3 | No Reading
DIMM Temp 24 | 81h | ns | 32.24 | No Reading
DIMM Temp 25 | 82h | ns | 32.25 | No Reading
DIMM Temp 26 | 83h | ns | 32.26 | No Reading
DIMM Temp 27 | 84h | ns | 32.27 | No Reading
DIMM Temp 28 | 85h | ns | 32.28 | No Reading
DIMM Temp 29 | 86h | ns | 32.29 | No Reading
DIMM Temp 30 | 87h | ns | 32.30 | No Reading
DIMM Temp 31 | 88h | ns | 32.31 | No Reading
CPU Core Temp 1 | 89h | ns | 208.0 | No Reading
CPU Core Temp 2 | 8Ah | ns | 208.1 | No Reading
CPU Core Temp 3 | 8Bh | ns | 208.2 | No Reading
CPU Core Temp 4 | 8Ch | ns | 208.3 | No Reading
CPU Core Temp 5 | 8Dh | ns | 208.4 | No Reading
CPU Core Temp 6 | 8Eh | ns | 208.5 | No Reading
CPU Core Temp 7 | 8Fh | ns | 208.6 | No Reading
CPU Core Temp 8 | 90h | ns | 208.7 | No Reading
CPU Core Temp 9 | 91h | ns | 208.8 | No Reading
CPU Core Temp 10 | 92h | ns | 208.9 | No Reading
CPU Core Temp 11 | 93h | ns | 208.10 | No Reading
CPU Core Temp 12 | 94h | ns | 208.11 | No Reading
Mem Proc0 Pwr | A1h | ns | 215.0 | No Reading
Mem Proc1 Pwr | A2h | ns | 215.1 | No Reading
Mem Proc2 Pwr | A3h | ns | 215.2 | No Reading
Mem Proc3 Pwr | A4h | ns | 215.3 | No Reading
Proc0 Power | A5h | ns | 215.4 | No Reading
PCIE Proc0 Pwr | A6h | ns | 215.8 | No Reading
IO A Power | A7h | ns | 215.12 | No Reading
IO B Power | A8h | ns | 215.13 | No Reading
Fan Power A | A9h | ns | 215.15 | No Reading
Storage Power A | AAh | ns | 215.17 | No Reading
Storage Power B | ABh | ns | 215.18 | No Reading
Mem Cache Power | ACh | ns | 215.22 | No Reading
GPU Power | ADh | ns | 215.23 | No Reading
Watchdog | 00h | ok | 0.0 |
Backplane Fault | 51h | ok | 7.0 |
System Event | 52h | ok | 1.0 |
Activate Pwr Lt | 53h | ok | 21.0 |
Ref Clock Fault | 54h | ok | 212.0 |
PCI Clock Fault | 55h | ok | 213.0 |
TOD Clock Fault | 56h | ok | 214.0 |
APSS Fault | 57h | ok | 215.0 |
CPU VDD Volt | 0Eh | ok | 3.0 | 0.93 Volts
CPU VDD Curr | 0Fh | ok | 3.0 | 22 Amps
PS Derating Fac | 58h | ok | 21.0 |
BIOS Golden Side | 5Ch | ok | 34.1 |
PSU Fault 1 | 5Dh | ok | 10.0 | Presence detected
PSU Fault 2 | 5Eh | ok | 10.1 | Presence detected
Fan 1 | B3h | ok | 29.3 | 14200 RPM
Fan 2 | B4h | ok | 29.3 | 14300 RPM
Fan 3 | B5h | ok | 29.3 | 14300 RPM
Fan 4 | B6h | ok | 29.3 | 14000 RPM
Fan 5 | B7h | ok | 29.3 | 14300 RPM
BMC Golden Side | 60h | ok | 34.1 |
Turbo Allowed | B8h | ok | 3.0 | State Asserted

hw/phb3: failure in phb3_init_hw() doesn't cause phb3_creset() to abort

phb3_init_hw() can fail for a variety of reasons, including DLP reset timeout, root complex config space init failure, etc.

If phb3_init_hw() is being invoked as part of a creset, phb3_creset() valiantly tries to ignore the failure and soldier on into doing an freset. Presumably the right thing to do is to check the return value and abort.

Long boot hang after "ipmi device interface"

Booting the latest code from github today on my Palmetto and noticed a very lengthy hang during the boot. Is this expected here?

[ 2.906206] ipmi message handler version 39.2
[ 2.907161] ipmi device interface
[ 241.304835] I[127423325658,3] BT: Expiring old messsage number 0x02
[127423385289,3] IPMI: Incorrect netfn 0x19 in response
NFO: task swapper/16:1 blocked for more than 120 seconds.
[ 241.305218] IPMI message handler: BMC returned incorrect response, expected netfn 7 cmd 8, got netfn 6 cmd 8
[ 241.305267] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x000000, prod_id: 0x0000, dev_id: 0x00)
[ 241.314995] random: nonblocking pool is initialized

Duplicate DT entries

With Skiboot v5.4.0, seeing the following duplicate errors

[ 89.499095662,3] DT: dt_attach_root failed, duplicate sensor@9
[ 89.500109636,3] DT: dt_attach_root failed, duplicate i2c-bus@2

While started testing with Trusted boot patches identified the above. I am not sure whether these entries are related to Trusted boot patches or not.
Please let me know what more details required.
Thanks!!

seeing device tree warnings on latest skiboot code

Host:
dtc -I fs -O dts /proc/device-tree > foo.dts
Warning (reg_format): "reg" property in /ibm,opal/flash@0 has invalid length (8 bytes) (#address-cells == 0, #size-cells == 0)
Warning (unit_address_vs_reg): Node /vpd/dimm@30000 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30002 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30004 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30006 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30008 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3000a has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3000c has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3000e has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30010 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30012 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30014 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30016 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@30018 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3001a has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3001c has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/dimm@3001e has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/processor@0 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/processor@0/cpu@8 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/processor@0/cpu@10 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/processor@0/cpu@18 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /vpd/processor@0/cpu@20 has a unit name, but no reg property

Petitboot
/ #
/ # dtc -I fs -O dts /proc/device-tree > foo.dts
Warning (reg_format): "reg" property in /ibm,opal/flash@0 has invalid length (8 bytes) (#address-cells == 0, #size-cells == 0)
/ #
/ #

reg_format warning is known issue, But unit_address_vs_reg is looks like a new one. And this is happening only on rhel and not on ubuntu or petitboot kernel.

systemsim perf question

Sorry if this is a bit OT, but in the systemsim config file for skiboot, the CPU frequency is set to 512, and the TB is also 512.
https://github.com/open-power/skiboot/blob/master/external/mambo/skiboot.tcl#L70

Yet when I run skiboot and a payload (I'm playing around with LE 64-bit code), the TB seems to be 1000-times slower. The TB just doesn't increment fast enough.

E.g. The 1000 should not be necessary, perhaps it's a factor of my environment (a not so new laptop). Are you guys aware of systemsim configuration options to make the timebase at least be approximately correct? Not atomic clock quality, just not 1000 or 10 or whatever times slower. Sorry again if this is OT.

                uint64_t now = mftb();
                while ((mftb() - now) * 1000 < (secs_to_tb(3))) {
                        printk("Now = %u.%u s\n",
                               ((mftb() - now) * 1000) / tb_hz,
                               ((mftb() - now) * 1000) % tb_hz);
                }