Git Product home page Git Product logo

pnor's People

Contributors

bofferdn avatar brs332 avatar cclaudio avatar chenduibm avatar crgeddes avatar cvswen avatar dcrowell77 avatar e-liner avatar erichte-ibm avatar ghf avatar jk-ozlabs avatar lf-luis avatar mabaiocchi avatar mikey avatar milesg-github avatar nagendraibm avatar ploetzma avatar popfuture avatar rjknight avatar sammj avatar sannerd avatar shakeebbk avatar shenki avatar spinler avatar stewartsmith avatar velozr avatar wghoffa avatar williamspatrick avatar

Stargazers

avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

brs332 gdhh wghoffa sannerd shenki hankchang scprek rjknight pragupta cvswen mikey sgupta2m ploetzma apopple dcrowell77 joeyang4 irarayjenkins ken1029 spinler maddy-kerneldev jk-ozlabs cyrilbur-ibm sammj bofferdn shakeebbk e-liner jahunsbe stewartsmith nagendraibm crgeddes popfuture ibm-op-release toshywoshy mine260309 ilyasmirnov91 milesg-github chendu1993 janani66 rajadas2 cclaudio naynajain lf-luis debmc wmc2021 katziejewski ibmzach

pnor's Issues

Current BOOTKERNEL physical size is not enough to transition to GCC 11.3.0 + GLIBC 2.3.6

My attempt to compile blackbird image with buildroot 2023.02 failed with following error:

ERROR: PnorUtils::checkSpaceConstraints: Image provided (/home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/openpower_pnor_scratch//zImage.epapr) has size (39321600) which is greater than allocated space (19660800) for section=BOOTKERNEL.  Aborting! at /home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/hostboot_build_images/PnorUtils.pm line 462.

see log for more details

and

TRACE: Done checkSpaceConstraints
TRACE: createPnorPartition:: 0
TRACE: createPnorImg:: 0
TRACE: createPnorPartition:: 67072000
TRACE: createPnorImg:: 67072000
TRACE:  fpart --target /home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/pnor/blackbird.pnor --partition-offset 67072000 --add --offset 0 --size 32768 --name BACKUP_PART --flags 0x0
TRACE:  fpart --target /home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/pnor/blackbird.pnor --partition-offset 67072000 --user 1 --name BACKUP_PART --value 6291456 --force
TRACE:  fpart --target /home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/pnor/blackbird.pnor --partition-offset 0 --add --offset 67072000 --size 32768 --name BACKUP_PART --flags 0x0
TRACE:  fpart --target /home/tle/Work/op-build/output/host/powerpc64le-buildroot-linux-gnu/sysroot/pnor/blackbird.pnor --partition-offset 0 --user 1 --name BACKUP_PART --value 6291456 --force
TRACE: fillPnorImage:: 67072000
fcp: errno : libffs.c(1165) : (code=27) __ffs_entry_truncate => File too large (errno=27)
fcp: errno : cmd_write.c(123) : (code=27) __write => File too large (errno=27)

So it's seems to me the physical size needs to get adjusted

p9Layouts: Need to mark read-only partitions with read-only flag

In the P9 layouts like the defaultPnorLayout_64.xml, the read-only flag is not being used to makr the read-only partitions. The read-only flag is needed by the BMC mailbox code to know if the partition should be written to.
The layout files already use the preserved flag to mark some partitions like NVRAM, so read-only would just be a different value from the same flag category. Reference: https://github.com/open-power/hostboot/blob/master/src/usr/pnor/common/ffs_hb.H

NVRAM partition falsely claims to use ECC

Listing available partitions with pflash displays the NVRAM partition as being ECC-corrected:

ID=18 NVRAM 01de2000..01e72000 (actual=00090000) [ECC]

But when dumping the partition itself this appears to not be the case, for example:

00000ff0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001000: 700c 1000 636f 6d6d 6f6e 0000 0000 0000  p...common......
00001010: 7065 7469 7462 6f6f 742c 626f 6f74 6465  petitboot,bootde
00001020: 7673 3d6e 6574 776f 726b 2064 6973 6b20  vs=network disk 
00001030: 616e 7920 0070 6574 6974 626f 6f74 2c77  any .petitboot,w
00001040: 7269 7465 3f3d 6661 6c73 6500 7065 7469  rite?=false.peti
00001050: 7462 6f6f 742c 7469 6d65 6f75 743d 3330  tboot,timeout=30
00001060: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001070: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00001080: 0000 0000 0000 0000 0000 0000 0000 0000  ................

AFAIK powerpc-utils (ie. the nvram utility) isn't ECC-aware, so perhaps it is easier to remove the ECC marker for the NVRAM partition.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.