From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Kennedy, Smith (Wireless Architect)" <smith.kennedy@hp.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
Daniel Dressler <danieru.dressler@gmail.com>,
"The CUPS developer list." <cups-devel@cups.org>
Subject: Re: [Printing-architecture] [cups-devel] Communication between IPP printer and "ipp" CUPS backend
Date: Wed, 16 Sep 2015 16:34:49 -0300 [thread overview]
Message-ID: <55F9C459.4080401@gmail.com> (raw)
In-Reply-To: <FB1D5086-D828-40DE-AD16-85293A1C66C4@hp.com>
On 09/15/2015 09:32 PM, Kennedy, Smith (Wireless Architect) wrote:
> Hi Till,
>
> Sorry for not replying earlier. Would you have any USB traces from Wireshark or a Beagle protocol analyzer, or logs, and/or the corresponding document files, so that we could try to repro it internally?
>
> Smith
As the problem always occurs after 4 or 5 successful jobs (all the jobs
being the same one) after turning on the printer, it seems that some
data is accumulating in some buffer of the printer which runs full after
a certain amount of activity making the printer blocking.
Perhaps it is data which the printer tries to send to the client without
being an answer to a request from the client but sent spontaneously by
the printer. ippusbxd does not pick up such data from the printer as it
waits for data from the printer only as an answer to a request which it
has sent.
Till
next prev parent reply other threads:[~2015-09-16 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 17:07 [Printing-architecture] Communication between IPP printer and "ipp" CUPS backend Till Kamppeter
2015-09-15 21:02 ` Till Kamppeter
[not found] ` <FB1D5086-D828-40DE-AD16-85293A1C66C4@hp.com>
2015-09-16 19:24 ` [Printing-architecture] [cups-devel] " Till Kamppeter
2015-09-16 19:34 ` Till Kamppeter [this message]
2015-09-21 19:53 ` Till Kamppeter
[not found] ` <36CB0E79-9A2E-44E4-AA39-A04101623303@hp.com>
2015-11-20 19:59 ` Till Kamppeter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F9C459.4080401@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cups-devel@cups.org \
--cc=danieru.dressler@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=smith.kennedy@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.