Bug 1266985
Summary: | Patch 138 to grub2 breaks PXE booting in UEFI mode? | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Mike Mosley <jmmosley> | ||||
Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.1 | CC: | jmmosley, shubham.git, tomek | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-01-19 22:06:20 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Mike Mosley
2015-09-28 18:07:02 UTC
Can you try this with grub2-2.02-28 ? We've seen several bugs like this, and the patch you've found as the problem is actually the /fix/ for it on many hardware platforms, but there are a couple of other fixes for the same behavior as well. So there's a good chance the current build will behave differently. Peter, I would be happy to try it out, but I can't seem to locate that particular version. The latest I could find is 2.02-0.23. Where should I download that version from? Thanks, Mike Peter, I built 2.02-0.23 and tried it. Same results. I have not been able to find the version you referenced (grub2-2.02-28). Mike Created attachment 1082049 [details]
0.23 .. 0.29
So, is 28 was the current beta build for 7.2. If you don't have access to that, then the attached patch should get you the same thing from 0.23.
Ok, I checked the RHEL 7.2 Beta DVD and found 0.25. Still unable to find 0.28 anywhere. I'm not familiar with the format of the attachment you provided because I seldom do source code patching. After saving it as a raw unified diff, I attempted to split it into individual patches using splitpatch but I was unsuccessful. What is the magic for applying the file of patches provided in the attachment such that I can use it in the rpmbuild environment for 0.23 to get to 0.29? Well, after much confusion and some amusing attempts on my part, I finally got things to work using 0.23 and the attachment of patches (to bring it to 0.29). I eventually used 'splitdiff' to break the individual patches out of the attachment. In order to get 'rpmbuild' to like the patches, I had to remove a couple of proceeding characters on the lines in each file as well as remove 3 lines proceeding the From: lines. Otherwise, rpmbuild complained that there was no valid email in the patch. Next, I had to eliminate some of the patch files I generated with splitdiff as they were deemed 'empty' or 'not applicable' Here is a list of the patches I did get to apply: Applying: Reverse rpmvercmp return value (#1229329) Applying: efinet: memory leak on module removal Applying: efinet: cannot free const char * pointer Applying: Revert "efinet: memory leak on module removal" Applying: efinet: handle get_status() on buggy firmware properly Applying: ppc64le sync mkconfig to disk (#1212114) Applying: tcp: ack when we get an OOO/lost packet Applying: tcp: add window scaling support Applying: Be more aggro about actually using the *configured* network device. Applying: efinet: add filter for the first exclusive reopen of SNP Applying: Put the correct .file directives in our .S files. Applying: Make efi machines load an env block from a variable Applying: Make it possible to enabled --build-id=sha1 Applying: Add grub_qdprintf() - grub_dprintf() without the file+line number. Applying: Make a "gdb" dprintf that tells us load addresses. Anyway, it did actually compile, and I was able to test the resulting grubx64-efi file. And strangely enough, it worked! :-) I don't know if any of this information is useful or not. My goal is to provide you guys with enough info so that we can ensure RHEL 7.2 will have a grux64.efi that works for us. Mike |