Bug 64704
Summary: | Attempt to rpmbuild kernel-2.4.18.src.rpm Exits with Seg Fault | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jason> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-05-09 21:35:44 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
Need Real Name
2002-05-09 20:18:05 UTC
This isn't an rpm problem. I'd guess it's a compiler problem, but, because you're saying that the bug is non-reproducible, it caould very well be a memory problem. Erm, how is it not a bug? If it's a problem with the compiler, then shouldn't it be assigned to the gcc guys? FWIW, I was able to compile 2.4.18 downloaded from kernel.org without difficulty, but the Red Hat version has patched applied that I need for my system. So, in any case, I'm pretty sure that the build tools are working well enough to build the 2.4.18 kernel, just not in the way that rpmbuild does it... I said it's not an *rpm* bug. I also said that -- because the bug is non-reproducible -- you need to check your hardware. Thats' what you're gonna hear from the kernel/gcc trolls, but, if you insist, off to the kernel for a 2nd opinion ... Try http://www.teresaudio.com/memtest86 on your memory chips. This *does* look like faulty memory or related hardware, from motherboard to cpu to chipset to fan... One thing to be aware of is that memtest86 doesn't find false positives (if it shows a memory problem, there really is a memory problem) but it DOES report false negatives (that is, just because memtest86 doesn't find a problem doesn't mean that there isn't a problem). Some memory problems only show up under DMA load, etc, which memtest86 doesn't test. |