From owner-freebsd-current@FreeBSD.ORG Mon Nov 12 01:08:42 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D58A116A421 for ; Mon, 12 Nov 2007 01:08:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9C7F313C48D for ; Mon, 12 Nov 2007 01:08:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1443668waf for ; Sun, 11 Nov 2007 17:08:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=p/OFy0sL1apcVbVEQcE4QZP4fGMqE5wsoVUt5zgSLg0=; b=Y9TWXfKLJwS4HujbNmaOpDpy80w52RTtE+LQxEaOYUx75u5DCZ4k8VimK76zwdxXqf+TZzI+RSxcZpfpCuLCYoe7ay6k3vj7E3KArn2wo5jFXEuzF/JL8PZdHYYWllu6i11fZFvGTDkSSdGngJNHHRIV8b8ANaKygPXd4ySfH1k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=aRFcwcEJYy6bxF8A9SrKOKJBN9VpHm1VF8BcGDKgsNUhr6+eg6Ytm0N/Wyamu7OQrEWvoxNz/vulNxLsAPL2qo99KJ3tma2cDt5riI7Hq1WuBT+7EymRgvc24DIIhFMO6I9OKU5YD9S/5FCYFJ0SCtLP23Hak3OyLQuYEbilyrw= Received: by 10.114.153.18 with SMTP id a18mr48698wae.1194829713545; Sun, 11 Nov 2007 17:08:33 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id l22sm6486287waf.2007.11.11.17.08.30 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 11 Nov 2007 17:08:31 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lAC18M6A095115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2007 10:08:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lAC18Mej095114; Mon, 12 Nov 2007 10:08:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 12 Nov 2007 10:08:22 +0900 From: Pyun YongHyeon To: Daniel Gerzo Message-ID: <20071112010822.GB87383@cdnetworks.co.kr> References: <507457093.20071111190706@rulez.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <507457093.20071111190706@rulez.sk> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org Subject: Re: Reproducible problems with re(4) on RELENG_7 and HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 01:08:43 -0000 On Sun, Nov 11, 2007 at 07:07:06PM +0100, Daniel Gerzo wrote: > Hello people, > > I would like to report problems which are most probably related to > the re(4) driver. The problem is reproducible after some time (i.e. > after some amount of data has been sent/received) and disappears > again after reboot. You can try to reproduce it by extracting a big > tar archive contianing a thousands of small files with verbose > output (e.g. tar -v) over ssh session. It will reset your connection > after some time with something like: > > Disconnecting: Bad packet length 4070316545. > > After it's been provoked for the first time, it is even more easier > to provoke it again, simply by ssh-ing to the box and running "yes". > The problem will occur in a few seconds, and you will be > disconnected with the error mentioned above, or sometimes with the > following error: > > Disconnecting: Corrupted MAC on input. > > Ok, these were the symptones, now the device in the question: > > I suppose that it is an integrated card (the machine is in > collocation and I've never seen it by myself). This is the > respective line from dmesg: > > re0: port 0xd800-0xd8ff mem 0xfdfff000-0xfdffffff irq 19 at device 0.0 on pci2 > > pciconf -lv output: > > re0@pci0:2:0:0: class=0x020000 card=0x368c1462 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > I would swear that this isn't a bad hardware, as the machine is > brand new, and we have 4 of these boxes, all of them are having the > same symptons. I also have a friend, who is experiencing the same > problem for quite some time on HEAD (I am running on recent > RELENG_7). > > I will very willingly provide any additional data, which might be > required, I can also manage a remote ssh access to the machine so it > can be debugged. > > The problem is, that the system itself doesn't hang, there is no > panic and no additional information in /var/log/messages. If there > is any way how can I debug this, please let me know and I will do so > ASAP (as we are migrating our servers to this hardware). Also, I > wasn't able to reproduce it by transferring a 10gb file over ftp, > but when the problem starts to occur, it's not limited to only ssh > connecion. I mean, even mysql connections are being reset. > > Any help will be greatly appreciated! Also, if you are able to > confirm this problem with re(4) etherent card, please let us know! > I didn't encounter this problem. And I think you're the first one that reported this issue. Problem description says that data corruption happened somewhere during large transfers of data. It seems that you can reproduce it on demand so how about disabling checksum offload on re(4)? If that fix the issue would you check number of bad checksums from the "netstat -s" before/after the test? -- Regards, Pyun YongHyeon