Bug 269461
| Summary: | Boot problem with 7G of memory and PAE kernel - FC7 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Cokey de Percin <fdepercin> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7 | CC: | chris.brown, triage |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-17 02:16:36 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
Cokey de Percin
2007-08-30 21:22:09 UTC
Can you get the boot messages with serial console or netconsole? Created attachment 185391 [details]
dmesg file from a non PAE successful boot
Created attachment 185401 [details]
messages from non PAE successful boot
Created attachment 185411 [details]
a transcription of a formatted dump from the init failure
Created attachment 185421 [details]
transcription of the console abend without the dump patch
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. The problem persists. I'm currently up to kernel 2.6.22.5-76.fc7 and the PAE varient still hangs. Also, I still haven't been able to get the netconsole working in order to get you more information. I take it running: grep pae /proc/cpuinfo generates some output. It would also be good to know that memtest runs without issues. You can install it using memtest-setup as root which will give you the option in grub if you wish. I'm also wondering if adding mem=7168 to the boot parameters help? grep pae /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse I ran the memory test on the system for 8 hours or so before installing F 7 and it found and tested all 7 Gig. Also I have booted this system with M$ Advanced server and it finds/uses all 7 Gig so I don't think there's anything wrong with the hardware. The memory consists of 6 x 1G and 2 x 512M simms in two banks of 4 slots. Also, neither moving the memory around or changing or reducing it makes any difference. Further all the memory is the same type from the same manf. mem=7168M doesn't change anything. Still stops at the same place in the same manner. Hello Cokey, Any update on this bug? Are you still having the same issues with a 2.6.23-based kernel? If so could you test with 2.6.24 when it arrives and report back. Cheers Chris Closing as per previous comment. Please re-open if this is still an issue for you. Problem persists as of kernel 2.6.25-rc4 This one is really puzzling. Unfortunately bugs like this which affect specific hardware are really tricky to diagnose. Something that might be worth trying would be to try and build a vanilla kernel on this machine, and see if that works. I'm doubtful that your problem is due to any of the patches we add, but it's always a possibility, and it'd be good to rule that out. By doing so, we may then be able to get upstream developers interested in your bug. I don't know if you've built kernels by hand before. If not, I just wrote up a document explaining how to go about this at http://fedoraproject.org/wiki/BuildingUpstreamKernel If you have questions, I'll try to answer them and enhance the document where necessary. Let me know how you get on. This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |