From owner-freebsd-current@FreeBSD.ORG Fri Jul 3 17:29:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF508106564A for ; Fri, 3 Jul 2009 17:29:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.swip.net [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 1B42E8FC0A for ; Fri, 3 Jul 2009 17:29:45 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=BQeo18V-fugA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=8kQB0OdkAAAA:8 a=btfoDKtnj2lBV_FJ9zQA:9 a=T7Aa-naySfWFPN8LFeEA:7 a=BvayL-nRSsXDwiZb4KGQxTAOLl0A:4 a=9aOQ2cSd83gA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 529979622; Fri, 03 Jul 2009 19:29:42 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 3 Jul 2009 19:29:15 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <20090703172600.1971111e@baby-jane.lamaiziere.net> <200907031756.55253.hselasky@c2i.net> <20090703185233.4f7e4a65@baby-jane.lamaiziere.net> In-Reply-To: <20090703185233.4f7e4a65@baby-jane.lamaiziere.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200907031929.17327.hselasky@c2i.net> Cc: Patrick Lamaiziere Subject: Re: ulpt problem (USB_ERR_IOERROR) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 17:29:47 -0000 On Friday 03 July 2009 18:52:33 Patrick Lamaiziere wrote: > Le Fri, 3 Jul 2009 17:56:54 +0200, > > Hans Petter Selasky a =E9crit : > > Have you tried: > > > > usbconfig -u XXX -a YYY reset > > > > Does it help? > > No, it returns > # usbconfig -u 0 -a 2 reset > usbconfig: could not reset device: Input/output error > > Then ulpt detaches > ulpt0: at uhub0, port 1, addr 2 (disconnected) > ulpt_detach:653: sc=3D0xc317f000 > > > To me it looks like a problem about your printer USB firmware. Does > > it respond to: > > > > usbconfig -u XXX -a YYY dump_curr_config_desc > > > > After the first print job? > > Yes, after the first job: > > # usbconfig -u 0 -a 2 dump_curr_config_desc ugen0.2: vendor 0x04f9> at usbus0, cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON > > > Configuration index 0 > > bLength =3D 0x0009 > bDescriptorType =3D 0x0002 > wTotalLength =3D 0x0020 > bNumInterfaces =3D 0x0001 > bConfigurationValue =3D 0x0001 > iConfiguration =3D 0x0000 > bmAttributes =3D 0x00c0 > bMaxPower =3D 0x0001 > > Interface 0 > bLength =3D 0x0009 > bDescriptorType =3D 0x0004 > bInterfaceNumber =3D 0x0000 > bAlternateSetting =3D 0x0000 > bNumEndpoints =3D 0x0002 > bInterfaceClass =3D 0x0007 > bInterfaceSubClass =3D 0x0001 > bInterfaceProtocol =3D 0x0002 > iInterface =3D 0x0000 > > Endpoint 0 > bLength =3D 0x0007 > bDescriptorType =3D 0x0005 > bEndpointAddress =3D 0x0001 > bmAttributes =3D 0x0002 > wMaxPacketSize =3D 0x0040 > bInterval =3D 0x0000 > bRefresh =3D 0x0000 > bSynchAddress =3D 0x0000 > > Endpoint 1 > bLength =3D 0x0007 > bDescriptorType =3D 0x0005 > bEndpointAddress =3D 0x0082 > bmAttributes =3D 0x0002 > wMaxPacketSize =3D 0x0040 > bInterval =3D 0x0000 > bRefresh =3D 0x0000 > bSynchAddress =3D 0x0000 > > > It looks like there are some problems even with the first job (I missed > this point before). > > ulpt0: using bi-directional > ulpt_write_callback:220: state=3D0x0 actlen=3D0 > ulpt_write_callback:220: state=3D0x1 actlen=3D2889 > ulpt_write_callback:220: state=3D0x1 actlen=3D3023 > ... > ulpt_status_callback:352: error=3DUSB_ERR_STALLED > ulpt_write_callback:220: state=3D0x1 actlen=3D16384 > ulpt_write_callback:220: state=3D0x1 actlen=3D16384 At this point it looks like the firmware crashes, when the error code chang= es=20 from STALLED to IOERROR. Are you sure the .ps/.pcl file is not corrupt? > ... > ulpt_status_callback:352: error=3DUSB_ERR_IOERROR > ulpt_write_callback:220: state=3D0x1 actlen=3D16384 > ulpt_write_callback:220: state=3D0x1 actlen=3D16384 > ... > ulpt_status_callback:352: error=3DUSB_ERR_IOERROR > ulpt_write_callback:220: state=3D0x1 actlen=3D16384 > ulpt_write_callback:220: state=3D0x1 actlen=3D15970 > ulpt_status_callback:352: error=3DUSB_ERR_IOERROR > ulpt_status_callback:352: error=3DUSB_ERR_IOERROR > ulpt_status_callback:352: error=3DUSB_ERR_IOERROR > ... (ad eternam) > > If it can help, I can compare with FreeBSD 7.2. Yes, that might give some more clues. =2D-HPS