hi -

   Based on Chris' message I just re-sup'd and tried again with the 
change that went in esp.c yesterday.   the result is:

scsibus0 at esp0
esp0 targ 1 lun 0: <QUANTUM, P105SS 910-10-94, 8.9> SCSI1 0/direct fixed
sd0 at scsibus0: 100MB, 1019 cyl, 6 head, 33 sec, 512 bytes/sec
error... error... esp0: async
error... error... error... error... error... 

The system hangs after printing the 7th "error..." (L1-a will not
break it).   (Before it never stopped printing "error...")

Peter suggested doing a "probe-scsi" ... i tried it and it did 
not help.

   Also, for fun, I tried to boot today's current on a ss2 with
a single disk drive (SunOS reports it as: sd0 at esp0 target 3 lun 0
sd0: <Box Hill Systems 4DQ 425MB cyl 875 alt 2 hd 10 sec 95>).
The system does something about like:

sd0 at scsibus0 sd0(esp0:3:0): timeout
<prints a few more timeout messages>
sd0 cound not mode sense(4); using ficticious geometry
<starts timeouts for esp0:3:1, etc...>

(sorry I don't have the console on a serial line so I can't get the
exact output...)


   Question: considering the state of the current sparc esp SCSI system, 
is it useful to generate bug reports, or should people hold off on them 
until more work is done?   I am willing to generate more detailed bug
reports if they will be useful.

chuck

ps- fyi: pk has put the changes for the 4/110 processor in the tree!