From owner-freebsd-current Sun Dec 2 11:10:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 28EF137B417 for ; Sun, 2 Dec 2001 11:10:49 -0800 (PST) Received: (qmail 2424 invoked from network); 2 Dec 2001 19:10:43 -0000 Received: from ken.yumyumyum.org (HELO there) (192.168.0.2) by dsl092-171-091.wdc1.dsl.speakeasy.net with SMTP; 2 Dec 2001 19:10:43 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Culver Reply-To: culverk@wam.umd.edu To: Alan Eldridge Subject: Re: parallel port i/o hogs cpu badly; is this normal? Date: Sun, 2 Dec 2001 14:10:58 -0500 X-Mailer: KMail [version 1.3.1] References: <20011202132001.A42382@wwweasel.geeksrus.net> In-Reply-To: <20011202132001.A42382@wwweasel.geeksrus.net> Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011202191049.28EF137B417@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't know if there's a way to stop this, but it's normal, whenever I use my Parallel port zip drive, I have similar problems. Ken On Sunday 02 December 2001 01:20 pm, you wrote: > I have an HP postsript laser (2100M) on a parallel intfc. > > [alane ~]$ uname -a > FreeBSD wwweasel.geeksrus.net 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Sun Oct > 28 04:44:34 EST 2001 > root@wwweasel.geeksrus.net:/usr/src-4.4-RELEASE/sys/compile/WWWEASEL i386 > > [alane ~]$ grep -i parallel /var/run/dmesg.boot > ppc0: at port 0x378-0x37f irq 7 on isa0 > > When I print a document that is heavy in graphics, it's large. > Multi-megabytes. That's expected 'cause postscript is verbose. > > But what surprises me is that copying that data to the parallel intfc burns > up an incredible amount of CPU. Until the document is printed, there's a > steady bg buzz of ~10% CPU use, with periods of 50% and even 100% CPU > utilization by the 'parallel'[1] process. The load is sufficient that it > locks out the mouse on X (interrupt blocking?). > > Anyone care to comment? Does this sound normal? Is there a way to reduce > the amount of CPU needed to drive the parallel port? > > Notes: > [1] /usr/local/libexec/cups/backend/parallel is the device interface using > by the print/cups package. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message