On Mar 6, 2007, at 9:20 AM, Chad Leigh -- Shire.Net LLC wrote:

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

ok, it started happening again after about 1.5 hours after the last reboot. bge0 started going down and up a few times over about an hour, and then the read timedout messages started up again. Previous to the very first time that this started, the server had run for about 4 days since it was newly installed.

Mar  6 09:09:23 server su: chad to root on /dev/ttyp0
Mar  6 10:26:29 server kernel: bge0: link state changed to DOWN
Mar  6 10:26:31 server kernel: bge0: link state changed to UP
Mar  6 10:42:33 server kernel: bge0: link state changed to DOWN
Mar  6 10:42:35 server kernel: bge0: link state changed to UP
Mar  6 11:31:19 server kernel: bge0: PHY read timed out
Mar  6 11:31:19 server last message repeated 3 times
Mar  6 11:31:19 server kernel: bge0: link state changed to DOWN
Mar  6 11:31:21 server kernel: bge0: PHY read timed out
Mar  6 11:31:52 server last message repeated 116 times
Mar  6 11:33:53 server last message repeated 488 times
Mar  6 11:43:54 server last message repeated 2356 times
Mar  6 11:53:56 server last message repeated 2372 times
Mar  6 12:03:57 server last message repeated 2368 times
Mar  6 12:09:53 server last message repeated 1399 times
Mar  6 12:09:53 server kernel: bge0: watchdog timeout -- resetting
Mar  6 12:09:53 server kernel: bge0: PHY read timed out
Mar  6 12:09:53 server last message repeated 4 times
Mar  6 12:09:53 server kernel: bge0: RX CPU self-diagnostics failed!
Mar  6 12:09:53 server kernel: bge0: flow-through queue init failed
Mar  6 12:09:53 server kernel: bge0: initialization failure
Mar  6 12:09:54 server kernel: bge0: PHY read timed out
Mar  6 12:10:25 server last message repeated 152 times
Mar  6 12:12:27 server last message repeated 616 times
Mar  6 12:22:29 server last message repeated 2540 times
Mar  6 12:32:30 server last message repeated 2452 times
Mar  6 12:42:31 server last message repeated 2524 times
Mar  6 12:46:27 server last message repeated 1127 times
Mar  6 12:46:27 server login: ROOT LOGIN (root) ON ttyv0
Mar  6 12:46:29 server kernel: bge0: PHY read timed out
Mar  6 12:46:41 server last message repeated 107 times
Mar  6 12:46:40 server reboot: rebooted by root

here is an ifconfig

bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
        inet 166.70.252.128 netmask 0xffffff00 broadcast 166.70.252.255
        inet 166.70.252.120 netmask 0xffffffff broadcast 166.70.252.120
        inet 166.70.252.199 netmask 0xffffffff broadcast 166.70.252.199
        ether 00:e0:81:61:e9:a0
        media: Ethernet autoselect (1000baseTX <full-duplex>)
        status: active

and uname

# uname -a
FreeBSD server.shire.net 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #1: Sat Mar 3 13:11:00 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/ src/sys/server i386
#

It is a TYAN S2850 single opteron system with 2.4ghz single core opteron.

Its dmesg ID is seen below in the quoted section.

I had another machine with this same MB that ran for a long time fine until I upgraded it to 6.0 or 6.1 last Fall and then I started to have the same problem (a post about it is in the archives). I assumed it was a HW issue and turned off the port in the BIOS and used the other port until I took the machine offline as the customer using it no longer needed it.

Now this machine is having the same symptoms and I remember reading in the lists something about PHY and bge and some driver problems a while back but cannot fnd it now in the archives.

Could this be a SW problem or is it a HW issue? Could it be related to the port it is connected to or the cable or something? The other machine that had this problem was on a different switch brand.

Thanks
Chad



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: <Broadcom BCM5705 A3, ASIC rev. 0x3003> mem 0xfeab0000-0xfeabffff irq 16 at device 14.0 on pci1
Mar  6 09:01:21 server kernel: miibus0: <MII bus> on bge0
Mar 6 09:01:21 server kernel: brgphy0: <BCM5705 10/100/1000baseTX PHY> 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



_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to