Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Crash while pinging from telnet
#1
Running the LITE build on a 5101.

CM> ping 10.232.199.113


>>> YIKES... looks like you may have a problem! <<<

r0/zero=00000000 r1/at =fffffffe r2/v0 =1000ffb2 r3/v1 =807dd5f8
r4/a0 =807e8cf0 r5/a1 =80018bb0 r6/a2 =807e8d58 r7/a3 =807e8cf0
r8/t0 =807e44f8 r9/t1 =01010101 r10/t2 =0000006d r11/t3 =0000000b
r12/t4 =803457f0 r13/t5 =000008d0 r14/t6 =b8000000 r15/t7 =00000000
r16/s0 =807e58a9 r17/s1 =807dd618 r18/s2 =00000001 r19/s3 =807de714
r20/s4 =807e44f8 r21/s5 =00000002 r22/s6 =00000001 r23/s7 =11110017
r24/t8 =00000000 r25/t9 =0000005c r26/k0 =00000001 r27/k1 =8027ad5c
r28/gp =8034d2a0 r29/sp =807e44b0 r30/fp =807e47e0 r31/ra =8009b248

PC : 0x8009903c error addr: 0x1000ffba
cause: 0x00000010 status: 0x1000ff03

BCM interrupt enable: ffffffff, status: 00000000
Instruction at PC: 0x8c430008

entry 80098fd0 called from 8009b240
entry 8009aa80 called from 8009ddf4
entry 8009dbc0 called from 8009ee88
entry 8009ed44 called from 80142828
entry 8014272c called from 8019bc84
entry 8019bbd8 called from 8024d824
entry 8024d7ec called from 8024d7e4
entry 8024d7ec Return address (00000000) invalid. Trace stops.

Task: ConsoleThread
---------------------------------------------------
ID: 0x000c
Handle: 0x807ec0b8
Set Priority: 27
Current Priority: 27
State: SUSP
Stack Base: 0x807de820
Stack Size: 24576 bytes
Stack Used: 3536 bytes
Stack Sta
ck Stack
TaskId TaskName Priority State Size Use
d Margin
---------- -------------------------------- -------- -------- -------- -----
--- --------
0x80382e00 Idle Thread 31 RUN 2048 105
6 992
0x804067b8 Network alarm support 6 SLEEP 2256 186
4 392
0x80385ab0 Network support 7 SLEEP 8192 236
8 5824
0x80407508 pthread.00000800 15 EXIT 7852 109
6 6756
0x8037d7b0 tStartup 18 SLEEP 12288 521
6 7072
0x8043f4ac Rajko HttpD 23 SLEEP 3280 308
4 196
0x807f8f1c NonVol Device Async Helper 25 SLEEP 3072 141
2 1660
0x807ef4d0 Motorola Standby Switch Thread 23 SLEEP 4096 104
8 3048
0x807ee244 Motorola Vendor Ctl Thread 23 SLEEP 4096 50
0 3596
0x807f9b20 WDOG 17 RUN 5120 280
0 2320
0x807ec8c4 BFC Ping Thread 29 SLEEP 6144 180
0 4344
0x807ec0b8 ConsoleThread 27 SUSP 24576 353
6 21040
0x807ddf80 TelnetD 23 RUN 2256 225
6 0 OVERFLOW
0x807d38c8 Time Of Day Thread 23 SLEEP 6144 162
4 4520
0x807d3d04 CmDocsisIpThread 23 SLEEP 8192 206
8 6124
0x807ce5a0 CmBpiManagerThd 25 SLEEP 8192 49
2 7700
0x807b6128 CmDsxHelper 23 SLEEP 8192 149
6 6696
0x807d5270 CmDocsisCtlThread 21 SLEEP 8192 585
2 2340
0x807afbc8 Scan Downstream Thread 23 SLEEP 4096 169
2 2404
0x807aca28 RateShaping Thread 23 SLEEP 4096 144
0 2656
0x807f9c18 CMHL 23 RUN 4500 167
2 2828
0x807f9d10 CMHH 21 SLEEP 4500 163
2 2868
0x807f9e08 ENRX 23 RUN 4500 189
2 2608
0x807f9f00 ENTX 23 SLEEP 4500 116
8 3332
0x807f9ff8 ELNK 23 SLEEP 4500 76
8 3732
0x807fa0f0 USTX 23 SLEEP 4500 34
0 4160
0x807fa1e8 USRX 23 SLEEP 4500 37
2 4128
0x807fa2e0 UBCT 19 SLEEP 4500 34
0 4160
0x807fa3d8 USRN 23 SLEEP 4500 34
0 4160
0x80634034 DHCP Client Thread 23 SLEEP 12288 240
0 9888
0x807fa4d0 IpHalIst 23 RUN 4500 124
0 3260
0x8062e400 CmPropaneCtlThread 23 SLEEP 8192 130
0 6892
0x8062b8bc IGMP Thread 23 SLEEP 4096 175
6 2340
0x806220e4 CfgVB Thread 23 SLEEP 4096 254
0 1556
0x80620b34 DHCM 25 SLEEP 16384 48
8 15896
0x8061a97c NetToMedia Thread 23 SLEEP 4096 176
4 2332
0x80619084 Trap Thread 23 SLEEP 16384 48
8 15896
0x80582fac Event Log Thread 25 SLEEP 8192 214
0 6052
0x807f9698 SNMP Thread 21 SUSP 20480 537
6 15104
0x8055797c DHCP Server Thread 23 SLEEP 8192 75
2 7440
Done!
Reply
#2
well i got nothing, mostly due to the fact i have never tried ping from the haxorware shell, can i ask why you would?


ok now i think about it, it looks kind of like the old doss bug (a pointless bug as it could not be used remotely)
http://www.securityfocus.com/bid/40635/discuss
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply
#3
Same reason you would want to ping from a Cisco IOS shell or any other shell for that matter, for diagnostic purposes.

I just tried to do a simple ping, that shouldn't result in a DOS.
Reply
#4
The Lite version is missing some key components left out by Rajko.

Use the full DIAG version
Knowledge=Power
Reply
#5
(05-04-2011, 03:58 PM)DJX Wrote: Same reason you would want to ping from a Cisco IOS shell or any other shell for that matter, for diagnostic purposes.

I just tried to do a simple ping, that shouldn't result in a DOS.
Cisco IOS humm never used one of those
(05-04-2011, 04:08 PM)ABMJR Wrote: The Lite version is missing some key components left out by Rajko.

Use the full DIAG version
good catch i should have seen that
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)