Bug 60543
Summary: | install/upgrade RH5.2->RH7.2 fails randomly with "abnormal termination" during package installation | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew L. Martin <mlm> |
Component: | installer | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:48:31 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
Matthew L. Martin
2002-03-01 15:46:32 UTC
Signal 11s are usually a sign of hardware issues and the 2.4 kernel pushes the hardware much harder than earlier kernels. Could you try running memtest86 on your machine and see if that helps? Also, what sort of hardware is this on? Signal 11 happens about 1 in every 10 attempts to upgrade/install. I will run memtest86 if you tell me where it is and how to use it. I can't find it on any of the RH cdroms or the installed system and there is no man page for it. The details of the hardware and other information that might be of use to you is filed under support ticket 199932. You will find there that replacing all of the system memory with PC-133 didn't change the installation behavior. The work around was to use a 80GB disk as the installation disk instead of the 8GB maxtor drives that supported RH 5.2. You can find memtest86 http://www.teresaudio.com/memtest86/. As to the hardware configuration, since I'm in development and not in support, I do not have access to the support database, thus it would be helpful if you could add the hardware information to this bug report. Closing due to inactivity, please reopen if you contine to have problems. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |