From owner-freebsd-bugs@FreeBSD.ORG  Wed Feb 25 17:19:43 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 73F2B77E
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Feb 2015 17:19:43 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 40E11846
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Feb 2015 17:19:43 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1PHJhHG023498
 for <freebsd-bugs@FreeBSD.org>; Wed, 25 Feb 2015 17:19:43 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 193802] tso seems broken on RELENG10 for version 7.4.2 of em
 driver
Date: Wed, 25 Feb 2015 17:19:43 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: bsd@volki.at
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-193802-8-QNTuCmXirs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193802-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-193802-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 17:19:43 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193802

Friedrich Volkmann <bsd@volki.at> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bsd@volki.at

--- Comment #1 from Friedrich Volkmann <bsd@volki.at> ---
Same here. I run into problems sending TCP data bigger than ~4 KB when the TCO
option is enabled (which is the default!). See
https://forums.freebsd.org/threads/error-sending-tcp-data-4kb.50431 for the
details.

The problems occur with both an up-to-date i386 kernel and an up-to-date amd64
kernel (10.1-STABLE r278696).

dmesg reports:
em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xf080-0xf09f mem
0xf7f00000-0xf7f1ffff,0xf7f3c000-0xf7f3cfff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt

# ifconfig -v em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=4009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO>
        ether ...
        inet ... netmask ... broadcast ...
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

This is an onboard LAN controller (I218-V according to the manual) on an MSI
Z97S SLI Plus motherboard (Intel Z97 Express chipset).

The importance has already been set to "Affects Many People". This is probably
true, and it is difficult for affected users to get help as they cannot send
data. To make it even worse, the symptoms (error messages such as "The server
may be unavailable or is refusing SMTP connections") do not reveal the real
cause of the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.