Segmentation Violations (SegV) exceptions are _always_ caused by a bug in Cisco IOS and could be triggered by either of the following:
- Accessing an invalid memory address e.g. attempting to access the lowest 16KB of memory on powerPC platforms - Writing to a read-only memory region - A jump to an invalid PC (often 0x0) Contact your network maintenance service provider/Cisco to get your bug fix. More info at... - http://www.cisco.com/en/US/products/hw/routers/ps359/products_tech_note09186a0080189ddb.shtml - http://solutions.mysolvr.com/Spurious_Memory_Accesses eninja On Mon, Jun 8, 2009 at 11:29 AM, Richey <[email protected]> wrote: > I am setting up Tacacs+ on all of our far end routers so I can run rancid. > I have found several 1720s and a 2621 that crash when I log in to them and > issue the "sh run" command. They reboot quickly and then I don't have a > problem with the "sh run" command after the reload. If I look at the > output from a "sh ver" I get System returned to ROM by error - a SegV > exception, PC 0x8066A150. This seems to only be a small number of > routers. They are in different environments (one is in a server room, > another on the wall in a warehouse, etc) The 1700s are running various > versions of the same image type. The only thing that they all have in > common is that it's been months since anyone has logged into the router. > Is this some bug that comes from long uptimes without any activity at the > CLI? > > > > Richey > > > > > > _______________________________________________ > 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/
