6509 Sup7203BXL Error

Unanswered Question
Aug 31st, 2008

Hi,

Has anyone of you seen this error? I tried to use Cisco Output

Interpreter but haven't seen any information about the error. Thanks.

000747: Aug 29 20:16:10.000 UTC: %DUMPER-3-PROCINFO: pid = 16426:

(sbin/udp.proc), terminated due to signal SIGSEGV, Segmentation

violation (Address not mapped)

000748: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

zero at v0 v1

000749: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R0

00000000 7228D517 00000000 00000000

000750: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

a0 a1 a2 a3

000751: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R4

0106136C 01061358 000007E9 0000402A

000752: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

t0 t1 t2 t3

000753: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R8

00000000 00000001 00000004 00000001

000754: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

t4 t5 t6 t7

000755: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R12

CDD182FC D05155F1 FF000000 00000000

000756: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

s0 s1 s2 s3

000757: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R16

00000000 00F71930 01061358 00F71948

000758: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

s4 s5 s6 s7

000759: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R20

01061340 6C0BA940 7C263170 01061138

000760: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

t8 t9 k0 k1

000761: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R24

7264CCA4 76117C90 00000000 00000000

000762: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

gp sp s8 ra

000763: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R28

7C5715E0 00F718F0 00F71918 7646AFF4

000764: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

sr lo hi bad

000765: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R32

1000FC73 00000000 00000000 0000010C

000766: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426:

cause pc epc

000767: Aug 29 20:16:10.000 UTC: %DUMPER-3-REGISTERS_INFO: 16426: R36

00800008 7646B038 00000000

000768: Aug 29 20:16:10.000 UTC: %DUMPER-3-TRACE_BACK_INFO: 16426:

(s72033_rp-adventerprisek9_

wan-64-dso-p.so+0x2038)

(s72033_rp-adventerprisek9_wan-51-dso-p.so+0x10324)

(s72033_rp-adventerprisek9_wan-51-dso-p.so+0x16100) (libc.so+0x48204)

(libc.so+0x47EC4) (s72033_rp-adventerprisek9_wan-1-dso-p.so+0x5B64)

(s72033_rp-adventerprisek9_wan-1-dso-p.so+0x5B04)

(s72033_rp-adventerprisek9_wan-1-dso-p.so+0x507C)

(s72033_rp-adventerprisek9_wan-1-dso-p.so+0x397C)

(s72033_rp-adventerprisek9_wan-1-dso-p.so+0x3F48) (libc.so+0x252D4)

(libc.so+0x127AC)

000769: Aug 29 20:16:11.000 UTC: %DUMPER-3-CRASHINFO_FILE_NAME: 16426:

Crashinfo for process sbin/udp.proc at

bootflash:/crashinfo_udp.proc-20080829-201610

000770: Aug 29 20:16:11.000 UTC: %DUMPER-6-BAD_PATH: 16426: Choice 1

either not configured or bad path. Trying next choice.

000771: Aug 29 20:16:11.000 UTC: %DUMPER-6-BAD_PATH: 16426: Choice 2

either not configured or bad path. Trying next choice.

000772: Aug 29 20:16:11.000 UTC: %DUMPER-6-BAD_PATH: 16426: Choice 3

either not configured or bad path. Trying next choice.

000773: Aug 29 20:16:12.000 UTC: %DUMPER-3-DUMP_FAILURE: 16426: Core

dump failed: Could not create core

000774: Aug 29 20:16:12.000 UTC: %SYSMGR-3-ABNORMTERM: udp.proc:1 (jid

98) abnormally terminated, restart scheduled

000775: Aug 29 20:16:13.000 UTC: %SYSMGR-6-RESPAWN: Process udp.proc:1

has been respawned

Regards,

John

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Sun, 08/31/2008 - 22:39

Hello John,

the tool to be used should be the error message decoder but it doesn't provide any answer.

I haven't found any ref in the error and system messages guide for release 12.2SX.

I can say that these messages have been written by a process DUMPER that is trying to create a core dump just after a crash.

An error occurred during this process and so a detailed list of steps is provided.

000747: Aug 29 20:16:10.000 UTC: %DUMPER-3-PROCINFO: pid = 16426:

(sbin/udp.proc), terminated due to signal SIGSEGV, Segmentation

violation (Address not mapped)

000773: Aug 29 20:16:12.000 UTC: %DUMPER-3-DUMP_FAILURE: 16426: Core

dump failed: Could not create core

the overall result is that the core dump could not be created.

Hope to help

Giuseppe

John Patrick Lopez Mon, 09/01/2008 - 14:27

Hey thanks for the reply. So what's this? Is this a hardware or software issue? Can this be resolved by updating the Cisco IOS? Thanks.

Giuseppe Larosa Mon, 09/01/2008 - 23:16

Hello John,

the core dump is written when a crash happens.

I think this is a software issue you can think of an IOS upgrade.

Hat it happened only once or more times ?

Hope to help

Giuseppe

Actions

This Discussion