On Tue, Jun 25, 2002 at 09:55:07PM +0200, Peter B wrote:
> 
>      Hi!
> 
> I got the following error that put a server of mine to a halt:
> Jun 24 00:39:32 lim /netbsd: sd2(esp0:2:0): esp0: timed out [ecb 0xf03a5270 (flags 0x3, dleft 800, stat 0)], <state 1, nexus 0x0, phase(l 10, c 100, p 3), resid 0, msg(q 0,o 0) >
> 
> Reboot didn't work. Only physical power cycling. The setup is a SS1+ with
> 7 scsi2 units.
> sd0 at scsibus0 target 0 lun 0: <HP, C2490A, 4020> SCSI2 0/direct fixed
> sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> sd2 at scsibus0 target 2 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> sd3 at scsibus0 target 3 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> sd4 at scsibus0 target 4 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> sd5 at scsibus0 target 5 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> sd6 at scsibus0 target 6 lun 0: <SEAGATE, ST11200N, 7906> SCSI2 0/direct fixed
> 
> Should I consider this as a hardware, kernel or a temporary glitch ..?
> (disk has worked ok for few mins now)

I got this on one machine here too. A power cycle got it back running (reboot
wasn't enouth), and is since 20 days. 

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--