From owner-freebsd-scsi Fri Nov 5 11:54:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 1A8D714D58 for ; Fri, 5 Nov 1999 11:54:16 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id MAA69413; Fri, 5 Nov 1999 12:43:02 -0700 (MST) Date: Fri, 5 Nov 1999 12:43:02 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911051943.MAA69413@narnia.plutotech.com> To: shaun@shamz.net Cc: scsi@FreeBSD.org Subject: Re: scsi bus errors X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19991105120951.C1083@shamz.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19991105120951.C1083@shamz.net> you wrote: [ I've reformatted your mail so it fits in 80 columns. This makes it much easier to read. ] > Hi, > > After reading the lists and trying about everything under the sun > to get the errors to abate, I am finally writing. The setup is > about the same as all the others with SCB timeout errors. ... > I left out the logs because they don't seem to have been more than > grounds for speculation about termination and such up until now. As far as I know, we've resolved all other "timeout" type errors with the ahc driver. This was only possible because the people having the problems gave detailed information about their setup and the errors that occurred. In other words, provide the output from 'dmesg' for the system having problems as well as the messages output by the driver when the errors occur and we'll see what we can do. Leave the determination of what is valuable information to the experts. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message