From owner-freebsd-current Sat Sep 19 23:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02319 for freebsd-current-outgoing; Sat, 19 Sep 1998 23:52:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02312 for ; Sat, 19 Sep 1998 23:52:56 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id AAA17429; Sun, 20 Sep 1998 00:52:26 -0600 (MDT) Message-Id: <199809200652.AAA17429@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: KATO Takenori cc: gibbs@plutotech.com, current@FreeBSD.ORG Subject: Re: [CAM] Broken tagged queuing drive? In-reply-to: Your message of "Sun, 20 Sep 1998 15:48:42 +0900." <19980920154842T.kato@gneiss.eps.nagoya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 00:45:59 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Justin T. Gibbs" wrote: > >> I believe I've found the cause of this panic. I would appreciate it if >> you could test to see if the next revision of aic7xxx.c survives the >> timeout. > >The panic went away. Does this mean that after the timeout the drive behaved normally (i.e. the system fully recovered)? I just want to ensure that the error recovery code is robust. >> My guess is that the SAMSUNG blows away other pending transactions when >> it sends a queue full message. You may want to try setting maxtags >> to a value that will avoid the queue full response (perhaps 32 or 31). > >The value 32 works without problem. I'll add the appropriate quirk entry. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message