Bug 21202
Summary: | Signal 9 during install of "dev" package | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | redhat-bugs |
Component: | anaconda | Assignee: | Brock Organ <borgan> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | redhat-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-02-21 00:15:09 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
redhat-bugs
2000-11-21 20:49:01 UTC
Most likely, the install kernel oopsed; that's pretty much the only way the installer gets SIGKILL. Hmmmm. There was no evidence of an oops on any of the VCs. What now? Passing to QA to reproduce. I don't mean to push, but any idea how long QA will take to reproduce? I only ask because I need to decide whether I can sit tight and wait or if I need to figure something else out. If you have any suggestions at all that I can do to help out please just let me know. hmmm ... this seems likely to be hardware specific, as I cannot reproduce the problem in our test lab using generic equipment ... what hardware do you have in your system ...? Bah! I hate that. The exact details of the machine can be found at http://www.e4me.com/infocentral/product_etower600is.html minus the [win]modem and add at least one Linksys LNE100TX, details at: http://www.linksys.com/products/product.asp?prid=31&grid=10 Mine are the version 4.1 cards, needing the updated tulip.o driver package from Donald Becker's netdriver package. unfortunately, we do not have this specific hardware in our test lab ... we have not seen this problem with similar class machines in our lab ... :( also, I have almost this machine @ home (a 500 Mhz celeron emachines for personal use), and though I've not done a kickstart install onto it, I've not had any other problems with installing Red Hat Linux 7 onto it ... do you also have this problem with an interactive (ie non-kickstart) install ...? Have you seen this problem occur similarly on different hardware ...? (I am wondering if this incident is not a single possibly faulty machine) No, an interactive install works just fine. I suspect that there is something about my kickstart recipie that is causing the barfage. Actually I think likely it has something to do with the part where I have the disk pre-partitioned and tell the kickstart what to do with those partitions rather than letting kickstart create them. What do you think of that hypothesis? Could you try having the installer allocate one of the partitions and see if it helps? But if the machine I am installing to has other OS(es) on it, along with some paritions that I want the installer to install into, how will it know not to write into the partitions of the other OS(es)? I solved it!! The problem is simply one of not enough memory. The machine I am installing onto only has 32MB of memory. You could not really have installed onto the same class of machine (memory plays heavily into replicating a "class" of machine IMHO) as you say above or you would have come across the same problem wouldn't you have? Anyway, I added a 128MB stick of memory and the install went fine. This seems to be only a Kickstart issue and not a general installer issue. Why? Because when used interactively, the installer notices that the amount of memory is low and requests that swap be mounted immediately to compensate. It would seem that the installer does not do the same during a kickstart. It should, no? Why not if you think it shouldn't? Is anything going to be done with the additional information I have provided? I have worked around the damn problem! Some acknowlegement of what permanent fixes will be put in place would be nice. For your original case you had 32M of RAM and 64M of swap? Yes, 32MB of memory, 64MB swap. > The problem is simply one of not enough memory. The machine I am installing
> onto only has 32MB of memory. You could not really have installed onto the
> same class of machine (memory plays heavily into replicating a "class" of
> machine IMHO) as you say above or you would have come across the same problem
> wouldn't you have?
You're right. I had more memory in the system (64 Mb) ... We are working to
have more efficient resource usages in future releases of anaconda ...
Don't be so quick to close the bug. :-) The interactive mode of the installer deals with this issue by mounting the swap partition very early in the install if it detects a low memory configuration. Why not have the kickstart mode of the installer do the same? Kickstart was designed for use on server machines primarily, which always have enough RAM to work. We do not plan to change this behavior at this time. |