From owner-freebsd-stable@FreeBSD.ORG Tue Mar 22 18:24:47 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 691C116A4CE for ; Tue, 22 Mar 2005 18:24:47 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0A1343D53 for ; Tue, 22 Mar 2005 18:24:44 +0000 (GMT) (envelope-from khera@kcilink.com) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 5A852B80A for ; Tue, 22 Mar 2005 13:24:44 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: <86b62f18a2b0f9feca7009a6e6e1b9d7@kcilink.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: stable@freebsd.org From: Vivek Khera Date: Tue, 22 Mar 2005 13:24:42 -0500 X-Mailer: Apple Mail (2.619.2) Subject: bge0 watchdog timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 18:24:47 -0000 Twice today during very heavy network I/O (dumping a large postgres database over the ethernet to another machine on the same switch) I got this error: Mar 22 03:42:22 d01 kernel: bge0: watchdog timeout -- resetting Mar 22 10:28:24 d01 kernel: bge0: watchdog timeout -- resetting The most informative info I found searching google was this one: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2003-08/0096.html However, that seems to imply that a 5.4-PRERELEASE build March 15 would not be caused by this particular bug. The dmesg says this of bge0: bge0: mem 0xfc9b0000-0xfc9bffff,0xfc9c0000-0xfc9cffff irq 24 at device 9.0 on pci3 miibus0: on bge0 bge0: Ethernet address: 00:e0:81:2a:ac:5e Any insights on where to look? This is a dual Opteron running FreeBSD/amd64 with 4GB disk. The only thing funny I did was build with CPUTYPE=opteron optimizations. I'm rebuilding right now without that, but I've also cvsup'd the sources... This is my SWAG as to the problem. Anyone else still experiencing these timeouts? Vivek Khera, Ph.D. +1-301-869-4449 x806