From owner-freebsd-usb@FreeBSD.ORG Thu Jan 27 11:50:28 2005 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C789416A4D7 for ; Thu, 27 Jan 2005 11:50:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F8843D2D for ; Thu, 27 Jan 2005 11:50:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0RBoPmZ054269 for ; Thu, 27 Jan 2005 11:50:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0RBoP6r054268; Thu, 27 Jan 2005 11:50:25 GMT (envelope-from gnats) Date: Thu, 27 Jan 2005 11:50:25 GMT Message-Id: <200501271150.j0RBoP6r054268@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Mikhail Teterin Subject: Re: kern/71155: [usb] misbehaving usb-printer hangs processes, causes panics X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mikhail Teterin List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 11:50:29 -0000 The following reply was made to PR kern/71155; it has been noted by GNATS. From: Mikhail Teterin To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/71155: [usb] misbehaving usb-printer hangs processes, causes panics Date: Thu, 27 Jan 2005 06:41:41 -0500 I'm seeing the same thing with a different system running 5.3-stable and a different HP printer. A freshly booted system prints fine, but after some uptime an attempt to print results in some commotion on the printer and a flood of messages like: Jan 26 12:19:32 aldan hpijs: unable to write to output, fd=6, count=4096: m Jan 26 12:19:32 aldan hpijs: unable to send DeviceStatus: m Jan 26 12:19:32 aldan hpijs: unable to write to output, fd=6, count=4096: m Jan 26 12:19:32 aldan hpijs: unable to write to output, fd=6, count=4096: m Jan 26 12:19:32 aldan hpijs: unable to send DeviceStatus: m (Indeed, hpijs is programmed to keep trying after a write(2) fails.) After some time, the whole machine panics -- even if I manage to kill the "offending" hpijs process. Could it be, that after some time it is harder for the driver to get memory and the shortage-handling code is broken? This is quite embarassing, actually. A simple print job to panic a server? -mi