As Matthew Jacob wrote ...
> > As Matthew Jacob wrote ...
> > >
> > > Q'uelle strange- what I have... well, we'll see what my nightly build
> > > brings...
> >
> > Mine fell over in 'truss'. I already reported it to Marcel, looks
> > like something was changed in kdump/mkioctls, a script that 'truss' also
> > uses.
>
> Mine's still going (I start mine at 0430 PST8PDT, the update from
> freefall runs at 0107 PST8PDT)).... Nope, what a coincidence. It *just*
> finished. Went all the way through w/o errors on a buildworld.
My buildworld is OK now. Minor snag in the truss Makefile that Marcel
committed already.
> > > > It's an Aspen systems DEC Durango PC164 motherboard based system.
> >
> > Doesn't that one have ECC memory (refering to a previous post where
> > you theorised a bit on memory problems and sig-11s ;)
>
> It may or may not, but memory problems are typically detected pretty well
Right, that is my experience.
> on alphas and you'll get a 670 machine check if it was recoverable (which
> the PALcode has already done, except for TurboLaser if the memory problem
I don't have TL :)
Wilko
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message