Messages in this thread | | | Date | Thu, 24 Jul 2008 11:25:18 +0200 | From | Ingo Molnar <> | Subject | Re: [TCP bug, regression] stuck distcc connections in latest -git |
| |
* Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Ingo Molnar <mingo@elte.hu> wrote: > > > > the client (running 2.6.24) does periodic 120 seconds retransmits: > > > > 07:40:48.255452 IP dione.39201 > phoenix.distcc: . 1608:2144(536) ack 1 win 584007:40:48.255547 IP phoenix.distcc > dione.39201: . ack 2144 win 65535 > > 07:40:48.255564 IP dione.39201 > phoenix.distcc: . 67143:67679(536) ack 1 win 5840 > > 07:40:48.255648 IP phoenix.distcc > dione.39201: . ack 2144 win 65535 > > 07:42:48.255440 IP dione.39201 > phoenix.distcc: . 2144:2680(536) ack 1 win 5840 > > 07:42:48.255559 IP phoenix.distcc > dione.39201: . ack 2680 win 65535 > > 07:42:48.255570 IP dione.39201 > phoenix.distcc: . 67679:68215(536) ack 1 win 5840 > > 07:42:48.255659 IP phoenix.distcc > dione.39201: . ack 2680 win 65535 > > 07:44:48.255436 IP dione.39201 > phoenix.distcc: . 2680:3216(536) ack 1 win 584007:44:48.255570 IP phoenix.distcc > dione.39201: . ack 3216 win 65535 > > 07:44:48.255585 IP dione.39201 > phoenix.distcc: . 68215:68751(536) ack 1 win 5840 > > 07:44:48.255669 IP phoenix.distcc > dione.39201: . ack 3216 win 65535 > > OK, something's seriously screwed up on dione's kernel. Could you > please disable syncookies (which should enable SACK for you) and see > if the problem goes away? > > I think our Reno code may have been broken.
ok, i've booted the latest kernel on dione and the builds are running on it now. It's using these settings currently:
# cat /proc/sys/net/ipv4/tcp_syncookies 0 # cat /proc/sys/net/ipv4/tcp_sack 1
Just to make sure i have the right test-plan: assuming this suspected-good kernel is trouble-free for say 48 hours, i should be able to switch back to the suspected-broken variant, by doing:
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
without rebooting the kernel, right? And then if the bug comes back again we've nailed it down to the area you suspect, correct?
Ingo
| |