From owner-freebsd-scsi Sun Mar 3 13:14:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 91C3F37B402 for ; Sun, 3 Mar 2002 13:14:37 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g23LFnI02625; Sun, 3 Mar 2002 14:15:49 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203032115.g23LFnI02625@aslan.scsiguy.com> To: "Matthew N. Dodd" Cc: =?ISO-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI driver problem: 'sym' fails, 'ahc' works. In-Reply-To: Your message of "Sun, 03 Mar 2002 16:06:40 EST." <20020303160107.S95839-100000@sasami.jurai.net> Date: Sun, 03 Mar 2002 14:15:49 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> You could also hack the driver source for it to accept the condition, >> but I would not be happy to help you for that given that the firmware >> bug you have been told about is likely the cause. > >Gee, thats helpful. > >I could also switch to hardware whose driver correctly interoperates with >my hardware. Its not really clear to me why one driver works and the other does not. Both should be flagging the overrun as an error. Perhaps in 3.4, the ahc driver was broken in this regard? Does a more recent ahc driver still work? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message