From owner-freebsd-net@FreeBSD.ORG Mon Mar 31 08:59:55 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCF8337B401 for ; Mon, 31 Mar 2003 08:59:55 -0800 (PST) Received: from 66-162-33-178.gen.twtelecom.net (66-162-33-181.gen.twtelecom.net [66.162.33.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13CF543F3F for ; Mon, 31 Mar 2003 08:59:55 -0800 (PST) (envelope-from jeff@expertcity.com) Received: from [10.4.1.134] (helo=expertcity.com) by 66-162-33-178.gen.twtelecom.net with esmtp (Exim 3.22 #4) id 1902dW-0000xi-00 for freebsd-net@freebsd.org; Mon, 31 Mar 2003 08:59:54 -0800 Message-ID: <3E88740A.5000606@expertcity.com> Date: Mon, 31 Mar 2003 08:59:54 -0800 From: Jeff Behl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Broadcom BCM5703X causing reboot? 4.8-RC2 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2003 16:59:59 -0000 I saw some threads that seemed to relate to the bge driver in -net, so i thought i'd post here as well... FreeBSD blade7-bc2.sjc 4.8-RC2 FreeBSD 4.8-RC2 #1: Wed Mar 26 20:17:42 GMT 2003 i've had two reboots in the last 30 mins on a fairly heavly loaded web server (apache). the following immediately precedes both reboots (no more messages after this): Mar 28 19:15:29 blade7-bc2 /kernel: NMI ISA 24, EISA 0 Mar 28 19:15:29 blade7-bc2 /kernel: Mar 28 19:15:29 blade7-bc2 /kernel: NMI ISA 24, EISA 0 Mar 28 19:15:37 blade7-bc2 /kernel: bge1: watchdog timeout -- resetting Mar 28 19:15:38 blade7-bc2 /kernel: bge1: gigabit link up here's how the cards are detected: Mar 28 19:18:36 blade7-bc2 /kernel: bge0: mem 0xfbff0000-0xfbffffff irq 10 at device 1.0 on pci1 Mar 28 19:18:36 blade7-bc2 /kernel: bge0: Ethernet address: 00:09:6b:00:4f:ff Mar 28 19:18:36 blade7-bc2 /kernel: pcib2: on motherboard Mar 28 19:18:36 blade7-bc2 /kernel: pci2: on pcib2 Mar 28 19:18:36 blade7-bc2 /kernel: bge1: mem 0xf9ff0000-0xf9ffffff irq 11 at device 1.0 on pci2 Mar 28 19:18:36 blade7-bc2 /kernel: bge1: Ethernet address: 00:09:6b:00:50:00 any ideas or help? these are the first blades we've put into production (IBM bladecenter)...which isn't boding well at all for using the remaining 12 blades. the machines are only pumping out around 9Mb/s. from other threads on this list, it would seem others have seen these watchdog timeouts and related it to a possible error in the chipset itself. has this been confirmed? will disabling checksum offload, as someone mentioned, fix this? i wouldn't be surprised if this was some sort of chipset issue as the management module for the blades logs errors whenever i get a reboot: 09:56:25 (image1.sjc) PFA Alert, see preceding error in system error log. 09:56:22 (image1.sjc) 00150500 PERR: Master Read parity error Slot=00 VendID=14E4 DevID=16A7 Status=83 09:56:21 (image1.sjc) 00150700 PERR: Slave signaled parity error Slot=00 VendID=1166 DevID=0101 Status any help greatly appreciated. we would really like to keep this bladecenter and not have to look into moving to linux...bleh jeff