From owner-freebsd-net@FreeBSD.ORG  Mon Sep  3 04:56:44 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 3531E106564A;
	Mon,  3 Sep 2012 04:56:44 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5])
	by mx1.freebsd.org (Postfix) with ESMTP id 886358FC0C;
	Mon,  3 Sep 2012 04:56:43 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.5/8.14.5) with ESMTP id q834uegw030240;
	Mon, 3 Sep 2012 11:56:40 +0700 (NOVT)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <50443888.9080400@rdtc.ru>
Date: Mon, 03 Sep 2012 11:56:40 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: pyunyh@gmail.com
References: <1865271844.20120829131610@serebryakov.spb.ru>
	<CAHu1Y70MynCMQTrJUMwTZ0+LrM1JiZFt_B77028XHfoiRgzmaA@mail.gmail.com>
	<1807373989.20120829223125@serebryakov.spb.ru>
	<20120830152726.A33776@sola.nimnet.asn.au>
	<534292400.20120830131158@serebryakov.spb.ru>
	<20120831180721.GB3208@michelle.cdnetworks.com>
	<50404F91.8080302@rdtc.ru>
	<20120903184049.GB3730@michelle.cdnetworks.com>
In-Reply-To: <20120903184049.GB3730@michelle.cdnetworks.com>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Cc: freebsd-net@freebsd.org, Lev Serebryakov <lev@freebsd.org>,
	Ian Smith <smithi@nimnet.asn.au>
Subject: Re: vr(4) troubles for AMD Geode CS5536 chipset
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Sep 2012 04:56:44 -0000

04.09.2012 01:40, YongHyeon PYUN пишет:

>> Presently, every day my WAN vr interface stops running correctly:
>> sometimes it stops receiving all packets - tcpdump shows none of them.
>> Sometimes, it receives some but with great delay - up to 10 seconds (not miliseconds)
>> and even more. tcpdump shows that delay occurs on receive path.
>> Sometimes, it even rearranges packets - tcpdump shows that some incoming ICMP echo requests
>> with lower sequence numbers come in later that already answered higher-numbered requests.
> 
> Hmm, it seems driver's consumer/producer index of RX path were
> corrupted.

Have you any idea how to find that out for sure?
Add some debug printfs or KASSERT, may be?
I'm ready to test.

> By chance, did vr(4) spew some kind of diagnostics messages to
> console?  If I remember correctly, vr(4) automatically restarts
> controller and show these errors when it detects abnormal
> condition. Abnormal conditions for vr(4) would be:
>  - TX/RX MAC stuck
>  - RX MAC stop due to FIFO overflow or no RX buffers
>  - PCI bus errors
>  - TX abort
>  - TX underrun
> 

None. I've read its source and learned it prints its debug
to the kernel dmesg buffer with sysctl dev.vr.1.stats=1
and done that before, during and after noted failure -
all counters are zero except of good frames conters (in/out).

Eugene Grosbein