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.

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

Fix for 'error:unrecognized number' when booting ISO on PPC #1978

Merged
merged 1 commit into from Dec 6, 2018

Conversation

rmetrich
Copy link
Contributor

@rmetrich rmetrich commented Nov 23, 2018

Relax-and-Recover (ReaR) Pull Request Template

Please fill in the following items before submitting a new pull request:

Pull Request Details:
  • Type: Bug Fix

  • Impact: Low

  • Reference to related issue (URL): No issue created

  • How was this pull request tested? Not tested, I don't have the hardware for now, please may someone with hardware test.

  • Brief description of the changes in this pull request:

Issue is caused by incorrect, according to PAPR specification,
bootinfo entity parsing code in grub2.

In PAPR spec "B.4.1.6.1 Bootinfo Entities" partition and path
separator (,) is optional and if not present bootinfo may be
treated as directory and filename components unless it begins
with number:

  &device;:[&partition;][,]&directory;&filename;

If (,) is missing and directory begins with a hexadecimal number
GRUB2 treats this as partition number immediately followed by a
directory/filename.

Note that with (,) present in bootpath issue isn't in the case
as GRUB2 returns empty string for GRUB_PARSE_PARTITIONS. This
effectively meaning that GRUB2 code requires (,) as mandatory.

This is a GRUB2 bug, but until it is fixed, we can make the
message disappear by specifying a comma in bootinfo.txt.

Issue is caused by incorrect, according to PAPR specification,
bootinfo entity parsing code in grub2.

In PAPR spec "B.4.1.6.1 Bootinfo Entities" partition and path
separator (,) is optional and if not present bootinfo may be
treated as directory and filename components unless it begins
with number:

  &device;:[&partition;][,]&directory;&filename;

If (,) is missing and directory begins with a hexadecimal number
GRUB2 treats this as partition number immediately followed by a
directory/filename.

Note that with (,) present in bootpath issue isn't in the case
as GRUB2 returns empty string for GRUB_PARSE_PARTITIONS. This
effectively meaning that GRUB2 code requires (,) as mandatory.

This is a GRUB2 bug, but until it is fixed, we can make the message disappear by specifying a comma in bootinfo.txt.

Signed-off-by: Renaud Métrich <rmetrich@redhat.com>
@jsmeix jsmeix added the enhancement Adaptions and new features label Nov 23, 2018
@jsmeix jsmeix added this to the ReaR v2.5 milestone Nov 23, 2018
@jsmeix
Copy link
Member

jsmeix commented Nov 23, 2018

@schabrolles
I assigned this one completely to you
because I cannot help with PPC booting issues.

Copy link
Member

@gdha gdha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The explanation looks fine to me to accept the PR

@jsmeix
Copy link
Member

jsmeix commented Dec 5, 2018

@schabrolles
if you have currently no time for an expert review,
I would like to merge it "as is" tomorrow.

@rmetrich
Copy link
Contributor Author

rmetrich commented Dec 5, 2018

@schabrolles It's as simple as making an ISO and booting it :-)

@schabrolles
Copy link
Member

Hi team, I'm currently testing it ... Sorry for the delay, as you say I'm a bit overloaded and I've completely forgotten to test it.
I come back to you later this day.

Copy link
Member

@schabrolles schabrolles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me ... Tested on RHEL 7.4 ppc64le.

@rmetrich Sorry for the delay, your test also allows me to find a bug (#1997) in usr/share/rear/output/ISO/Linux-ppc64le/800_create_isofs.sh

@jsmeix jsmeix merged commit d1435fb into rear:master Dec 6, 2018
@jsmeix jsmeix added fixed / solved / done bug The code does not do what it is meant to do and removed enhancement Adaptions and new features labels Dec 6, 2018
@jsmeix
Copy link
Member

jsmeix commented Dec 6, 2018

@rmetrich
thank you for the bug fix.

@schabrolles
thank you for verfication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The code does not do what it is meant to do fixed / solved / done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants