Bug 527506
Summary: | F-12 - ppc64.img does not boot on IBM Power5 system | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | anaconda-maint-list, awilliam, dcantrell, jturner, pavan.naregundi, stickster, tony, vanmeeuwen+fedora |
Target Milestone: | --- | Flags: | clumens:
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-10-14 12:41:02 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: | |||
Bug Depends On: | |||
Bug Blocks: | 473303 |
Description
James Laska
2009-10-06 17:15:00 UTC
Isolated the time the ppc64.img no longer worked. FAIL - http://download.fedora.redhat.com/pub/fedora/linux/releases/test/12-Alpha/Fedora/ppc/os/images/netboot/ppc64.img FAIL - http://kojipkgs.fedoraproject.org/mash/rawhide-20090714/development/ppc/os/images/netboot/ppc64.img FAIL - http://kojipkgs.fedoraproject.org/mash/rawhide-20090707/development/ppc/os/images/netboot/ppc64.img FAIL - http://kojipkgs.fedoraproject.org/mash/rawhide-20090705/development/ppc/os/images/netboot/ppc64.img FAIL - http://kojipkgs.fedoraproject.org/mash/rawhide-20090704/development/ppc/os/images/netboot/ppc64.img FAIL - http://kojipkgs.fedoraproject.org/mash/rawhide-20090703/development/ppc/os/images/netboot/ppc64.img <!-- SOMETHING CHANGED --> PASS - http://kojipkgs.fedoraproject.org/mash/rawhide-20090702/development/ppc/os/images/netboot/ppc64.img PASS - http://kojipkgs.fedoraproject.org/mash/rawhide-20090630/development/ppc/os/images/netboot/ppc64.img PASS - http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/ppc/os/images/netboot/ppc64.img That's some excellent debugging, but unfortunately the change between those two trees was pretty huge: 20090702 - anaconda-11.5.0.53-1.fc12 20090703 - anaconda-12.0-1.fc12 I'll look into this a little more tomorrow. I looked at the changes a bit, and there is very little that has to do with ppc, and even less that has to do with netboot image creation. I'm suspecting more something else in the tree changed. It could also be the size of the images, as they increased in size by a number of megs on that day as well. Jlaska was going to get some help from PPC folks on that. Adding tonyb for additional insight. Tony, do you have any experiences to share that might be contributing the failure? (In reply to comment #0) > 0 > boot network:,\ppc\F-12-Alpha-ppc64.img <SNIP> > FILE: /ppc/F-12-Alpha-ppc64.img > FINAL Packet Count = 59157 > FINAL File Size = 30288142 bytes. > load-base=0x4000 > real-base=0x2000000 <SNIP> > FILE: /ppc/F-11-GOLD-ppc64.img > FINAL Packet Count = 51497 > FINAL File Size = 26366022 bytes. > load-base=0x4000 > real-base=0x2000000 It looks to me that the image is just too large to load with that real-base. Try the never ending dance of moving real-base around 0x6000000 (96Mb) should be sooo far away from load-base that it should work. But, having looked at the filesizes from: http://kojipkgs.fedoraproject.org/mash/rawhide-20090703/development/ppc/os/images/netboot/ The change was small :( Thanks Tony, setting real-base to 6000000 did the trick. 0 > printenv real-base -------------- Partition: common -------- Signature: 0x70 --------------- real-base 6000000 6000000 ok 0 > boot network:,\ppc\F-12-Alpha-ppc64.img ... Linux/PowerPC load: Finalizing device tree... using OF tree (promptr=06039a68) OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 2.6.31-0.125.4.2.rc5.git2.fc12.ppc64 (mockbuild.phx.redhat.com) (gcc version 4.4.1 20090807 (Red Hat 4.4.1-5) (GCC) ) #1 SMP Tue Aug 11 21:05:10 EDT 2009 Calling ibm,client-architecture...command line: http://pastie.org/648337 (full log) So what's the outcome here? Should this be documented somewhere? (In reply to comment #6) > Thanks Tony, setting real-base to 6000000 did the trick. > > 0 > printenv real-base > -------------- Partition: common -------- Signature: 0x70 --------------- > real-base 6000000 6000000 > ok > > 0 > boot network:,\ppc\F-12-Alpha-ppc64.img > ... > Linux/PowerPC load: > Finalizing device tree... using OF tree (promptr=06039a68) > OF stdout device is: /vdevice/vty@30000000 > Preparing to boot Linux version 2.6.31-0.125.4.2.rc5.git2.fc12.ppc64 > (mockbuild.phx.redhat.com) (gcc version 4.4.1 20090807 (Red Hat > 4.4.1-5) (GCC) ) #1 SMP Tue Aug 11 21:05:10 EDT 2009 > Calling ibm,client-architecture...command line: > > http://pastie.org/648337 (full log) > > So what's the outcome here? Should this be documented somewhere? I think documenting it in the release notes for each Redhat/Fedora release would be great. Also if it's not too hard adding a README to the images/netboot would be helpful. Of course netbooting yaboot is the "preferred" install method :) I see 2 RFE's coming out of this ... (In reply to comment #7) > I think documenting it in the release notes for each Redhat/Fedora release > would be great. Also if it's not too hard adding a README to the > images/netboot would be helpful. #1 - add a README file into the "images/netboot/" directly explaining the ppc[32|64].img. jkeating is cc'd and probably can offer input here. > Of course netbooting yaboot is the "preferred" install method :) #2 - add content to the Fedora 12 install guide outlining what these images are? I've filed bug#528495 (despite ppc becoming a secondary architecture in Fedora 13) to raise this issue with the docs group. I'm going to close this out as NOTABUG as far as anaconda's concerned, then, since we're not responsible for setting these values up. If I'm misunderstanding something here, please feel free to reopen. this doesn't seem like a common bugs issue, as it's - well - NOTABUG. seems, as jlaska suggested, more of an install guide thing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #10) > this doesn't seem like a common bugs issue, as it's - well - NOTABUG. seems, as > jlaska suggested, more of an install guide thing. Are the release notes or install-guide open to modifications for F12? I don't know, best check with the documentation team. stickster? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |