From owner-freebsd-hackers Sat Nov 20 11:45:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BBC1F1508B for ; Sat, 20 Nov 1999 11:44:57 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id OAA19595 for ; Sat, 20 Nov 1999 14:44:58 -0500 (EST) Message-Id: <199911201944.OAA19595@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 20 Nov 1999 14:41:27 -0500 To: hackers@freebsd.org From: Dennis Subject: PCI DMA lockups in 3.2 (3.3 maybe?) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've run into a situation where, with heavy PCI bus traffic, freebsd 3.2 systems lock up. I havent tried it on 3.3 yet. The same scenarios do not cause the problem on the exact machine in both FreeBSD 2.2.8 and LINUX so it doesnt seem to be a hardware problem. The problem can be duplicated regularly by passing 80Mb/s of traffic through ethernet and serial devices and then doing a "find" to create excessive disk access. The 2.2.8 and LINUX systems continue to run normally while FreeBSD 3.2 hangs regularly. I'll test this in 3.3 shortly...has anything been done in this area? It seems to happen on passive backplace systems (although its more likely the chipsets used on SBCs)...my acer MB doesnt lock up with the same test. This problem has been duplicated on more than 1 system with completely different hardware. Any ideas? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message