i hope that it is ok to also ask an OpenBSD/pmax question here
(... there are currently only 3 pmaxen running OpenBSD/pmax two here
at me and one at a friend - so it's not worth to create an own
OpenBSD/pmax mailinglist and all the "hardcore" pmax i will find here
:-) - ok after having said that - my problem:

i have the system running here on two decstation's 2100 - it runs so
far really good but on one of the 2100 it really often hangs (simply
hangs - no crash - but i have to reset the machine) and this always
happens then i access the disks heavily - the other machine is'nt
crashing that often (but it has other disks) - i'm now wondering if
this is a hardware problem or do i miss something in OpenBSD/pmax (i
have it now a the state of NetBSD-current 961107 - at least the pmax
and the mips dir - which is in OpenBSD "merged" into the pmax dir) ?

can it be that one disk has failures which will result in such a
behaviour ? - if yes - how can i for instance scan for bad blocks or
what diagnostics can give me the 2100 console ?

if i remember right there was a bug in NetBSD/pmax which resulted in
scsi hangs - and you had do disable the cluster-read/write via sysctl
- was the fix for this inside the pmax/mips trees or was it outside ?
- if the last is true can someone (jonathan ?) please mail me the fix
?

what makes me a bit more wondering is that it runs very fine on the
3100 of the friend - he did a make build without crashes :-) ?

a lot of thanks in advance for any help

t

p.s.: jonathan i still have your conf-glue test code on my todo list
(to check if the rz at scsi id 5 & 6 also works on the 2100) - but i'm
very seldom here and i have to find an scsi cable for the zip drive
here again to test - but i'll test it :-)

-- 
  thomas graichen - graichen@rzpd.de graichen@OpenBSD.org graichen@FreeBSD.org

  perfection is reached, not when there is no longer anything to add, but when
      there is no longer anything to take away    antoine de saint-exupery