From owner-freebsd-scsi Tue Aug 11 23:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29571 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 23:42:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29565 for ; Tue, 11 Aug 1998 23:42:51 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130] (may be forged)) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id CAA05021 for ; Wed, 12 Aug 1998 02:42:26 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <35D13957.D52AC90D@pubnix.net> Date: Wed, 12 Aug 1998 02:42:31 -0400 From: Alain Hebert Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Re: Heavy CAM Problems... References: <199808111906.NAA06851@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (Just in case... I'm not native english some part are more understandable if you read-it as it sound!) SOLVED! (Or at least isolated...) That's what is happening... The new cables (U2W: The one with a terminator and with all the wire independently connecter to the connector (but still in serial fashion) ) are kinda having quite a ride on EMI... Yeap, your PC emit like a small Radio station! So you have to make sure where you route the cable throughout the casing. Like, Justin said: that the Adaptec Guys thinks it hardware... Some timing or access sequence were surely changed between 0520 and 0712 and made that problem appear more frequently. So a good SCSI hygiene and good posture (don't route the cable around the power, but near the casing following a single direction, not to pinch or apply stress to the cable or wire...) might generally solve the problem. (This can explain why some got 0x17d and others 0x17e... I was re-arranging it tonight when I start getting 0x2!) So, I'm mailing from a functional 0712 installation with a 3.0-current kernel (but I still have the patch Justin send us... Will see without it tomorrow, OK!) Have fun with your 3.0-19980716-CAM system. (I will for sure!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message