From owner-freebsd-scsi Mon Jul 24 11:48:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 55ECE37BCB5 for ; Mon, 24 Jul 2000 11:48:10 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA17284; Mon, 24 Jul 2000 12:47:54 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007241847.MAA17284@pluto.plutotech.com> To: "NandaKumar P.K." Cc: scsi@FreeBSD.org Subject: Re: System panic with new HBA driver Date: Mon, 24 Jul 2000 12:48:40 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000629120911.22792.qmail@web1904.mail.yahoo.com> you wrote: > Hi, > > I am in the process of testing all the error > conditions of my FreeBSD 3.4 driver for the HBA. I > have 4 partitions on the Fibre Channel disk and a copy > is done from one partition to other. Now if remove > the disk when this is going on the firmware reports > timeout error and i report back the CAM_CMD_TIMEOUT > status. Now after sometime system comes with a sync > cache command and i report the same status > CAM_CMD_TIMEOUT for this command also. After this > system panic. Is there any way to avoid this condition > ? Since the disks are hot swapable this may be > condition i can expect in the real situation. If a device goes completely away, you should return CAM_SEL_TIMEOUT. That doesn't explain the panic in the sync cache code. Have you bothered to debug why the system panics? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message