System Configuration can not be saved #27
Comments
|
Before rebooting please run |
|
Please refer to the attachment. Thank you. |
Petitboot is recognising the change and updating it, so the issue may be with a different layer. |
|
Skiboot is re-initialising the NVRAM partition on boot which would explain why the changes don't persist. When you "reboot" the system is that via a clean |
|
Because our BMC have issues for rebooting system. So we type "reboot" in petitboot, after BMC cut the system power and then we have to AC cycle to power on system again. |
|
Yep, that normally should be fine. I wonder if the new mbox interface is not flushing something in time. @cyrilbur-ibm or @sjitindarsingh do you have any ideas here? |
|
So it seems to me like either the write back to flash is failing under the hood and due to the fact that this is cached we're still seeing the changed in the nvram tool even if they weren't successful. Additionally I'm not sure of the state the daemon is in after all this power cycling etc. Can you run the following commands 3 times:
Commands: Please post the results stating which is which |
1. After running nvram --update-config and before powering off the host.root@zaius:# pflash -r /tmp/tmp -P NVRAM; hexdump -C /tmp/tmp 2. After powering off the host and before power cycling the bmcroot@zaius:# pflash -r /tmp/tmp -P NVRAM; hexdump -C /tmp/tmp 3. After power cycling the bmc and before powering the host back on again.root@zaius:# pflash -r /tmp/tmp -P NVRAM; hexdump -C /tmp/tmp |
|
Further investigation has determined that this is due to a bug in the mailbox daemon (mboxd) running on the bmc. When the nvram is updated it is erasing the skiboot partition and not writing it back again. This means that on every boot skiboot is detecting that the nvram in invalid and reinitialising it meaning that any changes aren't persistent across reboots. To fix this I recommend updating to the latest mailbox daemon available in OpenBMC which has a fix for this problem. The current state of your system means I believe it is impossible for nvram to be persistent through the skiboot boot process. |
|
Hi, After I tried using tag v1.99.5@OpenBMC to validate, I found it is good for saving changed configurations. |
Hi
We tried to modify "Timeout" for auto-boot setting in Petitboot System Configuration and choose "OK" on Zaius system.
After we "reboot" the system, the value we previously set in configuration page will not remain. It turns back to the default value.
We use this open-power/op-build@316265f to build zaius pnor image.
The text was updated successfully, but these errors were encountered: