From owner-freebsd-questions@FreeBSD.ORG Tue Mar 6 16:20:50 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C222916A406 for ; Tue, 6 Mar 2007 16:20:50 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.freebsd.org (Postfix) with ESMTP id AA8DC13C4AA for ; Tue, 6 Mar 2007 16:20:50 +0000 (UTC) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.51) id 1HOcPC-0008Ye-1I for freebsd-questions@freebsd.org; Tue, 06 Mar 2007 09:20:50 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: User Questions From: "Chad Leigh -- Shire.Net LLC" Date: Tue, 6 Mar 2007 09:20:49 -0700 X-Mailer: Apple Mail (2.752.2) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Subject: started getting repeated "bge0: PHY read timed out" messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2007 16:20:50 -0000 Hi After running fine for a while, my new server running 6.2-RELEASE with latest security patches as of last Thursday or Friday started giving the message bge0: PHY read timed out and I found the following in the system log Mar 6 02:59:33 server kernel: bge0: link state changed to DOWN Mar 6 02:59:36 server kernel: bge0: link state changed to UP Mar 6 03:00:27 server kernel: bge0: link state changed to DOWN Mar 6 03:00:29 server kernel: bge0: link state changed to UP Mar 6 05:09:27 server kernel: bge0: PHY read timed out Mar 6 05:09:27 server last message repeated 3 times Mar 6 05:09:27 server kernel: bge0: link state changed to DOWN Mar 6 05:09:29 server kernel: bge0: PHY read timed out Mar 6 05:09:50 server last message repeated 79 times Mar 6 05:09:50 server kernel: bge0: watchdog timeout -- resetting Mar 6 05:09:50 server kernel: bge0: PHY read timed out Mar 6 05:09:50 server last message repeated 4 times Mar 6 05:09:50 server kernel: bge0: RX CPU self-diagnostics failed! Mar 6 05:09:50 server kernel: bge0: flow-through queue init failed Mar 6 05:09:50 server kernel: bge0: initialization failure Mar 6 05:09:52 server kernel: bge0: PHY read timed out Mar 6 05:10:23 server last message repeated 140 times Mar 6 05:12:24 server last message repeated 616 times Mar 6 05:22:26 server last message repeated 2580 times Mar 6 05:32:28 server last message repeated 2460 times Mar 6 05:42:30 server last message repeated 2540 times Mar 6 05:52:32 server last message repeated 2572 times Mar 6 06:02:33 server last message repeated 2652 times Mar 6 06:12:34 server last message repeated 2532 times Mar 6 06:22:35 server last message repeated 2516 times Mar 6 06:32:37 server last message repeated 2452 times Mar 6 06:42:38 server last message repeated 2520 times Mar 6 06:52:39 server last message repeated 2544 times Mar 6 07:02:39 server last message repeated 2919 times Mar 6 07:12:41 server last message repeated 2521 times Mar 6 07:22:43 server last message repeated 2524 times Mar 6 07:32:44 server last message repeated 2440 times Mar 6 07:42:45 server last message repeated 2524 times Mar 6 07:52:48 server last message repeated 2528 times Mar 6 08:02:50 server last message repeated 2656 times Mar 6 08:12:51 server last message repeated 2552 times Mar 6 08:22:53 server last message repeated 2528 times Mar 6 08:32:55 server last message repeated 2436 times Mar 6 08:42:57 server last message repeated 2536 times Mar 6 08:52:58 server last message repeated 2544 times Mar 6 08:58:55 server last message repeated 1631 times This appears to be a HW problem at first look. But when the server boots, it works fine for a while (hours, days??) Here is the id in the boot message Mar 6 09:01:21 server kernel: bge0: mem 0xfeab0000-0xfeabffff irq 16 at device 14.0 on pci1 Mar 6 09:01:21 server kernel: miibus0: on bge0 Mar 6 09:01:21 server kernel: brgphy0: on miibus0 Mar 6 09:01:21 server kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Mar 6 09:01:21 server kernel: bge0: Ethernet address: 00:e0:81:61:e9:a0 Is this some sort of SW driver issue or is it a HW issue at first glance? I remember kind of reading about some BGE issues a while back. Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net