From: "Ian McDonald" <imcdnzl@gmail.com>
To: dccp@vger.kernel.org
Subject: Re: Resend: [PATCH] DCCP: Divide by zero fix
Date: Tue, 28 Feb 2006 21:35:05 +0000 [thread overview]
Message-ID: <cbec11ac0602281335n3c53c214mc2e8fb4d4e104c9e@mail.gmail.com> (raw)
In-Reply-To: <cbec11ac0602281324i6e1ff681m752c06c3b7fa7b97@mail.gmail.com>
On 3/1/06, Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> On 2/28/06, Ian McDonald <imcdnzl@gmail.com> wrote:
> > Arnaldo,
> >
> > Haven't seen this going in so resending...
>
> What a coincidence, I'm testing this patch right now, and I'm afraid it has
> some bug or makes it more likely that some other bug happens, the machine
> soft locks with it enabled and when using CCID3 as the default RX CCID in
> a TTCP test over loopback.
>
> Note that the problem happens more quickly if you test it on a machine with
> less than 64 MB (where the problem happens, but after more time).
>
OK. I am doing some testing on lockups at present from CCID3 which I
suspect are introduced recently.... they don't lock up on older code.
Having said that I'm running without that patch applied so I will
retest soon - but I don't believe it is the problem when I looked at
the scope of that code.
I have a suspicion that if I don't find anything with git-bisect for
CCID3 lockups that it might be when you use CCID3 and set
DCCP_INITIAL_SEND_ACK_VECTOR to 1....
Anyway another 3 or 4 reboots and I should give some more answers.
BTW my problems occur when using a netem box in the middle as per
setup described on DCCP testing on ODSL Wiki.
Ian
--
Ian McDonald
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
prev parent reply other threads:[~2006-02-28 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 21:24 Resend: [PATCH] DCCP: Divide by zero fix Ian McDonald
2006-02-28 21:28 ` Arnaldo Carvalho de Melo
2006-02-28 21:35 ` Ian McDonald [this message]
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=cbec11ac0602281335n3c53c214mc2e8fb4d4e104c9e@mail.gmail.com \
--to=imcdnzl@gmail.com \
--cc=dccp@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox