From owner-freebsd-scsi Tue Apr 13 3:14:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id E4E5314A09 for ; Tue, 13 Apr 1999 03:14:15 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-146.ix.netcom.com [209.109.232.146]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id DAA14420 for ; Tue, 13 Apr 1999 03:12:04 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id DAA47254; Tue, 13 Apr 1999 03:10:41 -0700 (PDT) Date: Tue, 13 Apr 1999 03:10:41 -0700 (PDT) Message-Id: <199904131010.DAA47254@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: scsi@freebsd.org Subject: timed out while idle? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Justin, Ken and others, What exactly does "timed out while idle" mean? We're still seeing these stuff from time to time: === Apr 1 18:34:47 m0 /kernel: (da44:ahc2:0:12:0): SCB 0x30 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 1 18:34:47 m0 /kernel: SEQADDR == 0x8 Apr 1 18:34:47 m0 /kernel: SSTAT1 == 0xa Apr 1 18:34:47 m0 /kernel: (da44:ahc2:0:12:0): Queuing a BDR SCB Apr 1 18:34:47 m0 /kernel: (da44:ahc2:0:12:0): Bus Device Reset Message Sent Apr 1 18:34:47 m0 /kernel: (da44:ahc2:0:12:0): no longer in timeout, status = 34b Apr 1 18:34:47 m0 /kernel: ahc2: Bus Device Reset on A:12. 1 SCBs aborted Apr 1 18:58:37 m0 sshd[28252]: log: Connection from 209.111.209.216 port 963 Apr 1 18:58:40 m0 sshd[28252]: log: RSA authentication for asami2 accepted. Apr 1 19:38:30 m0 sshd[1204]: log: Generating new 768 bit RSA key. Apr 1 19:38:30 m0 sshd[1204]: log: RSA key generation complete. Apr 2 13:43:27 m0 /kernel: (da33:ahc2:0:1:0): SCB 0x86 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 2 13:43:27 m0 /kernel: SEQADDR == 0x8 Apr 2 13:43:27 m0 /kernel: SSTAT1 == 0xa Apr 2 13:43:27 m0 /kernel: (da33:ahc2:0:1:0): Queuing a BDR SCB Apr 2 13:43:27 m0 /kernel: (da33:ahc2:0:1:0): Bus Device Reset Message Sent Apr 2 13:43:27 m0 /kernel: (da33:ahc2:0:1:0): no longer in timeout, status = 34b Apr 2 13:43:27 m0 /kernel: ahc2: Bus Device Reset on A:1. 1 SCBs aborted Apr 2 14:58:03 m0 /kernel: (da32:ahc2:0:0:0): SCB 0x75 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 2 14:58:03 m0 /kernel: SEQADDR == 0x8 Apr 2 14:58:03 m0 /kernel: SSTAT1 == 0xa Apr 2 14:58:03 m0 /kernel: (da32:ahc2:0:0:0): Queuing a BDR SCB Apr 2 14:58:03 m0 /kernel: (da32:ahc2:0:0:0): Bus Device Reset Message Sent Apr 2 14:58:03 m0 /kernel: (da32:ahc2:0:0:0): no longer in timeout, status = 34b Apr 2 14:58:03 m0 /kernel: ahc2: Bus Device Reset on A:0. 2 SCBs aborted === Some of these eventually lead to panics or hangs. These are the same IBM disks we asked about a while ago. === da34 at ahc2 bus 0 target 2 lun 0 da34: Fixed Direct Access SCSI2 device da34: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da34: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) === I traced the message to ahc_timeout() in aic7xxx.c but not being a kernel hacker myself I can't really tell where it's called from. Is this like one of those alarm clocks ("wake me up in 5msecs if nothing happens")? Also, I see 7 phases in case statements: === case P_DATAOUT: printf("in dataout phase"); break; case P_DATAIN: printf("in datain phase"); break; case P_COMMAND: printf("in command phase"); break; case P_MESGOUT: printf("in message out phase"); break; case P_STATUS: printf("in status phase"); break; case P_MESGIN: printf("in message in phase"); break; case P_BUSFREE: printf("while idle, LASTPHASE == 0x%x", bus_state); break; === Is there some place that explans roughly what these correspond to? The ones we see most often are P_BUSFREE, P_COMMAND and P_DATAIN. I see that you refer to Adaptec databooks in aic7xxx.reg but since we don't have those, any web page or other on-line documentation that we can refer to will be great. Thanks! Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message