ports bouncing after NTP time set? bad switch?

[expohl]

I have a ws-12-250-dc that has been working great for years, never an issue, on the 23rd I lost connectivity to some links and when I logged into the switch port 8 was receiving POE voltage but had no ethernet link, when bounced everything returned to normal. Upon checking the logs it seems that about half of the ports when up/down right after an NTP event, does this possibly mean the switch is going bad? The other ports involved besides port 8 came back with no bounce needed.

1.4.8rc7



Dec 31 16:01:09 system: starting ntpclient
Dec 31 16:01:17 Port: link state changed to 'up' (1G) on port 9
Mar 23 14:03:03 system: time set by NTP server
Mar 23 14:03:26 Port: link state changed to 'down' on port 6
Mar 23 14:03:29 Port: link state changed to 'up' (1G) on port 6
Mar 23 14:03:41 Port: link state changed to 'down' on port 6
Mar 23 14:03:44 Port: link state changed to 'up' (1G) on port 6
Mar 23 14:03:46 Port: link state changed to 'up' (1G) on port 5
Mar 23 14:03:47 Port: link state changed to 'up' (1G) on port 10
Mar 23 14:04:07 Port: link state changed to 'down' on port 5
Mar 23 14:04:07 Port: link state changed to 'down' on port 10
Mar 23 14:04:08 Port: link state changed to 'up' (1G) on port 5
Mar 23 14:04:09 Port: link state changed to 'up' (1G) on port 10
Mar 23 14:04:22 Port: link state changed to 'down' on port 3
Mar 23 14:04:24 Port: link state changed to 'up' (1G) on port 3
Mar 23 14:04:33 Port: link state changed to 'down' on port 3
Mar 23 14:04:36 Port: link state changed to 'up' (1G) on port 3
Mar 23 14:04:37 UI: Port 8 bounced by admin (10.10.10.20)
Mar 23 14:04:37 switch[954]: Port 8 Link: changed from poe override
Mar 23 14:04:48 Port: link state changed to 'up' (100M-F) on port 8
Mar 23 14:05:02 Port: link state changed to 'down' on port 8
Mar 23 14:05:03 Port: link state changed to 'up' (100M-F) on port 8
Mar 23 14:05:06 Port: link state changed to 'down' on port 8
Mar 23 14:05:11 Port: link state changed to 'up' (100M-F) on port 8

[sirhc]

Well for 1 firmware is WAY OLD - Upgrade to v1.5.2

I would pull the unit back to shop and upgrade and bench test as explained here: viewtopic.php?f=6&t=2780