On Wed, Oct 20, 1999 at 06:16:57PM -0700, Jonathan Stone wrote:
> 
> [... upgraded to 1.4.1 first]
> 
> >The result was a panic, same as before.
> 
> Okay. Then -current is probably busted on pmaxes.  It's very hard to

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.1.gz:Oct 13 12:59:05 sockdev /netbsd: panic: trap
messages.1.gz:Oct 13 12:59:06 sockdev savecore: reboot after panic: trap
messages.1.gz:Oct 14 08:39:34 sockdev /netbsd: panic: trap
messages.1.gz:Oct 14 08:39:34 sockdev savecore: reboot after panic: trap
messages.1.gz:Oct 14 08:55:07 sockdev savecore: reboot after panic: trap
messages.1.gz:Oct 14 12:08:26 sockdev savecore: reboot after panic: trap
messages.2.gz:Sep 30 10:06:07 sockdev /netbsd: panic: trap
messages.2.gz:Sep 30 10:06:08 sockdev savecore: reboot after panic: trap
messages.2.gz:Sep 30 22:47:59 sockdev /netbsd: panic: trap
messages.2.gz:Sep 30 22:47:59 sockdev /netbsd: panic: trap
messages.2.gz:Sep 30 22:48:00 sockdev savecore: reboot after panic: trap
messages.3.gz:Sep 29 03:20:27 sockdev /netbsd: panic: trap
messages.3.gz:Sep 29 03:20:28 sockdev savecore: reboot after panic: trap
messages.4.gz:Sep  5 06:48:35 sockdev /netbsd: panic: trap
messages.4.gz:Sep  5 06:48:36 sockdev savecore: reboot after panic: trap
messages.4.gz:Sep  5 10:06:05 sockdev /netbsd: panic: trap
messages.4.gz:Sep  5 10:06:06 sockdev savecore: reboot after panic: trap
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


- Erik