-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-36~~test1) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Aug 28 07:02:39 UTC 2011
** Kernel log:
[121346.904848] IPv6 addrconf: prefix with wrong length 112
[121545.363267] IPv6 addrconf: prefix with wrong length 112
[121705.607323] IPv6 addrconf: prefix with wrong length 112
[121882.980935] IPv6 addrconf: prefix with wrong length 112
[122062.794094] IPv6 addrconf: prefix with wrong length 112
[122260.996581] IPv6 addrconf: prefix with wrong length 112
[122422.132551] IPv6 addrconf: prefix with wrong length 112
[122582.668669] IPv6 addrconf: prefix with wrong length 112
[122755.607614] IPv6 addrconf: prefix with wrong length 112
[122944.318643] IPv6 addrconf: prefix with wrong length 112
[123094.710549] IPv6 addrconf: prefix with wrong length 112
[123255.552262] IPv6 addrconf: prefix with wrong length 112
[123411.620998] IPv6 addrconf: prefix with wrong length 112
[123590.854267] IPv6 addrconf: prefix with wrong length 112
[123763.579536] IPv6 addrconf: prefix with wrong length 112
[123924.648488] IPv6 addrconf: prefix with wrong length 112
[124073.066374] IPv6 addrconf: prefix with wrong length 112
[124224.191840] IPv6 addrconf: prefix with wrong length 112
[124404.708921] IPv6 addrconf: prefix with wrong length 112
[124568.008579] IPv6 addrconf: prefix with wrong length 112
[124729.944418] IPv6 addrconf: prefix with wrong length 112
[124884.821342] IPv6 addrconf: prefix with wrong length 112
[125056.111801] IPv6 addrconf: prefix with wrong length 112
[125212.164695] IPv6 addrconf: prefix with wrong length 112
[125398.564716] IPv6 addrconf: prefix with wrong length 112
[125567.147614] IPv6 addrconf: prefix with wrong length 112
[125756.067417] IPv6 addrconf: prefix with wrong length 112
[125913.939883] IPv6 addrconf: prefix with wrong length 112
[126081.466919] IPv6 addrconf: prefix with wrong length 112
[126249.465871] IPv6 addrconf: prefix with wrong length 112
[126427.179352] IPv6 addrconf: prefix with wrong length 112
[126584.935826] IPv6 addrconf: prefix with wrong length 112
[126763.089327] IPv6 addrconf: prefix with wrong length 112
[126939.311225] IPv6 addrconf: prefix with wrong length 112
[127106.762115] IPv6 addrconf: prefix with wrong length 112
[127288.562915] IPv6 addrconf: prefix with wrong length 112
[127476.353069] IPv6 addrconf: prefix with wrong length 112
[127636.695010] IPv6 addrconf: prefix with wrong length 112
[127832.037894] IPv6 addrconf: prefix with wrong length 112
[127988.586542] IPv6 addrconf: prefix with wrong length 112
[128147.862788] IPv6 addrconf: prefix with wrong length 112
[128300.919986] IPv6 addrconf: prefix with wrong length 112
[128499.890292] IPv6 addrconf: prefix with wrong length 112
[128674.492271] IPv6 addrconf: prefix with wrong length 112
[128865.787740] IPv6 addrconf: prefix with wrong length 112
[129048.536473] IPv6 addrconf: prefix with wrong length 112
[129224.230307] IPv6 addrconf: prefix with wrong length 112
[129385.618205] IPv6 addrconf: prefix with wrong length 112
[129560.984101] IPv6 addrconf: prefix with wrong length 112
[129729.770899] IPv6 addrconf: prefix with wrong length 112
[129898.397785] IPv6 addrconf: prefix with wrong length 112
[130092.444863] IPv6 addrconf: prefix with wrong length 112
[130290.551328] IPv6 addrconf: prefix with wrong length 112
[130449.486642] IPv6 addrconf: prefix with wrong length 112
[130614.279041] IPv6 addrconf: prefix with wrong length 112
[130763.844747] IPv6 addrconf: prefix with wrong length 112
[130917.966564] IPv6 addrconf: prefix with wrong length 112
[131113.496584] IPv6 addrconf: prefix with wrong length 112
[131292.161979] IPv6 addrconf: prefix with wrong length 112
[131474.126815] IPv6 addrconf: prefix with wrong length 112
[131623.304591] IPv6 addrconf: prefix with wrong length 112
[131778.693433] IPv6 addrconf: prefix with wrong length 112
[131958.458616] IPv6 addrconf: prefix with wrong length 112
[132120.574452] IPv6 addrconf: prefix with wrong length 112
[132311.713917] IPv6 addrconf: prefix with wrong length 112
[132473.305814] IPv6 addrconf: prefix with wrong length 112
[132640.832835] IPv6 addrconf: prefix with wrong length 112
[132826.893321] IPv6 addrconf: prefix with wrong length 112
[133003.770733] IPv6 addrconf: prefix with wrong length 112
[133159.637989] IPv6 addrconf: prefix with wrong length 112
[133314.284487] IPv6 addrconf: prefix with wrong length 112
[133511.194537] IPv6 addrconf: prefix with wrong length 112
[133709.381636] IPv6 addrconf: prefix with wrong length 112
[133900.809484] IPv6 addrconf: prefix with wrong length 112
[134078.258667] IPv6 addrconf: prefix with wrong length 112
[134269.326195] IPv6 addrconf: prefix with wrong length 112
[134420.639662] IPv6 addrconf: prefix with wrong length 112
[134605.916052] IPv6 addrconf: prefix with wrong length 112
[134764.020549] IPv6 addrconf: prefix with wrong length 112
[134920.313266] IPv6 addrconf: prefix with wrong length 112
[135069.207080] IPv6 addrconf: prefix with wrong length 112
[135235.658304] IPv6 addrconf: prefix with wrong length 112
[135432.169039] IPv6 addrconf: prefix with wrong length 112
[135582.590835] IPv6 addrconf: prefix with wrong length 112
[135747.374280] IPv6 addrconf: prefix with wrong length 112
[135903.050945] IPv6 addrconf: prefix with wrong length 112
[136056.902816] IPv6 addrconf: prefix with wrong length 112
[136217.676152] IPv6 addrconf: prefix with wrong length 112
[136404.152361] IPv6 addrconf: prefix with wrong length 112
[136590.600618] IPv6 addrconf: prefix with wrong length 112
[136745.809536] IPv6 addrconf: prefix with wrong length 112
[136937.648081] IPv6 addrconf: prefix with wrong length 112
[137104.520174] IPv6 addrconf: prefix with wrong length 112
[137280.901095] IPv6 addrconf: prefix with wrong length 112
[137454.492117] IPv6 addrconf: prefix with wrong length 112
[137615.585511] IPv6 addrconf: prefix with wrong length 112
[137805.347935] IPv6 addrconf: prefix with wrong length 112
[137976.014642] IPv6 addrconf: prefix with wrong length 112
[138139.030289] IPv6 addrconf: prefix with wrong length 112
[138329.553945] IPv6 addrconf: prefix with wrong length 112
** Model information
sys_vendor: ASUSTek Computer INC.
product_name: RS100-E7-PI2
product_version: 1.xxG
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: 0401 x64
board_vendor: ASUSTeK Computer INC.
board_name: P8B-M
board_version: 1.xxG
** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
*** Protocol statistics:
Ip:
51356 total packets received
0 forwarded
0 incoming packets discarded
51356 incoming packets delivered
23914 requests sent out
Icmp:
483 ICMP messages received
7 input ICMP message failed.
ICMP input histogram:
destination unreachable: 13
echo requests: 464
479 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 15
echo replies: 464
IcmpMsg:
InType3: 13
InType8: 464
OutType0: 464
OutType3: 15
Tcp:
19 active connections openings
1065 passive connection openings
15 failed connection attempts
7 connection resets received
1 connections established
49776 segments received
20708 segments send out
1641 segments retransmited
13 bad segments received.
472 resets sent
Udp:
1084 packets received
13 packets to unknown port received.
0 packet receive errors
1086 packets sent
UdpLite:
TcpExt:
13 resets received for embryonic SYN_RECV sockets
823 TCP sockets finished time wait in fast timer
438 delayed acks sent
Quick ack mode was activated 1 times
344 packets directly queued to recvmsg prequeue.
1486 bytes directly received in process context from prequeue
8400 packet headers predicted
20 packets header predicted and directly queued to user
18203 acknowledgments not containing data payload received
18625 predicted acknowledgments
5 times recovered from packet loss by selective acknowledgements
1 congestion windows recovered without slow start after partial ack
1626 fast retransmits
2 other TCP timeouts
1 DSACKs sent for old packets
1 DSACKs received
10 connections reset due to unexpected data
1 connections aborted due to timeout
TCPSackShifted: 5598
TCPSackMerged: 139
TCPSackShiftFallback: 130
IpExt:
InOctets: 12414230
OutOctets: 172686207
04:05.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 10) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:8373]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 15
Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at fb000000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at c000 [size=128]
Expansion ROM at <unassigned> [disabled]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
** USB devices:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii initramfs-tools [linux-init 0.99~bpo60+1 tools for generating an initramfs
pn linux-base <none> (no description available)
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-5-amd64 recommends:
pn firmware-linux-free <none> (no description available)
pn libc6-i686 <none> (no description available)
Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110902083651.5680.27187.reportbug@fillmore.wieis tmeineip.de">http://lists.debian.org/20110902083651.5680.27187.reportbug@fillmore.wieis tmeineip.de
09-04-2011, 09:41 PM
Ben Hutchings
Bug#640091: linux-image-2.6.32-5-amd64: Performance problem with the e1000e driver
On Fri, 2011-09-02 at 10:36 +0200, Thorsten Giese wrote:
> Package: linux-2.6
> Version: 2.6.32-36~~test1
> Severity: important
>
> I discussed this already with Ben Hutchings, please see this thread:
>
> http://lists.debian.org/debian-kernel/2011/08/msg01267.html
To summarise the information you've given about different
configurations:
Affected:
1. e1000e on 2.6.32 connecting to site on different network segment
2. e1000e backport from 2.6.38 connecting to site on different network
segment
Not affected:
3. e1000e on 2.6.26
4. e1000e on 2.6.32 connecting to site on same network segment
5. e1000e on 2.6.32 during first few minutes after boot
6. e1000e on 2.6.39
7. r8169 on 2.6.32 (not same system)
Case 7 strongly suggests that this issue is related to the driver or the
environment and not the stack (or not only the stack). But then there
don't seem to be any relevant changes to this driver between 2.6.38 and
2.6.39, so why the difference beween cases 2 and 6?
Case 5 is interesting. Is there some service started at boot, that may
start to access the network after a few minutes? In cases 3 and 6, did
you test in the first few minutes after boot, or did you wait a while?