USB colorlaserjet 5550 fails with invalid write_ecp_channel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HPLIP |
New
|
Undecided
|
Unassigned |
Bug Description
HPLIP 3.9.8
CUPS 1.3.9
We (i.e. Novell/Suse) investigate a currently non-public bug report
for Suse Linux Enterprise Server/Desktop 11:
https:/
Here a Color LaserJet 5550 (but perhaps other printers too)
connected as
hp:/usb/
does not print anything because it fails with error messages
in /var/log/messages
-------
... hp[30549]: io/hpmud/musb.c 216: invalid write_ecp_channel: Broken pipe
... hp[30549]: prnt/backend/hp.c 743: ERROR: cannot open channel PRINT
-------
Similar error messages occur for "hp-test" or "hp-testpage" like
-------
... python: io/hpmud/hpmud.c 632: invalid channel_write state
... python: io/hpmud/pml.c 461: GetPml channel_write failed ret=31
... python: io/hpmud/hpmud.c 613: invalid channel_close state
... python: io/hpmud/musb.c 216: invalid write_ecp_channel: Broken pipe
-------
It works fine if the generic CUPS 'usb' backend is used
(i.e. when the DeviceURI is 'usb://HP/...').
Therefore - from my non-USB-expert point of view - it looks similar to
https:/
for which we already filed this bug report:
https:/
First of all I would be interested in some information
whether or not both issues are singular special error cases
which happen for example only for a particular combination
of printer model and USB hardware in the computer
or whether the issues are a more general case.
Of course it does not happen in any case because
it works well for my HP LaserJet 1220 on my worksation
but I don't know how often such issues could happen.
Perhaps the 'hp' backend might be not yet sufficiently
robust against whatever kind of USB failures?
Or is the root cause perhaps in libusb (because
the 'hp' backend uses libusb but the CUPS 'usb' backend
in CUPS 1.3 uses the usblp kernel module)?
We have tried more than two different computers
with the same printer HP Color LaserJet 5550
so that the issue seems to be a more general issue
at least for this particular printer model.