Re: Signal 4 while compiling 4.1.1

2000-10-02 Thread Jeff Wyman
Small note, as I wasn't thinking this far back when I wrote this.. I tracked stable since 3.3-RELEASE on a K6-2 333 ([EMAIL PROTECTED]), and never had such problems. Same good cooling - big fan/heatsink and conducting grease. On Mon, 2 Oct 2000, Jeff Wyman wrote: > Just a little side note, alth

Re: Signal 4 while compiling 4.1.1

2000-10-02 Thread Jeff Wyman
Just a little side note, although enough info might have been given out already... I have a K6-2/500 system (actually a 550@6x83) running at 2.2v core. It runs very fast and has tracked stable for a few months now, building about every week or so. I decided as of 4.1.1-R to stop this wasting of t

Re: Signal 4 while compiling 4.1.1

2000-10-01 Thread Roman Shterenzon
On Sun, 1 Oct 2000, Rodney W. Grimes wrote: > > > > Something is wrong with your system, check cabling, cooling and memory. > > I would change that to check, in order, cooling, cpu voltage setting, > memory and memory timing, power supply, and finally cabling. > > If you have one of the rare 2

Re: Signal 4 while compiling 4.1.1

2000-10-01 Thread Jeff Duffy
On Sun, 1 Oct 2000, Mike Smith wrote: >> I just compiled Gimp on the same system without any hitches. Other >> programs as well. I also ran memory tests and verified the >> motherboard's temperature via the BIOS and visually checked the fans. In response, I have checked as well. All three of

Re: Signal 4 while compiling 4.1.1

2000-10-01 Thread Mike Smith
> I just compiled Gimp on the same system without any hitches. Other > programs as well. I also ran memory tests and verified the > motherboard's temperature via the BIOS and visually checked the fans. > > It's my belief that within the last three weeks new code was inserted > into STABLE that

Re: Signal 4 while compiling 4.1.1

2000-10-01 Thread Corey G.
I just compiled Gimp on the same system without any hitches. Other programs as well. I also ran memory tests and verified the motherboard's temperature via the BIOS and visually checked the fans. It's my belief that within the last three weeks new code was inserted into STABLE that was never fu