From owner-freebsd-hackers Sun Nov 21 17:50:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 13A5914EFA for ; Sun, 21 Nov 1999 17:50:45 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA32364; Sun, 21 Nov 1999 20:50:38 -0500 (EST) Date: Sun, 21 Nov 1999 20:50:38 -0500 (EST) From: Bosko Milekic To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) In-Reply-To: <199911220127.UAA28430@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Nov 1999, Dennis wrote: !>Its a late 3.2-STABLE. so its not that old. Surely someone knows if !>something in this area was fixed or not? !> !>Since its a DMA lockup, how would you suggest that the informatoin about !>what instruction was executing be obtained? !> !>The nightmare of instability of 3.x continues whilst the braintrust flogs !>away at 4.x. Its really a damn shame. And why is 3.x so much slower than !>2.2.8? Will 4.0 be slower yet? !> !>DB !> Can you quantify how "slower" the 3.x code is? What's "slower" about it? A lot of people are willing to help, but providing no concrete information offers little possibility. In the mean time, did you happen to get a chance to reproduce the problem in 3.3-STABLE ? It appears from your description of the problem that's it somewhat tougher to debug, and knowing whether 3.3 remedies the problem can be of some help. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message