Kevin, Do you have the crashinfo files or TAC SR # of your SegV crash? If yes, please share.
Either way, I'd hate to bust your bubble and this is the last time I'll say this, SegV exceptions in IOS are always caused by software bugs. Mem corruptions/leaks/fragmentations, parity errors, failed hardware etc. will be appropriately reported in the crashdumps and discerning expert engineers are able to quickly decipher and resolve. As you probably know, incompetent level 1, 2 TAC 'personnel' always throw hardware at everything so they "band-aid issues, close your case and move on to the next one. Your VAM might have failed, but it's failure is a separate issue from your SegV outage. eninja www.multiven.com - simple, efficient & affordable maintenance for all networks™ On Nov 11, 2010, at 5:12 PM, Kevin Graham <[email protected]> wrote: > > >> Rather than speculate, do you have an actual example of a >> crash that IOS reported as 'SegV exception' that was caused > >> by failed hardware? > > Yes, I've had a failing VAM manifest itself with SegV crashes. > Eventually it died completely and wasn't recognized on boot; > once replaced, router was stable as-is. > > Ken's right on, there are some classes of hardware faults, > namely feeding corrupted data into the system in-between > validation points that could cause a software-triggered SegV > crash. > > Hosing a pointer most commonly would be a software error, but > hardware can absolutely contribute. > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
