From owner-freebsd-scsi Fri Aug 29 14:35:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29837 for freebsd-scsi-outgoing; Fri, 29 Aug 1997 14:35:15 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29828 for ; Fri, 29 Aug 1997 14:35:12 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id OAA19967; Fri, 29 Aug 1997 14:34:43 -0700 (PDT) Date: Fri, 29 Aug 1997 14:34:43 -0700 (PDT) Message-Id: <199708292134.OAA19967@vader.cs.berkeley.edu> To: dufault@hda.com CC: scsi@FreeBSD.ORG In-reply-to: <199708281141.HAA07328@hda.hda.com> (message from Peter Dufault on Thu, 28 Aug 1997 07:41:12 -0400 (EDT)) Subject: Re: bus resets (was "NOT READY") From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Several adapters support SCSI_RESET to reset a specific target; * you can get at it through "scsi_reset_target(sc_link)". * You can start a unit with "scsi_start_unit(sc_link, flags)". * In all cases you will then have to hope the system goes into the retry * forever logic based on the "device in the process of coming ready". Thanks, but do you think you can write a short program to do that? I'm really not well-versed in the kernel stuff, you know. ;) Satoshi