On Fri, 22 Oct 1999, Simon Burge wrote:

=> Erik Bertelsen wrote:
=> 
=> > Well, not completely. My 5000/133 seems to run reasonably well with -current,
=> > although I've seen a few panics that I've no explanation for:
=> > 
=> >  zgrep panic messages*z
=> > [ ... ]
=> > messages.4.gz:Sep 22 09:06:56 sockdev savecore: reboot after panic: trap
=> > messages.5.gz:Aug 28 21:36:56 sockdev /netbsd: panic: trap
=> > messages.5.gz:Aug 28 21:36:57 sockdev savecore: reboot after panic: trap
=> > messages.5.gz:Sep  3 10:50:56 sockdev savecore: reboot after panic: trap
=> > messages.5.gz:Sep  4 17:06:48 sockdev savecore: reboot after panic: trap
=> 
=> Out of curiosity, how far back do your messages files go?  Is this a
=> problem that started appearing at the end of August, or is this when
=> your logs start?

FWIW, I'd posted on here at least twice---the first time going a ways
back---about -current regularly panicing my DECstation 3100.  It got so
bad, my "solution" was to regress back to the 1.4.1-release sources and
rebuild everything from there. :-(

I've never had any luck with post-1.4 -current on my DS3100.  It always
seems to panic after a while (under load?).  For example, I could never
get it to complete a "make build" because it would panic 1--2 hours
after the build started.

Cheers,

Paul.

e-mail: paul@gromit.dlib.vt.edu

"I don't live today; maybe tomorrow..."
	--- James Marshall Hendrix