> 
> Good morning.
> 
>  >   probe(esp:0:6:1) timed out
>  >   probe(esp:0:6:1) timed out
>  >   probe(esp:0:6:1) timed out
> I got similar messges this morning.
> My disks are the following:
> 
> esp0 targ 0 lun 0: <MAXTOR  LXT-213S SUN02074.20> SCSI1 direct fixed
> sd0 at scsibus0: 202MB, 1310 cyl, 7 head, 45 sec, 512 bytes/sec
> esp0 targ 1 lun 0: <MAXTOR  LXT-213S SUN02074.20> SCSI1 direct fixed
> sd1 at scsibus0: 202MB, 1310 cyl, 7 head, 45 sec, 512 bytes/sec
> esp0 targ 2 lun 0: <MAXTOR  LXT-535S        8.73> SCSI1 direct fixed
> sd2 at scsibus0: 510MB, 1546 cyl, 11 head, 61 sec, 512 bytes/sec
> esp0 targ 3 lun 0: <FUJITSU M2694ES-512     8108> SCSI2 direct fixed
> sd3 at scsibus0: 1037MB, 1819 cyl, 15 head, 77 sec, 512 bytes/sec
> esp0 targ 4 lun 0: <FUJITSU M2694ES-512     8108> SCSI2 direct fixed
> sd4 at scsibus0: 1033MB, 1819 cyl, 15 head, 77 sec, 512 bytes/sec
> 
> When I use new kernel(I made it from the current this morning), those
> ``timed out'' messages appear at probing LXT-535S.
> ``esp0 targ 2 lun 0: ...'' was displayed, but at 2nd line, only ``sd2
> at scsibus0:'' was displayed. After this, I got ``timed out''
> messages. What is wrong?
> My old kernel which is compiled on Dec.15 doesn't have this problem.
> 

  I also have this problem, on a Sparc 4/330, and an sd2 target...
I have this problem with kernels around Jan 9 as well as current.
(compiled current last night)

I haven't been able to get CD9660 to work at all, and I have some 
strange mis-identification problems that I've mentioned before.
Any ideas?

   John Stone
   johns@cs.umr.edu