Re: started getting repeated "bge0: PHY read timed out" messages
On Mar 15, 2007, at 12:48 AM, Michael K. Smith - Adhost wrote: Have you considered hard-setting the speed/duplex to 1000/Full instead of 100/Full? There may be some issues in the autonegotiation happening between switch and server. We used to see some of this early on in inter-vendor GigE connections; perhaps the switch vendor and the FreeBSD devels are reading the standards differently. I thought of that. However, I thought that if that were the case, the problem would happen at boot and not start at some random time after boot and work for a while first. Is that not a valid thought? Chad Mike --- 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]"
RE: started getting repeated "bge0: PHY read timed out" messages
Hello Chad: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Leigh -- Shire.Net LLC Sent: Wednesday, March 14, 2007 11:19 PM To: User Questions Subject: Re: started getting repeated "bge0: PHY read timed out" messages On Mar 6, 2007, at 9:55 PM, Chad Leigh -- Shire.Net LLC wrote: > > On Mar 6, 2007, at 5:08 PM, Michael K. Smith - Adhost wrote: > >> >> Have you looked at the output of 'netstat -i' to see if there are >> interface errors? Also, have you looked at the switch-side interface >> for errors, buffer problems, etc. (if that's possible)? Finally, >> have >> you swapped ports/cables on the switch? >> >> Regards, >> >> Mike > > > Hi Mike > > Right now it seems to be behaving. netstat -i shows no issues and > I have not had the problem recur again once I forced it from auto > negotiation which ended up at 1000tx full duplex to now be 100tx at > full duplex. I don't know if it is related to the problem or not > or is a coincidence that once I did that the problem has not > arisen. It happened about 3 times today before forcing the > connection to be 100tx. OK, this problem has not resurfaced since I hardwired the settings on the port to 100tx and full duplex. I have another system with the same board that got the same problem last Fall when I upgraded from 5.4 to 6.0 or 6.1. The problem this time was on 6.2. I have another one of these boards running on a system with 5.4 without issue at gigabit speed. It appears that something happened in the bge driver from 5.x to 6.x at gigabit speeds, at least with some of the supported chipsets. Chad Have you considered hard-setting the speed/duplex to 1000/Full instead of 100/Full? There may be some issues in the autonegotiation happening between switch and server. We used to see some of this early on in inter-vendor GigE connections; perhaps the switch vendor and the FreeBSD devels are reading the standards differently. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: started getting repeated "bge0: PHY read timed out" messages
On Mar 6, 2007, at 9:55 PM, Chad Leigh -- Shire.Net LLC wrote: On Mar 6, 2007, at 5:08 PM, Michael K. Smith - Adhost wrote: Have you looked at the output of 'netstat -i' to see if there are interface errors? Also, have you looked at the switch-side interface for errors, buffer problems, etc. (if that's possible)? Finally, have you swapped ports/cables on the switch? Regards, Mike Hi Mike Right now it seems to be behaving. netstat -i shows no issues and I have not had the problem recur again once I forced it from auto negotiation which ended up at 1000tx full duplex to now be 100tx at full duplex. I don't know if it is related to the problem or not or is a coincidence that once I did that the problem has not arisen. It happened about 3 times today before forcing the connection to be 100tx. OK, this problem has not resurfaced since I hardwired the settings on the port to 100tx and full duplex. I have another system with the same board that got the same problem last Fall when I upgraded from 5.4 to 6.0 or 6.1. The problem this time was on 6.2. I have another one of these boards running on a system with 5.4 without issue at gigabit speed. It appears that something happened in the bge driver from 5.x to 6.x at gigabit speeds, at least with some of the supported chipsets. 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]"
Re: started getting repeated "bge0: PHY read timed out" messages
On Mar 6, 2007, at 5:08 PM, Michael K. Smith - Adhost wrote: Have you looked at the output of 'netstat -i' to see if there are interface errors? Also, have you looked at the switch-side interface for errors, buffer problems, etc. (if that's possible)? Finally, have you swapped ports/cables on the switch? Regards, Mike Hi Mike Right now it seems to be behaving. netstat -i shows no issues and I have not had the problem recur again once I forced it from auto negotiation which ended up at 1000tx full duplex to now be 100tx at full duplex. I don't know if it is related to the problem or not or is a coincidence that once I did that the problem has not arisen. It happened about 3 times today before forcing the connection to be 100tx. If it starts to happen again I will try and log in to the console and do the netstat -i then... In the morning I will break out my powerbook and get the switch port assignments off a chart I have there so I can log in to the switch and check the port for errors. I have not swapped ports/cables on the switch this time around but have had the exact same symptoms on a server with the same HW that was using different cables and a different switch... I may swap cables but the machine is downtown and I am not so unless I cannot make progress I want to avoid going downtown :-) I may swap the mainboard if it happens again to see if it is HW. I have one or two spare mainboards of the same sort. 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]"
RE: started getting repeated "bge0: PHY read timed out" messages
Hello: > -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of Chad Leigh -- Shire.Net LLC > Sent: Tuesday, March 06, 2007 12:05 PM > To: User Questions > Subject: Re: started getting repeated "bge0: PHY read timed out" > messages > > > 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 mtu 1500 > options=1b > inet 166.70.252.128 netmask 0xff00 broadcast > 166.70.252.255 > inet 166.70.252.120 netmask 0x broadcast > 166.70.252.120 > inet 166.70.252.199 netmask 0x broadcast > 166.70.252.199 > ether 00:e0:81:61:e9:a0 > media: Ethernet autoselect (1000baseTX ) > 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 > > >
Re: started getting repeated "bge0: PHY read timed out" messages
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 mtu 1500 options=1b inet 166.70.252.128 netmask 0xff00 broadcast 166.70.252.255 inet 166.70.252.120 netmask 0x broadcast 166.70.252.120 inet 166.70.252.199 netmask 0x broadcast 166.70.252.199 ether 00:e0:81:61:e9:a0 media: Ethernet autoselect (1000baseTX ) 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: rev. 0x3003> mem 0xfeab-0xfeab 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: 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]"
Re: started getting repeated "bge0: PHY read timed out" messages
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 Probably should have said i386 version # 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 # Tyan S2850 single opteron 2gb ecc new install from ISO then cvsup'ed to latest Chad 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: rev. 0x3003> mem 0xfeab-0xfeab 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: 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 "freebsd-questions- [EMAIL PROTECTED]" --- 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]"
Re: started getting repeated "bge0: PHY read timed out" messages
> > 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: 0x3003> mem 0xfeab-0xfeab 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: 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 sorry, no solution here, just a `me too`: FreeBSD 6.2-RELEASE #0 i386 (in my case, it started right after upgrading from 6.1-RELEASE to 6.2-RELEASE) [..] Mar 4 20:01:39 lyekka kernel: sk0: link state changed to DOWN Mar 4 20:01:45 lyekka kernel: sk0: link state changed to UP Mar 4 20:02:18 lyekka kernel: sk0: link state changed to DOWN Mar 4 20:02:20 lyekka kernel: sk0: link state changed to UP Mar 4 20:02:35 lyekka kernel: sk0: link state changed to DOWN Mar 4 20:02:39 lyekka kernel: sk0: link state changed to UP Mar 4 21:50:35 lyekka kernel: sk0: link state changed to DOWN Mar 4 21:50:38 lyekka kernel: sk0: link state changed to UP Mar 4 21:50:52 lyekka kernel: sk0: link state changed to DOWN Mar 4 21:50:54 lyekka kernel: sk0: link state changed to UP Mar 5 00:45:00 lyekka kernel: sk0: link state changed to DOWN Mar 5 05:28:56 lyekka kernel: sk0: phy write timeout [..] card is: [..] skc0: port 0xa800-0xa8ff mem 0xef004000-0xef007fff irq 12 at device 7.0 on pci0 skc0: SK-9521 10/100/1000Base-T Adapter rev. (0x1) sk0: on skc0 [..] after some time (it differs, normally after a few days) it is not possible to send/receive data via this interface. `ifconfig sk0 down ; ifconfig sk0 up` helps i notice this UP/DOWN flap when i start/shutdown another machine with direct connection to that one (nve card on
started getting repeated "bge0: PHY read timed out" messages
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: 0x3003> mem 0xfeab-0xfeab 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: 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]"
Re: bge0: PHY read timed out
On Sep 9, 2006, at 11:52 PM, Chad Leigh -- Shire.Net LLC wrote: I have a machine that is acting up. It was doing this a couple weeks ago and I replaced the motherboard thinking that maybe the physical ethernet port was going bad (connector or chip). The new motherboard is starting to act up the same way after a week or two of running fine and I am wondering if something else might be the issue. I forgot to mention that the MB at issue is the Tyan S2850 single opteron MB. This particular server had its MB replaced a week or two ago for the same sort of issue on bge1 that got progressively worse and I eventually turned it off in the BIOS. Then a while later it started seeming to freeze up with this same issue as listed below and I replaced the MB, which is starting to show the same issue. I have a few other servers with the same MB and they have never had any issues. Chad After the uname I list the stuff from the syslog before it goes off the net and my auto rebooter power strip thinks it has crashed and forces a reboot (which I have now turned off so I can go in and look more next time it happens). This did not happen for the last week or two and all of a sudden happened about 5 times today... # uname -a FreeBSD whitwell.shire.net 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Fri May 19 01:50:39 MDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/ sys/WHITWELL i386 # Sep 9 20:49:02 whitwell kernel: bge0: PHY read timed out Sep 9 20:49:02 whitwell last message repeated 3 times Sep 9 20:49:02 whitwell kernel: bge0: link state changed to DOWN Sep 9 20:49:04 whitwell kernel: bge0: PHY read timed out What does this message mean? PHY read timed out? I did a google on it but the issues were various other things. Could this be a bad cable? 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 "freebsd-questions- [EMAIL PROTECTED]" --- 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]"
bge0: PHY read timed out
I have a machine that is acting up. It was doing this a couple weeks ago and I replaced the motherboard thinking that maybe the physical ethernet port was going bad (connector or chip). The new motherboard is starting to act up the same way after a week or two of running fine and I am wondering if something else might be the issue. After the uname I list the stuff from the syslog before it goes off the net and my auto rebooter power strip thinks it has crashed and forces a reboot (which I have now turned off so I can go in and look more next time it happens). This did not happen for the last week or two and all of a sudden happened about 5 times today... # uname -a FreeBSD whitwell.shire.net 6.1-RELEASE FreeBSD 6.1-RELEASE #1: Fri May 19 01:50:39 MDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ WHITWELL i386 # Sep 9 20:49:02 whitwell kernel: bge0: PHY read timed out Sep 9 20:49:02 whitwell last message repeated 3 times Sep 9 20:49:02 whitwell kernel: bge0: link state changed to DOWN Sep 9 20:49:04 whitwell kernel: bge0: PHY read timed out What does this message mean? PHY read timed out? I did a google on it but the issues were various other things. Could this be a bad cable? 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]"
