From owner-freebsd-bugs Fri Oct 12 14:40:15 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8A7F537B408 for ; Fri, 12 Oct 2001 14:40:01 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9CLe1O73414; Fri, 12 Oct 2001 14:40:01 -0700 (PDT) (envelope-from gnats) Received: from holly.dyndns.org (adsl-208-191-149-224.dsl.hstntx.swbell.net [208.191.149.224]) by hub.freebsd.org (Postfix) with ESMTP id E9FB937B406 for ; Fri, 12 Oct 2001 14:33:53 -0700 (PDT) Received: (from chris@localhost) by holly.dyndns.org (8.11.6/8.9.3) id f9CLYHH23981; Fri, 12 Oct 2001 16:34:17 -0500 (CDT) (envelope-from chris) Message-Id: <200110122134.f9CLYHH23981@holly.dyndns.org> Date: Fri, 12 Oct 2001 16:34:17 -0500 (CDT) From: Chris Costello Reply-To: Chris Costello To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: kern/31238: `hpijs' process hangs unkillably in `devbuf' state Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 31238 >Category: kern >Synopsis: `hpijs' process hangs unkillably in `devbuf' state >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Oct 12 14:40:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Chris Costello >Release: FreeBSD 4.4-STABLE i386 >Organization: FreeBSD Project >Environment: System: FreeBSD holly.calldei.com 4.4-STABLE FreeBSD 4.4-STABLE #1: Sun Oct 7 16:56:12 CDT 2001 chris@holly.calldei.com:/usr/obj/usr/src/sys/Holly i386 >Description: The GhostScript helper process, `hpijs' (for the DeskJet et. al. Hewlett-Packard printers), will hang after printing a page or two, and will not be killable: 20317 daemon -20 0 1488K 128K devbuf 0:00 0.00% 0.00% hpijs More information in the audit trail as I start adding debugging stuff to my system. So far, I _think_ I've deduced that it's a memory leak, as `ksp->ks_memuse' exceeding `ksp->ks_limit' is the only place where malloc() will sleep. I've currently not tracked down the source of the memory leak. >How-To-Repeat: Printing anything exceeding usually two or three pages using this driver will do the trick. >Fix: Not sure yet. Going to work on it. Input or verbal abuse (delivering at least helpful guidance or a solution) is welcomed! >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message