Ken, Rather than speculate, do you have an actual example of a crash that IOS reported as 'SegV exception' that was caused by failed hardware?
People come here for answers, not speculation. eninja On Nov 11, 2010, at 6:08 AM, "Matlock, Kenneth L" <[email protected]> wrote: > Always, huh? > > So it's 100% not possible ever for one or more memory locations to get > corrupted (due to a bad memory chip), and put an invalid pointer in an array, > and the IOS uses that pointer to access a memory area it's not > supposed/allowed to? > > I'm not sure what perfect world you live in, but it certainly doesn't match > reality. Hardware problems can (and frequently DO) appear as software > issues.... > > Ken > > ________________________________ > > From: [email protected] on behalf of Eninja > Sent: Wed 11/10/2010 10:20 PM > To: Michael Loftis > Cc: Dominic Ogbonna; <[email protected]> > Subject: Re: [c-nsp] Unstable IOS Version for LNS on Cisco 7206 NPE-G2 > > > > Michael, > > 'stuck bits'? > > SegV exceptions are _always_ caused by software bugs. > > http://bit.ly/98QqhO > > eninja ;-) > > > > On Nov 10, 2010, at 8:56 PM, Michael Loftis <[email protected]> wrote: > >> SegV is most certainly not always software. Stuck bits in IO memory or in >> memory used by a PPP session description could easily cause a SegV. The POST >> isn't completely exhaustive. examining the crash dumps can help discern if >> its a hardware or software issue. I wouldn't rule out either. Open a TAC >> case for sure. > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
