Subject: Re: 3100 woes [was Re: libdl?]
To: None <port-pmax@NetBSD.ORG>
From: Benson L Chow <email@example.com>
Date: 04/24/1997 22:58:49
I lost my sole way to connect my 3100 so I can no longer do much with my
3100 if there are any major hacks to the code (plus the fact I have so
many things to do before graduation...)
Excerpts from internet.computing.netbsd.port-pmax: 24-Apr-97 3100 woes
[was Re: libdl?] by Jonathan Stone@DSG.Stanf
> What would be really useful to know is:
> * what disks people with problems are using
I am using a DEC RZ55.
> * whether they're using SCSI-2 cables and correct termination
It's hooked up via all DEC standard equipment.
> * what the last version of the kernel was which worked on
> their 3100, if any
1.2. I haven't had any luck with any kernel since the release version.
> * When the machine first started wedging
> * whether there's any indication that this is _really_
> a disk-access problem, or something else.
The guess currently is the disk subsystem - but there's no real way for
me to tell. It freezes only if large disk accesses are done, such as
cp -r source destination
with source being a large amount of data (e.g. X11 tree). Thus, I can
barely compile kernels (though some kernels seem to work better than
others, no idea why). Failure mode on all kernel versions is a frozen
machine, no further activity until hard reset.
Just some comments... I wish I had some time to hack this, would be fun :(