What could the problem be?

[David D. Lucas]

I have seen this kind of problem during kernel compiles when I had two 
SIMMs providing 256MB.  The first I bought with the mother board.  The 
second 128MB I bought about 2 years later.  Thy had problems because of 
different makers and specs.  I ended up trading them both in and getting 
a new motherboard with 512MB (2x256MB).

Lesson learned:  Always max out your memory when you buy the 
motherboard.  Keep your memory in sync, same type, same speed, same 
manufacture.

There is an memtest module you can boot up to test your memory.
Check out http://www.memtest86.com  and read their suggestions.

Best Wishes,
Dave


robb at bossleyfamily.com wrote:
> 
> 
> 
> Just to give an update.  It does appear to be something that is going
> wrong with the processor, motherboard, or hard drive setup.  I was able to
> unzip the bz2 kernel with bunzip2 first, but in compiling, I got
> segmentation faults.  It would run for a while without any errors, and
> then a segmentation fault would occur.  I don't know if it has something
> to do with the software raid that I have running, or if it is just a
> hardware issue.  Any ways to check this problem and narrow it down?
> 
> 
>>Robb Bossley wrote:
>>
>>>I have an older computer which I have utilized for the past couple of
>>>years.  Recently, I reinstalled Linux on it for the Nth time, this time
>>>utilizing the fact that I have two scsi drives and making all but one
>>>partition part of a RAID array.
>>>
>>>My question is this.  I have tried to copy the latest kernel (2.6.6) in
>>>bz2 form onto this computer, both from my usb storage device and from a
>>>one time writeable disk.  Each copies just fine.  However, when I go to
>>>untar it (tar -xjvf), I get a complaint that the headers?? for the bz2
>>>format are corrupted.  The odd thing is that each time was from a
>>>different download, and the downloads are fine because they work on
>>>other computers when unzipped just fine.
>>>
>>>What would this indicate, and is there any way to fix the problem?  I
>>>suspect a failing hard drive may be the culprit, but I'm not sure.  Is
>>>there a good way to test the harddrives?  All I want to do is upgrade
>>>the kernel.
>>>
>>>Thanks,
>>>
>>>Robb
>>
>>I had an Athlon 700 that developed this problem.  I suspect that it was
>>the processor, or possibly the motherboard.  Everything else I had
>>swapped out.  I could make the problem worse by doing processor
>>intensive tasks such as ripping mp3s.  It also would fail while
>>compiling the kernel and a simple restart of the compile would go
>>further and so on until it was done.  I underclocked it and used it for
>>another 6 months and it started happening again.  I sold it on ebay with
>>full disclosure.
>>
>>Judd
>>_______________________________________________
>>colug mailing list
>>colug at colug.net
>>http://www.colug.net/mailman/listinfo/colug
>>
> 
> 
> _______________________________________________
> colug mailing list
> colug at colug.net
> http://www.colug.net/mailman/listinfo/colug
> 

-- 

+------------------------------------------------------------+
| David Lucas                      mailto: ddlucas @ lse.com |
| Lucas Software Engineering, Inc.   (740) 964-6248 Voice    |
| Unix,Java,C++,CORBA,XML,EJB        (614) 668-4020 Mobile   |
| Middleware,Frameworks              (888) 866-4728 Fax/Msg  |
+------------------------------------------------------------+
| GPS Location:  40.0150 deg Lat,  -82.6378 deg Long         |
| IMHC: "Jesus Christ is the way, the truth, and the life."  |
| IMHC: "I know where I am; I know where I'm going."    <><  |
+------------------------------------------------------------+

Notes: PGP Key Block=http://www.lse.com/~ddlucas/pgpblock.txt
IMHO="in my humble opinion" IMHC="in my humble conviction"
All trademarks above are those of their respective owners.