From owner-freebsd-net@FreeBSD.ORG Thu Nov 1 00:01:11 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29DFA16A419; Thu, 1 Nov 2007 00:01:11 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from relanium.yandex.ru (relanium.yandex.ru [213.180.193.88]) by mx1.freebsd.org (Postfix) with ESMTP id 917E113C447; Thu, 1 Nov 2007 00:01:10 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from [87.250.227.221] (v3-227-221.yandex.net [87.250.227.221]) by relanium.yandex.ru (8.14.1/8.14.1) with ESMTP id lA100Mn9053416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2007 03:00:23 +0300 (MSK) (envelope-from wawa@yandex-team.ru) Message-ID: <47291716.1030904@yandex-team.ru> Date: Thu, 01 Nov 2007 03:00:22 +0300 From: Vladimir Ivanov Organization: Yandex LLC User-Agent: Thunderbird 1.5.0.14pre (X11/20071023) MIME-Version: 1.0 To: Scott Long References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> <4728AFCC.7020706@samsco.org> In-Reply-To: <4728AFCC.7020706@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on relanium.yandex.ru host X-Antivirus-Code: 100000 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List , Jack Vogel Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 00:01:11 -0000 Scott Long wrote: > Jack Vogel wrote: >> I have found that the FAST interrupt handling is implicated >> in the watchdog resets that I have seen. It's not true. I have seen watchdogs much earlier then FASTINTR. Also, please note: older driver had a bug preventing watchdog to be reported (see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92895) >> >> What I plan to do is revert to the way 6.2 had things, meaning >> that FAST interrupts will be available but defined off by default. >> >> I wanted to know if anyone has an issue with this. And more >> importantly, I have personally not seen this problem on 7, but >> I could set up #ifdef's in that driver to be the same way. >> >> What does everyone think? We've a lot of computers w/FASTINTR (more or less patched). They carry huge traffic. But I don't remember when I have seen last watchdog. E.g.: pitman:~# sysctl dev.em.0.stats=1; dmesg | tail -30 dev.em.0.stats: -1 -> -1 [skip] em0: Excessive collisions = 0 em0: Sequence errors = 0 em0: Defer count = 0 em0: Missed Packets = 44614035 em0: Receive No Buffers = 5082415 em0: Receive Length Errors = 0 em0: Receive errors = 0 em0: Crc errors = 1 em0: Alignment errors = 0 em0: Carrier extension errors = 0 em0: RX overruns = 185231 em0: watchdog timeouts = 0 em0: XON Rcvd = 0 em0: XON Xmtd = 0 em0: XOFF Rcvd = 0 em0: XOFF Xmtd = 0 em0: Good Packets Rcvd = 918214961288 em0: Good Packets Xmtd = 933147667144 pitman:~# uptime 2:54 up 247 days, 5:59, 1 user, load averages: 1,82 1,63 1,55 WBR, Vladimir