Bug 492569
Summary: | Segfault in loader while attempting static IP install | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | ||||
Component: | anaconda | Assignee: | Chris Lumens <clumens> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 11 | CC: | dcantrell, jturner, notting, pjones, rmaximo, tcallawa, vanmeeuwen+fedora | ||||
Target Milestone: | --- | Flags: | jlaska:
fedora_requires_release_note?
|
||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-07-29 03:29:23 UTC | Type: | --- | ||||
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
James Laska
2009-03-27 14:04:46 UTC
eu-addr2line tells me that 0x805229e is loader.c:1386, which is this: class = installMethods[validMethods[loaderData->method]].type I'm going to take a wild guess here that loaderData->method is invalid. Setting fedora_requires_release_note to document the behavior that when entering a static IP, should the server and path entered not be valid, there is a potential interaction bug when navigating Back to the installation method screen. This bug will manifest as a segfault. The work around is to reboot the system using a valid server and path. If this is only in the fallback case on bad input, is it truly a release blocker? Bill: I've set the fedora_requires_release_note? to document this behavior in the Fedora 11 release notes. Unless the fix is simple+straightforward, I suspect playing with loader at this stage would not be wise. Chris, should we keep this on bug#F11AnacondaBlocker ? Retesting against anaconda-11.5.0.55 and I'm not able to reproduce. Perhaps this is related to the uninitialized memory issue that notting addressed (bug#501757)? Or something may still be lurking. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Closing on the basis of comment #5. If we see this again, we can open it back up. |