From owner-freebsd-scsi Sun Nov 26 11:33:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 6BC0337B4C5 for ; Sun, 26 Nov 2000 11:33:56 -0800 (PST) Received: from nas1-128.mea.club-internet.fr (nas1-128.mea.club-internet.fr [195.36.139.128]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA12201; Sun, 26 Nov 2000 20:33:49 +0100 (MET) Date: Sun, 26 Nov 2000 19:34:00 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: John-Mark Gurney Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr problems (and amd) In-Reply-To: <20001126105441.34721@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Some VIA based chipset motherboards can mess-up a lot with your controller when some feature is enabled on the chipset. I donnot remember exactly the feature that makes problems (DMA problems), but it should have something to do with `cache streaming' or `PCI streaming'. Could you look into your mother-board set-up if a feature that resembles ` streaming' is enabled and then disable it. G=E9rard. On Sun, 26 Nov 2000, John-Mark Gurney wrote: > G=E9rard Roudier scribbled this message on Nov 26: > > I read your 2 messages, and the problems reported by the `ncr' driver > > seems to me rather due to flaws in the hardware than to the `ncr' itsel= f. > >=20 > > Could you describe the hardware you are using and what you are doing wi= th > > it. You also may check that it is properly configured in all its parts.= I > > mean, clockings, cabling, cooling, etc ... >=20 > ok... well, the hardware is a Tekram DC-390F. Attached hardware is: > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da4) > at scbus0 target 4 lun 0 (pass3,da2) >=20 > All are narrow except the Fujitsu. All are internal, using no special > addapters. Termination is turned on on both drives at the end of the > chain. Motherboard is a FICA VA-503+ VIA based chipset that is *NOT* > overclocked. As for cooling, nothing special, but the case is closed > and has two exhaust fans and one intake fan. When I upgraded from the > Advansys Ultra SCSI card, I didn't change internal cabling for the > three narrow devices (and I'd been running that for 9+ months). >=20 > The cable length on the narror part of the system might be a bit long, > so I plan on next crash replacing it with a cable that only has three > connectors for drives instead of the current five. Though the Tekram > manual lists a length of 3 meters for 4 devices or less, which I know > I'm less than, for the 1.5 meters (max of 8 devices) I'm probably pretty > close to. >=20 > Well, it also survived daily, but I did reduce the tags all above > mentioned drives to 16, which may have made a difference. But only > 16 tags is so few. :( >=20 > Thanks for any help you can provide. >=20 > --=20 > John-Mark Gurney=09=09=09=09Voice: +1 408 975 9651 > Cu Networking > =09"Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message