The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: FabF <fabian.frederick@skynet.be>
To: Jesse Stockall <stockall@magma.ca>
Cc: Debi Janos <debi.janos@freemail.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm1 - 2.6.7-mm4 weird http behavior
Date: Tue, 29 Jun 2004 19:39:06 +0200	[thread overview]
Message-ID: <1088530746.3598.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1088530069.8367.2.camel@localhost>

On Tue, 2004-06-29 at 19:27, Jesse Stockall wrote:
> On Tue, 2004-06-29 at 09:20, Debi Janos wrote:
> > I am found an interesting (bug?) feature in kernels between
> > 2.6.7-mm1 and 2.6.7-mm4
> > 
> > Some web pages eg. 
> > 
> > http://www.hup.hu/
> > http://portal.fsn.hu/
> > http://wiki.hup.hu/
> > 
> > is unreachable with these kernels. If i try kernel versions
> > <= 2.6.7 everything is O.K. above-mentioned all web pages works.
> > 
> 
> I'm seeing the same thing after upgrading to 2.6.7-mm4, 2.6.7 vanilla
> does not exhibit the problem.
> 
> Also Azureus (Java Bittorrent client) crashes when it tries to open a
> network socket to begin downloading. Again problem does not exist with
> 2.6.7.
> 
> I'm going to try a few other kernel versions to see if I can find when
> this started.
Same behaviour.

Here's an ipv4 diff (2.6.6 FE2 vs 2.6.7mm3)

 ip_local_port_range|32768 61000
 ip_nonlocal_bind|0
 ip_no_pmtu_disc|0
+ip_queue_maxlen|1024
 tcp_abort_on_overflow|0
 tcp_adv_win_scale|2
 tcp_app_win|31
-tcp_bic|0
+tcp_bic|1
 tcp_bic_fast_convergence|1
 tcp_bic_low_window|14
+tcp_default_win_scale|7
 tcp_dsack|1
 tcp_ecn|0
 tcp_fack|1
 tcp_max_orphans|8192
 tcp_max_syn_backlog|1024
 tcp_max_tw_buckets|180000
-tcp_mem|48128 48640 49152
+tcp_mem|24576 32768 49152
+tcp_moderate_rcvbuf|1
 tcp_no_metrics_save|0
 tcp_orphan_retries|0
 tcp_reordering|3
 tcp_sack|1
 tcp_stdurg|0
 tcp_synack_retries|5
-tcp_syncookies|0
 tcp_syn_retries|5
 tcp_timestamps|1
 tcp_tw_recycle|0

Regards,
FabF

> 
> Jesse


  reply	other threads:[~2004-06-29 17:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 13:20 2.6.7-mm1 - 2.6.7-mm4 weird http behavior Debi Janos
2004-06-29 15:45 ` bert hubert
2004-06-29 16:57   ` Debi Janos
2004-06-29 17:28     ` bert hubert
     [not found]       ` <freemail.20040529200446.32881@fm2.freemail.hu>
2004-06-29 18:38         ` bert hubert
2004-06-29 18:47           ` Debi Janos
2004-06-29 22:46             ` Redeeman
2004-06-29 17:27 ` Jesse Stockall
2004-06-29 17:39   ` FabF [this message]
2004-06-29 18:22 ` Stephen Hemminger
2004-06-29 18:50   ` David S. Miller
2004-06-29 19:07     ` Debi Janos
2004-06-29 19:13   ` Jesse Stockall
2004-06-29 19:49   ` Stephen Hemminger
2004-06-29 19:54     ` David S. Miller
2004-06-29 20:35       ` Stephen Hemminger
2004-06-29 20:59         ` David S. Miller
2004-06-29 21:02           ` Stephen Hemminger
2004-06-29 21:36             ` John Heffner
2004-06-29 21:53               ` David S. Miller
2004-06-29 21:58                 ` Martin Schlemmer
2004-06-30  8:04               ` Debi Janos
2004-06-30  8:04               ` Debi Janos
2004-06-30 20:14                 ` David S. Miller
2004-06-30 20:20                   ` John Heffner
  -- strict thread matches above, loose matches on Subject: below --
2004-06-29 18:40 Debi Janos
2004-06-29 22:39 ` Redeeman

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=1088530746.3598.4.camel@localhost.localdomain \
    --to=fabian.frederick@skynet.be \
    --cc=debi.janos@freemail.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stockall@magma.ca \
    /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