On Fri, Jun 18, 1999 at 04:50:16AM -0700, Tony Hernandez wrote:
> Has anyone run accross this ? It seems like all my builds of anything
> crash atleast 15 times ..  compiling xemacs was a pain in my ass  cause
> I had to keep restarting  the compile  make ; make ; make ; make ...
> wtf ? This happened before in 1.3.2  and then quit happening ....   now
> im in 1.4 and this started happening again ..... I fear this is not
> NetBSD's fault for any reason and that it may be hardware .. any ideas
> folks ?
That's funny. A few days ago I had the same problem:

I've got a K6-2 300, that has run without problems for 6 months. Then
I overclocked it to 350MHz and it run flawless for another month.

Then I've bought new components, set up a new box, plugged in the old K6-2 
let it run setiathome (100% CPU-usage!), a nfs server, a personal squid and
some other stuff (still overclocked at 350MHz) and after 2 days of uptime
I thought this machine is "burned in" and stable.

But then I compiled a kernel, and on some large files I get the same error
(signal 11) wich has confused me alot.

I've upped the core voltage for 0.1V and now it's running absolutly perfect
for ~2 weeks. Maybe the other motherboard gives a slightly higher vcore,
or the power supply of the new box is not as stable...

gcc's signal 11 seems to be a quite good indication for hardware problems.

BTW: NetBSD's seti@home team needs more members:
http://setiathome.ssl.berkeley.edu/cgi-bin/cgi?cmd=team_lookup&name=netbsd
It would be a shame for NetBSD if we don't make it to the top 100...
-- 
Dies ist Thilos Unix Signature! Viel Spass damit.