[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#446855: marked as done (linux-image-2.6.22-2-amd64: problem with window scaling, again :()

Your message dated Tue, 16 Oct 2007 10:16:36 +0200
with message-id <20071016081636.GA1362@baikonur.stro.at>
and subject line Bug#446855: linux-image-2.6.22-2-amd64: problem with window scaling, again :(
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.22-2-amd64
Version: 2.6.22-4
Severity: normal

I observe this problem with 2.6.22-amd64, 2.6.20-i386, 2.6.18-amd64, but
not 2.6.15-i386.  Try

 wget www.copyleft-italia.it

and you should see it hang with the newer kernels after the GET.  The
symptoms are similar to those described and explained in
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267342>, but this may
be a different problem, as 2.6.15 works.  As usual, the workaround is

 echo 0 > /proc/sys/net/ipv4/tcp_window_scaling

as root, and

 net.ipv4.tcp_window_scaling = 0

in /etc/sysctl.conf.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-proposed-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=it_IT@euro (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.22-2-amd64 depends on:
ii  e2fsprogs                    1.40.2-1    ext2 file system utilities and lib
ii  initramfs-tools [linux-initr 0.90a       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

linux-image-2.6.22-2-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.22-2-amd64/preinst/initrd-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/preinst/already-running-this-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/preinst/bootloader-initrd-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.22-2-amd64/prerm/removing-running-kernel-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/preinst/abort-install-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/postinst/bootloader-test-error-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/preinst/lilo-initrd-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/preinst/failed-to-move-modules-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/postinst/depmod-error-2.6.22-2-amd64: false
  linux-image-2.6.22-2-amd64/preinst/abort-overwrite-2.6.22-2-amd64:
  linux-image-2.6.22-2-amd64/postinst/bootloader-error-2.6.22-2-amd64:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.22-2-amd64/prerm/would-invalidate-boot-loader-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/postinst/old-system-map-link-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/postinst/old-initrd-link-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/preinst/elilo-initrd-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.22-2-amd64/postinst/old-dir-initrd-link-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/postinst/depmod-error-initrd-2.6.22-2-amd64: false
  linux-image-2.6.22-2-amd64/preinst/overwriting-modules-2.6.22-2-amd64: true
  linux-image-2.6.22-2-amd64/postinst/create-kimage-link-2.6.22-2-amd64: true

--- End Message ---
--- Begin Message --- 
On Tue, Oct 16, 2007 at 09:52:57AM +0200, Francesco Potorti` wrote:
> 
>  echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
> 

as already discussed X times, fix the b0rked router inbetween you
and the named site.

closing as not a bug on our side.

-- 
maks

--- End Message ---
Reply to: