From owner-freebsd-current@FreeBSD.ORG Wed Nov 14 15:15:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC00116A420; Wed, 14 Nov 2007 15:15:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 51A5213C43E; Wed, 14 Nov 2007 15:15:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id lAEFFATO006897; Wed, 14 Nov 2007 10:15:10 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id lAEFFA7o096062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Nov 2007 10:15:10 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200711141515.lAEFFA7o096062@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 14 Nov 2007 10:15:10 -0500 To: John Baldwin , freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: <7.1.0.9.0.20071031165823.25898768@sentex.net> References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> <200710311621.53910.jhb@freebsd.org> <7.1.0.9.0.20071031165823.25898768@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: jfvogel@gmail.com Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 15:15:11 -0000 At 03:58 PM 10/31/2007, Mike Tancsa wrote: >To: John Baldwin , freebsd-current@freebsd.org >From: Mike Tancsa >Subject: Re: em0: watchdog timeout ... > >At 04:21 PM 10/31/2007, John Baldwin wrote: >> > >> > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 >> > rev=0x06 hdr=0x00 >> > vendor = 'Intel Corporation' >> > device = 'PRO/1000 PT' >> > class = network >> > subclass = ethernet >> > cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> > cap 05[d0] = MSI supports 1 message, 64 bit >> > cap 10[e0] = PCI-Express 1 endpoint >> > >> > its also in FastE mode and not gigE. Not sure if that makes a >> > difference or not. >> >>What if you use MSI? > >How do I enable that ? Just to follow up on this thread for the archives, enabling MSI does indeed seem to stop, or at least mitigate watchdog timeouts. Its been almost 2 weeks on this one box and we have had zero watchdog timeouts. # vmstat -i interrupt total rate irq1: atkbd0 6 0 irq4: sio0 59020 0 irq17: em3 225204 0 irq19: atapci1 243645 0 cpu0: timer 1985129675 1997 irq256: em0 1460563078 1470 irq257: em1 2360550 2 irq258: em2 1300707554 1309 cpu1: timer 1985084642 1997 Total 6734373374 6777 However, it *seems* to increase the amount of missed packets. But, traffic patterns are a little higher, so I cant be certain. em0: Missed Packets = 5514 em0: Receive No Buffers = 1950 em0: RX overruns = 9 em2: Missed Packets = 220073 em2: Receive No Buffers = 29034 em2: RX overruns = 1498 ---Mike