From: Harry Chan (harrychan.hk@gmail.com)
Date: Mon Aug 25 2008 - 22:57:28 ART
I think you need to contact the rack provider..
Extract from:
http://www.cisco.com/en/US/products/hw/routers/ps359/products_tech_note09186a0080189ddb.shtml
Cause of SegV Exceptions
SegV exceptions are always software problems. It is possible for
different software issues to cause a SegV exception, such as:
Access to an invalid memory address
Write access to a read-only memory region
A jump to an invalid PC (often 0x0)
Troubleshoot
If you have not manually reloaded or power-cycled the router since the
SegV exception, you can search for a known bug ID that matches the
Output Interpreter tool.
If you have the output of a show stacks command from your Cisco
device, you can use Output Interpreter to display potential issues and
fixes. To use Output Interpreter , you must be a registered customer,
be logged in, and have JavaScript enabled.
If the decoded output from the show stacks command matches a known
software bug, you receive the bug IDs of the most likely software bugs
to have caused the SegV exception. Click on the bug ID hyperlinks to
view additional bug details from the Cisco Bug Toolkit (registered
customers only) , which can help you determine the correct bug ID
match. Once you have identified a bug ID that matches, refer to the
"fixed in" field to determine the first Cisco IOS software version
that contains the fix for the bug.
If you are uncertain which bug ID matches or which Cisco IOS software
version contains the fix for the problem, a Cisco IOS software upgrade
to the latest version in your release train is one option that often
resolves the issue. This option often works because the latest version
usually contains the fix for a large number of bugs.
2008/8/25, Jonny English <redkidneybeans@gmail.com>:
> Hi,
>
> I am using a rack rental and router one all of a sudden just decided to keep
> rebooting.
>
> I was wondering does this happen if the WIC card craps out?
>
> here's the output that I get on router 1. The router just keeps rebooting.
> Any ideas? Thank you for any help..
>
> Writing crashinfo to flash:crashinfo_20020301-000031
>
> === Flushing messages (00:00:31 UTC Fri Mar 1 2002) ===
>
> Queued messages:
> *Mar 1 00:00:31.719: %SYS-3-LOGGER_FLUSHING: System pausing to ensure
> console debugging output.
>
> *Mar 1 00:00:07.907: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> VoIP-Null0, changed state to up
> *Mar 1 00:00:28.003: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed
> state to up
> *Mar 1 00:00:28.003: %LINK-3-UPDOWN: Interface Serial0/0, changed state to
> up
> *Mar 1 00:00:28.007: %LINK-3-UPDOWN: Interface Serial0/1, changed state to
> down
> *Mar 1 00:00:29.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> FastEthernet0/0, changed state to down
> *Mar 1 00:00:29.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0/0, changed state to up
> *Mar 1 00:00:29.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0/1, changed state to down
> *Mar 1 00:00:30.435: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Tunnel0, changed state to down
> *Mar 1 00:00:30.839: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Tunnel16, changed state to down
> *Mar 1 00:00:31.039: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Loopback0, changed state to up
> *** System received a SegV exception ***
> signal= 0xb, code= 0x1100, context= 0x85044898
> PC = 0x0, Vector = 0x1100, SP = 0x853c2ac8
>
> System Bootstrap, Version 12.2(7r) [cmong 7r], RELEASE SOFTWARE (fc1)
> Copyright (c) 2002 by cisco Systems, Inc.
> C2600 platform with 131072 Kbytes of main memory
>
> program load complete, entry point: 0x80008000, size: 0x1d3f630
> Self decompressing the image :
> ##########################################################################################################################################################################################################################################################################################################################################################################################################################################################################################
> [OK]
>
> Smart Init is disabled. IOMEM set to: 10
>
> Using iomem percentage: 10
>
> Restricted Rights Legend
>
> Use, duplication, or disclosure by the Government is
> subject to restrictions as set forth in subparagraph
> (c) of the Commercial Computer Software - Restricted
> Rights clause at FAR sec. 52.227-19 and subparagraph
> (c) (1) (ii) of the Rights in Technical Data and Computer
> Software clause at DFARS sec. 252.227-7013.
>
> cisco Systems, Inc.
> 170 West Tasman Drive
> San Jose, California 95134-1706
>
>
>
> Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version
> 12.4(4)T1, RELEASE SOFTWARE (fc4)
> Technical Support: http://www.cisco.com/techsupport
> Copyright (c) 1986-2005 by Cisco Systems, Inc.
> Compiled Wed 21-Dec-05 16:43 by ccai
> Image text-base: 0x80008098, data-base: 0x82C179F8
>
>
> This product contains cryptographic features and is subject to United
> States and local country laws governing import, export, transfer and
> use. Delivery of Cisco cryptographic products does not imply
> third-party authority to import, export, distribute or use encryption.
> Importers, exporters, distributors and users are responsible for
> compliance with U.S. and local country laws. By using this product you
> agree to comply with applicable laws and regulations. If you are unable
> to comply with U.S. and local laws, return this product immediately.
>
> A summary of U.S. laws governing Cisco cryptographic products may be found
> at:
> http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
>
> If you require further assistance please contact us by sending email to
> export@cisco.com.
>
> Cisco 2620XM (MPC860P) processor (revision 1.0) with 118784K/12288K bytes of
> memory.
> Processor board ID JAE073108DG (809517350)
> M860 processor: part number 5, mask 2
> 1 FastEthernet interface
> 2 Serial(sync/async) interfaces
> 32K bytes of NVRAM.
> 49152K bytes of processor board System flash (Read/Write)
>
> Slot is empty or does not support clock participate
> WIC slot is empty or does not support clock participate
>
> 00:00:31 UTC Fri Mar 1 2002: Unexpected exception to CPUvector 1100, PC =
> 0x0 , LR = 0x828B624C
>
> -Traceback= 0x828B624C 0x828B624C 0x81211F20 0x8122DD24 0x8122DEA0
> 0x8122DFFC 0x8122E0A0 0x816D932C 0x816D4670 0x816CD708 0x816D67E8 0x816D69E8
> 0x811DE340 0x811CA700 0x80260DD8 0x802643D0
>
> CPU Register Context:
> MSR = 0x08209032 CR = 0x93005053 CTR = 0x00000000 XER = 0xE0000A6F
> R0 = 0x00000000 R1 = 0x853C2AC8 R2 = 0x84DF0000 R3 = 0x86120500
> R4 = 0x00000000 R5 = 0x8612CB60 R6 = 0x00000000 R7 = 0x68010000
> R8 = 0x00000000 R9 = 0x00000001 R10 = 0x8612CC34 R11 = 0x00000000
> R12 = 0x33005053 R13 = 0xFFF4B518 R14 = 0x00000001 R15 = 0x0000067F
> R16 = 0x00000001 R17 = 0x00000000 R18 = 0x860F8398 R19 = 0x00000000
> R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x00000000
> R24 = 0x00000000 R25 = 0x852A9BD4 R26 = 0x852A9ABC R27 = 0x8612CBAC
> R28 = 0x00000000 R29 = 0x8612CB14 R30 = 0x86120500 R31 = 0x8612CB60
>
> Writing crashinfo to flash:crashinfo_20020301-000031
>
> === Flushing messages (00:00:31 UTC Fri Mar 1 2002) ===
>
> Queued messages:
> *Mar 1 00:00:31.735: %SYS-3-LOGGER_FLUSHING: System pausing to ensure
> console debugging output.
>
> *Mar 1 00:00:07.923: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> VoIP-Null0, changed state to up
> *Mar 1 00:00:28.019: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed
> state to up
> *Mar 1 00:00:28.019: %LINK-3-UPDOWN: Interface Serial0/0, changed state to
> up
> *Mar 1 00:00:28.023: %LINK-3-UPDOWN: Interface Serial0/1, changed state to
> down
> *Mar 1 00:00:29.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> FastEthernet0/0, changed state to down
> *Mar 1 00:00:29.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0/0, changed state to up
> *Mar 1 00:00:29.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0/1, changed state to down
> *Mar 1 00:00:30.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Tunnel0, changed state to down
> *Mar 1 00:00:30.855: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Tunnel16, changed state to down
> *Mar 1 00:00:31.055: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Loopback0, changed state to up
> *** System received a SegV exception ***
> signal= 0xb, code= 0x1100, context= 0x85044898
> PC = 0x0, Vector = 0x1100, SP = 0x853c2ac8
>
>
> --
> Thank You,
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:32 ART