Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[witherspoon] petitboot does not retain boot order #58

Closed
manjo-git opened this issue Mar 11, 2019 · 11 comments
Closed

[witherspoon] petitboot does not retain boot order #58

manjo-git opened this issue Mar 11, 2019 · 11 comments

Comments

@manjo-git
Copy link

Witherspoon firmware version: witherspoon-IBM-OP9-v2.2-rc2-9.44_prod.pnor.squashfs.tar

After flashing this firmware, petitboot does not retain the boot order, it can retain the "network" device but nothing else. For example:

I added the following boot devices to the boot order.

Autoboot: ( ) Disabled
                 (*) Enabled

  Boot Order: (0) net: enP5p1s0f1 [mac: 08:94:ef:80:27:32]
                 (1) Any Disk device
                 (2) Any CD/DVD device

                 [ Add Device ]
                 [ Clear & Boot Any ]
                 [ Clear ]

I entered the petitboot shell and typed 'reboot'. After reboot, I checked the boot order I and see that other boot devices, except net were all removed from the boot order.

Autoboot: ( ) Disabled
                 (*) Enabled

  Boot Order: (0) net: enP5p1s0f1 [mac: 08:94:ef:80:27:32]

                 [ Add Device ]
                 [ Clear & Boot Any ]
                 [ Clear ]

It looks like a bug in petitboot since and it cannot keep boot devices like disk etc
@manjo-git
Copy link
Author

This issue is also observed when I install the witherspoon, it is able to deploy the OS, but on 1st boot after install the boot order does not contain any disk devices, but it does retain the net device.

@sammj
Copy link
Contributor

sammj commented Mar 12, 2019

This logic hasn't been touched recently in Petitboot so I wonder if something is happening under the covers. Could you try
a) Setting the boot order, then dropping to the shell and running pb-sos.
b) Rebooting and running pb-sos again.

With these two sets of logs we can see what's happening before and after the change.

@manjo-git
Copy link
Author

manjo-git commented Mar 12, 2019 •
edited

Please download the pb-sos files from http://people.canonical.com/~manjo/witherspoon/

This logic hasn't been touched recently in Petitboot so I wonder if something is happening under the covers. Could you try
a) Setting the boot order, then dropping to the shell and running pb-sos.

file: pb-sos.before.tar.gz

b) Rebooting and running pb-sos again.

file: pb-sos.after.tar.gz

With these two sets of logs we can see what's happening before and after the change.

@sammj
Copy link
Contributor

sammj commented Mar 13, 2019

Looks like you have an IPMI override set:
[15:51:16] IPMI boot device 0x01
where 0x01 = network.
You should see a message in the configuration screen about this, is it there? There should also be an option to clear it.

Otherwise you can clear it remotely via ipmitool -I lanplus -H host -U user -P pass chassis bootdev none

@manjo-git
Copy link
Author

manjo-git commented Mar 13, 2019 via email

@sammj sammj mentioned this issue Mar 20, 2019
Closed
@sammj
Copy link
Contributor

sammj commented Mar 21, 2019 •
edited

Finally had a chance to test on a Witherspoon with the latest O9x0 update and Petitboot appears to be handling IPMI overrides as expected (ie. clearing temporary ones on boot).
Can you do the steps you mentioned about (set order, clear override) and grab a pb-sos before booting? This is starting to sound like more of an OpenBMC problem.

@manjo-git
Copy link
Author

manjo-git commented Mar 21, 2019 via email

@manjo-git
Copy link
Author

Please find the pb-sos file here: http://people.canonical.com/~manjo/witherspoon/

@sammj
Copy link
Contributor

sammj commented Apr 7, 2019

A quick thought; when this happens if you select "Rescan" from the menu, do the missing devices appear?
If so this will be related to open-power/op-build#2756, and issue with eudev. If not, I'll need to dig into this deeper.

@manjo-git
Copy link
Author

I got petitboot firmware IBM-witherspoon-OP9-v2.2-9.56 from IBM, after installing this firmware I no longer have the problem of missing boot order.

@sammj
Copy link
Contributor

sammj commented Apr 9, 2019

Between those two builds we have these versions:

BM-witherspoon-OP9-v2.2-rc2-9.44
    op-build-v2.2-rc2-1-g951b4b0
    buildroot-2018.11.1-7-g5d7cc8c
    skiboot-v6.2.1
    hostboot-2fce6c0-p561d11b
    occ-12c8088
    linux-4.19.13-openpower1-p88886ff
    petitboot-1.10.1
    machine-xml-f7cffdb
    hostboot-binaries-hw021419a.930
    capp-ucode-p9-dd2-v4
    sbe-2e253ce
    hcode-hw022019a.930

and

IBM-witherspoon-OP9-v2.2-9.56
    op-build-v2.2-14-g29f0ba6
    buildroot-2018.11.3-12-g222837a
    skiboot-v6.2-176-g261ca8e779e5
    hostboot-0b3f4e1-p64efa43
    occ-12c8088
    linux-4.19.26-openpower1-p278e5c6
    petitboot-v1.10.2
    machine-xml-e3e9aef
    hostboot-binaries-hw021419a.930
    capp-ucode-p9-dd2-v4
    sbe-1410677
    hcode-hw031219a.940

Between v1.10.1 and v1.10.2 the only changes are related to boot messages and how versions are described, so nothing that would affect boot order. Perhaps instead something in Buildroot or Skiboot has been fixed. I'll have a look to see if we haven't missed something.

@sammj sammj closed this as completed Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@manjo-git @sammj