I remember 'chip creep' being a question on my Novell service and support exam way back when. I laughed, but a few years later, had a video card that was acting erratic with an odd pattern. Thought it was a long shot, but all the video RAM chips had crept out halfway. Pushed them back in, problem solved. Just heating and cooling can do it.
Chuck -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tony Li Sent: Monday, July 05, 2010 8:05 PM To: Alan Buxey Cc: Gert Doering; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Cisco 6509 reboots on its own... again... On Jul 5, 2010, at 4:50 AM, Alan Buxey wrote: >> ==> Blades didn't move for months if not years for some ! Plus, diags passed >> fully without any kind of problem ! > > we had an issue earlier this year when the temperature of a data > centre went up by 3 degrees and cooled repidly. yep. reseating the blade > fixed it. hmmm. :-) Thermal cycling is a fact of life, as is vibration and connector corrosion. Yes, 3 degrees doesn't seem like much, but at the microscopic scale, it's more than enough to cause boards (and parts!) to expand and contract. When you combine that with the continual vibration of fans, and corrosion from general atmospheric contact, Bad Things can and do happen. Tony _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
