On Sep 19, 2005, at 6:16 PM, Pat Maddox wrote:
Happens in different spots, so I guess it's a hardware problem. But
what exactly am I looking for? Is it bad ram, a bad disk? How do I
find out what's messed up?
CPU cooling or bad memory are likely culprits.
Run memtest.org's checker overnight
On 9/19/05, Charles Swiger <[EMAIL PROTECTED]> wrote:
> On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote:
> >> The obvious question is: does it always fail at the same point? If
> >> not, then it's almost certainly a hardware problem. If it does, then
> >> a bit more information on your system would
On Sep 19, 2005, at 6:04 PM, Pat Maddox wrote:
The obvious question is: does it always fail at the same point? If
not, then it's almost certainly a hardware problem. If it does, then
a bit more information on your system would be needed, including how
you updated the ports skeletons, and whethe
On 19 Sep 2005 16:17:03 -0400, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Pat Maddox <[EMAIL PROTECTED]> writes:
>
> > I'm trying to upgrade my system, and the build of kdelibs always fails
> > because of some segmentation fault. I have absolutely no idea what
> > all this means, so I'll try to
