From owner-freebsd-current@FreeBSD.ORG Tue Aug 25 19:58:45 2009 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 5C206106568D for ; Tue, 25 Aug 2009 19:58:45 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 67B148FC1D for ; Tue, 25 Aug 2009 19:58:42 +0000 (UTC) Received: by ewy5 with SMTP id 5so2165328ewy.36 for ; Tue, 25 Aug 2009 12:58:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type:content-transfer-encoding; bh=OJyEeyhQ9sE6TU2GPXfAAzBU0brbSQxN+4ww41WHHHU=; b=rtWuI4/tCQhJejje5LNhyK7vbO0fVJ1/rpRxQWz75JwQ2kBSD2nJQLfTCALrrnIyWX twTtE212E1+yQgCsJRyhc+QRtBq7ndYc1nZVprvh98IZpCWjsyrmUQ3DmMqw3ouA6/tQ 7ztS/eFT+GIOX/e48dhUaWyKR+06ITMR+XK6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=FOP15ntdjoL+Cvhl3PAS9duCKUXL5lz4OSMmB16SqrwMLvczPLG29lo2UdNaV8sxFw NGkNxUSdXzlLEqyFR+FmnLe/EmjFxO3LQqr2V23n33KDUI+9Xdq8DFR1HkFFe0L+jK1r HShwPpZwvqzWVVsjIiK3TFE2PviPVVIDTOqwU= MIME-Version: 1.0 Received: by 10.210.79.18 with SMTP id c18mr6770179ebb.87.1251230252157; Tue, 25 Aug 2009 12:57:32 -0700 (PDT) From: Scott Ullrich Date: Tue, 25 Aug 2009 15:57:12 -0400 Message-ID: To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: kernel: em2: watchdog timeout -- resetting 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: Tue, 25 Aug 2009 19:58:45 -0000 I have a Nexcom firewall with Intel em nics that will not spamming the system logs with this message: kernel: em2: watchdog timeout -- resetting em0@pci0:1:4:0: class=0x020000 card=0x10768086 chip=0x10768086 rev=0x05 hdr=0x00 em1@pci0:1:5:0: class=0x020000 card=0x10768086 chip=0x10768086 rev=0x05 hdr=0x00 em2@pci0:1:6:0: class=0x020000 card=0x10768086 chip=0x10768086 rev=0x05 hdr=0x00 em3@pci0:1:7:0: class=0x020000 card=0x10768086 chip=0x10768086 rev=0x05 hdr=0x00 em0: [FILTER] em0: Ethernet address: 00:10:f3:0d:0a:db em1: port 0xd100-0xd13f mem 0xe8040000-0xe805ffff,0xe8060000-0xe807ffff irq 10 at device 5.0 on pci1 em1: [FILTER] em1: Ethernet address: 00:10:f3:0d:0a:da em2: port 0xd200-0xd23f mem 0xe8080000-0xe809ffff,0xe80a0000-0xe80bffff irq 11 at device 6.0 on pci1 em2: [FILTER] em2: Ethernet address: 00:10:f3:0d:0a:d9 The box in question is running Beta 1. I have not seen commits relating to this so I have not had a chance to update to beta 3. Does anyone know how I can clam down this system log message? It does not appear to affect network traffic at all. The device in question is a firewall. Thanks, Scott