Bug 214338
Summary: | Must specify RAM size to get kernel to boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew York <ayork> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | jonstanley, wtogami, yanmin.zhang |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-08 00:30:42 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: |
Description
Andrew York
2006-11-07 03:53:43 UTC
*** Bug 214339 has been marked as a duplicate of this bug. *** 1) Is kernel 2.6.18-1.2798.fc5 or 2.6.18-1.2798.fc6? 2) From the additional info, it is an i386 machine instead of ia64. Could you post your dmesg using mem=4G. Also if you have a digital camera, remove the "quiet" from the kernel cmdline and take a picture of the lockup. Did this work before 2.6.18-1.2798.fc5 or did it never work? (In reply to comment #2) > 1) Is kernel 2.6.18-1.2798.fc5 or 2.6.18-1.2798.fc6? Sorry FC6. Linux localhost.localdomain 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux > 2) From the additional info, it is an i386 machine instead of ia64. I guess processor may really be 32-bit, but I'm running 64 bit Linux and Vista without a problem. (well other than the one above) So it's a x86_64 machine, not an Itanium (IA64) machine. Sorry, my mistake. 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, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora! Closing per previous comment. If you can provide the requested information, please feel free to re-open this bug. |