On Thu, 8 May 2008, Ilpo Järvinen wrote:
On Thu, 8 May 2008, Damon L. Chesser wrote:
> reran the print job with the correct kernel (for control reasons) and
> received
> the same results: tcp_frto=1 no print. tcp_frto=0 I can print. Attached
> is
> the output of tcpdump
>
> uname -r = 2.6.24
On Thu, 8 May 2008, Damon L. Chesser wrote:
Ilpo Järvinen wrote:
> SNIP
>
> Could you next try with tcp_frto set to 1, if my theory proves to be
> correct, it too should be "enough" to fix the problem (in this particular
> case). Of course you can verify the patch below too if you want to, the
Ilpo Järvinen wrote:
SNIP
Could you next try with tcp_frto set to 1, if my theory proves to be
correct, it too should be "enough" to fix the problem (in this
particular case). Of course you can verify the patch below too if you
want to, the patch should allow cups<->printer to work with tc
Ilpo Järvinen wrote:
Snip
Could you next try with tcp_frto set to 1, if my theory proves to be
correct, it too should be "enough" to fix the problem (in this
particular case). Of course you can verify the patch below too if you
want to, the patch should allow cups<->printer to work with tcp_
Ilpo Järvinen wrote:
Snip
Could you next try with tcp_frto set to 1, if my theory proves to be
correct, it too should be "enough" to fix the problem (in this
particular case). Of course you can verify the patch below too if you
want to, the patch should allow cups<->printer to work with tcp_
Added Cc netdev (=linux network developers list).
On Wed, 7 May 2008, Damon L. Chesser wrote:
Ilpo Järvinen wrote:
>
> So the problem was 100% reproducable for you with FRTO (I'm still catching
> up the details here :-))?
>
Yes, 100% reproducible if you turn FRTO = 2. Printing works as it is
6 matches
Mail list logo
