From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 6 14:03:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3334A37B401 for ; Wed, 6 Aug 2003 14:03:34 -0700 (PDT) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55B2643FB1 for ; Wed, 6 Aug 2003 14:03:33 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.9/8.12.8) with ESMTP id h76L3WEU071132; Wed, 6 Aug 2003 15:03:32 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Date: Wed, 06 Aug 2003 15:03:32 -0600 From: "Justin T. Gibbs" To: Dave Dolson , "'freebsd-scsi@freebsd.org'" Message-ID: <1787590000.1060203812@aslan.scsiguy.com> In-Reply-To: References: X-Mailer: Mulberry/3.0.3 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Swapping deadlock due to aic/scsi errors? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2003 21:03:34 -0000 > We have a reproducible bug characterized by the system > becoming unresponsive (but db may be entered). > System is based on FreeBSD 4.7 (i386) > Using the aic79xx scsi driver. If you are using the stock aic79xx driver found in 4.7, I would start by pulling in the latest 4.X aic79xx driver into your system. > I would like to add some debugging to detect the lost command > and possibly retry it. Can someone suggest where the lost > command is supposed to be detected, and where the retry is > supposed to occur. The "lost command" is supposed to be detected by the timeout handler in the ahd driver. The timeout handler just forces a bus reset which should cause the command to be returned to the SCSI layer and then retried. It's not clear to me why this might not be happening, but the ahd driver was relatively green in 4.7 and you may just be tripping over a known (and later corrected) bug manifesting itself in an unusual way. -- Justin