From owner-freebsd-hackers Wed Dec 15 13:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id 657B114BC6 for ; Wed, 15 Dec 1999 13:32:37 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id WAA23759; Wed, 15 Dec 1999 22:32:35 +0100 (CET) (envelope-from bd) To: freebsd-hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) From: Bjorn Danielsson Date: 15 Dec 1999 22:32:35 +0100 Message-ID: Lines: 47 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had similar problems (with 3.3-RELEASE), and yesterday I tried the ncr.c from 4.x but unfortunately it didn't help. My system crashed after 26 hours, with instruction pointer == random page fault address. The machine is a Compaq Proliant 1850R with 640M RAM and a "ThunderLAN" (tl) network interface. It's a newsfeed machine running Diablo 1.25. The load during the past 26 hours was about 12 Mbit/s in, 55 Mbit/s out constantly (on the tl0 device), and about 150 tps on each of the two disks. I have had great success running Diablo 1.14 on FreeBSD-2.2.5 on older hardware. Success, like 434 days of uninterrupted service until a power outage that occurred during a scheduled (!) test of the UPS system this summer. (Diablo actually saved our asses here back in 1997, since we had been relying on INN 1.5 until then... my kudos to Matt!) I'd very much like to repeat that success on the new machine, if possible. Matthew Dillon wrote: > > :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 > -- Björn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message