Date: Thu, 9 Dec 1999 17:22:41 -0500 (EST) From: Pat Lynch <lynch@bsdunix.net> To: Ed Hall <edhall@screech.weirdnoise.com> Cc: Matthew Dillon <dillon@apollo.backplane.com>, "Jonathan M. Bresler" <jmb@hub.freebsd.org>, kris@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Message-ID: <Pine.BSF.4.05.9912091716450.10407-100000@bytor.rush.net> In-Reply-To: <199912062126.NAA30946@screech.weirdnoise.com>
next in thread | previous in thread | raw e-mail | index | archive | help
We are having a similar problem at the job I just started. A box meeting the exact specifications that Mike said caused the problem is essentially having the crap beat out of it as far as disk access and network activity (it might help to also say that this company is rather large in the scheme of things and would be a good example of how to use FreeBSD in a large enterprise environment). It is the only box out of alot of them having this problem, but its also the only one thats getting beat up as much as this one. it would be great if Peter could post his "patch" for the problem (how to migrate the -CURRENT driver into the 3.3 source) from what you say, Ed, it stands up a bit better than the current driver does, and can only probably get better. While this machine will probably be replaced with a different machine, FreeBSD is somewhat of a "Pride and Joy" here. -Pat -- Pat Lynch lynch@rush.net lynch@bsdunix.net Systems Administrator Rush Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9912091716450.10407-100000>