From owner-freebsd-hackers Mon Dec 6 12:41: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id ED088152B9; Mon, 6 Dec 1999 12:41:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA72445; Mon, 6 Dec 1999 12:40:59 -0800 (PST) (envelope-from dillon) Date: Mon, 6 Dec 1999 12:40:59 -0800 (PST) From: Matthew Dillon Message-Id: <199912062040.MAA72445@apollo.backplane.com> To: Ed Hall Cc: "Jonathan M. Bresler" , kris@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912062022.MAA30052@screech.weirdnoise.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've confirmed that neither problem exists in 4.0. There are ample :work-arounds, both hardware and software, including just not using 3.3. :No fixes, though, just work-arounds... Workarounds for the NCR/FXP :issue included: : :1) Using 2.2.8 (4.0 isn't a production option). :2) Using a different NIC (a Tulip worked fine). :3) Using a different SCSI adapter (Adaptec, as Matt suggested, works fine). :4) Using a different SCSI driver (Peter managed to get a driver from 4.0 : hooked up under 3.3, and it survived two days of torture that would : have toasted things within an hour using the stock driver; you'll have : to ask him for details). Ed, this is great stuff! Are you sure about #4? Is that the same ncr.c driver or something else? There are only a few differences between the 3.x and 4.x /usr/src/sys/pci/ncr.c drivers. Which Peter, Peter Wemm? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message