Date: Fri, 3 Jul 2009 19:29:15 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Patrick Lamaiziere <patfbsd@davenulle.org> Subject: Re: ulpt problem (USB_ERR_IOERROR) Message-ID: <200907031929.17327.hselasky@c2i.net> In-Reply-To: <20090703185233.4f7e4a65@baby-jane.lamaiziere.net> References: <20090703172600.1971111e@baby-jane.lamaiziere.net> <200907031756.55253.hselasky@c2i.net> <20090703185233.4f7e4a65@baby-jane.lamaiziere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 03 July 2009 18:52:33 Patrick Lamaiziere wrote: > Le Fri, 3 Jul 2009 17:56:54 +0200, > > Hans Petter Selasky <hselasky@c2i.net> 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: <product 0x001a > 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 <no string> > 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 <no string> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907031929.17327.hselasky>