| Author |
Message |
Carlo
Guest
|
Posted:
Sat Oct 16, 2004 4:03 am Post subject:
Bus Error |
|
|
One of my BLN's rebooted twice today. Slot 3 is an Octal Sync card.
Does this look like a hardware error?
# 544: 10/15/2004 17:43:02.300 FAULT SLOT 3 GAME Code: 164
Error: exception vector 2 - Bus error
system restart
This was all I could find on Nortels web site.
Entity Code/Event Code 5/164
Decimal Identifier 16778660
Severity: Fault
Message: Error: exception vector <vector_no.> - <description>
Meaning: GAME detected an unexpected hardware interrupt, typically a
bus error.
Action: Call the Bay Networks Technical Solutions Center to report the
error message.
Call Bay Networks. Sorry, no support contract.
Here is a list of all the hardware in the BLN.
bcc> show hardware slots
show hardware slots Oct 15, 2004
19:26:22 [GMT-5]
Processor Net Module
-----------------------------------------
-----------------------------
Slot Module Revision Serial# Module Revision Serial
No.
---- ---------------- -------- ---------- --------- --------
----------
1 srmf 5 21105 srml 20
14609
2 are 15 1625 atmcoc3mm 7
4e3
3 o60 11 32502 osync 6
266d
4 fre2 22 99557 de100 5
3d97
bcc>
Should I be shopping for a new Osync card or something else?
Thanks. Carlo |
|
| Back to top |
|
 |
Julio Arruda
Guest
|
Posted:
Mon Oct 18, 2004 3:40 am Post subject:
Re: Bus Error |
|
|
Carlo wrote:
| Quote: | One of my BLN's rebooted twice today. Slot 3 is an Octal Sync card.
Does this look like a hardware error?
# 544: 10/15/2004 17:43:02.300 FAULT SLOT 3 GAME Code: 164
Error: exception vector 2 - Bus error
system restart
This was all I could find on Nortels web site.
Entity Code/Event Code 5/164
Decimal Identifier 16778660
Severity: Fault
Message: Error: exception vector <vector_no.> - <description
Meaning: GAME detected an unexpected hardware interrupt, typically a
bus error.
Action: Call the Bay Networks Technical Solutions Center to report the
error message.
Call Bay Networks. Sorry, no support contract.
Here is a list of all the hardware in the BLN.
bcc> show hardware slots
show hardware slots Oct 15, 2004
19:26:22 [GMT-5]
Processor Net Module
-----------------------------------------
-----------------------------
Slot Module Revision Serial# Module Revision Serial
No.
---- ---------------- -------- ---------- --------- --------
----------
1 srmf 5 21105 srml 20
14609
2 are 15 1625 atmcoc3mm 7
4e3
3 o60 11 32502 osync 6
266d
4 fre2 22 99557 de100 5
3d97
bcc
Should I be shopping for a new Osync card or something else?
|
I would first open a case with the whole log file saved (save log
blablabla.log). Bus Errors from what I remember can very easily be
traced to a software problem (kind of a "windows BSOD" for that specific
slot). The log file itself would have a trace of the stack, and support
would be able to use it to locate the exact point of the error (loadmap
and etc are also saved in the log, with this and the stack dump, you
would find the process running). |
|
| Back to top |
|
 |
MC
Guest
|
Posted:
Wed Oct 20, 2004 4:14 am Post subject:
Re: Bus Error |
|
|
What a coinscedence! I had an octal card with the same error on one of my
BCN's yesterday!
I have seen this error a couple of times before, usually reset the slot and
never see the same error again for a long time.
"Julio Arruda" <jarruda@nospamnortelnetworks.com> wrote in message
news:ckuvsq$o9d$1@zcars0v6.ca.nortel.com...
| Quote: | Carlo wrote:
One of my BLN's rebooted twice today. Slot 3 is an Octal Sync card.
Does this look like a hardware error?
# 544: 10/15/2004 17:43:02.300 FAULT SLOT 3 GAME Code: 164
Error: exception vector 2 - Bus error
system restart
This was all I could find on Nortels web site.
Entity Code/Event Code 5/164
Decimal Identifier 16778660
Severity: Fault
Message: Error: exception vector <vector_no.> - <description
Meaning: GAME detected an unexpected hardware interrupt, typically a
bus error.
Action: Call the Bay Networks Technical Solutions Center to report the
error message.
Call Bay Networks. Sorry, no support contract.
Here is a list of all the hardware in the BLN.
bcc> show hardware slots
show hardware slots Oct 15, 2004
19:26:22 [GMT-5]
Processor Net Module
-----------------------------------------
-----------------------------
Slot Module Revision Serial# Module Revision Serial
No.
---- ---------------- -------- ---------- --------- --------
----------
1 srmf 5 21105 srml 20
14609
2 are 15 1625 atmcoc3mm 7
4e3
3 o60 11 32502 osync 6
266d
4 fre2 22 99557 de100 5
3d97
bcc
Should I be shopping for a new Osync card or something else?
I would first open a case with the whole log file saved (save log
blablabla.log). Bus Errors from what I remember can very easily be
traced to a software problem (kind of a "windows BSOD" for that specific
slot). The log file itself would have a trace of the stack, and support
would be able to use it to locate the exact point of the error (loadmap
and etc are also saved in the log, with this and the stack dump, you
would find the process running).
|
|
|
| Back to top |
|
 |
Carlo
Guest
|
Posted:
Wed Oct 20, 2004 8:15 pm Post subject:
Re: Bus Error |
|
|
"MC" <mwclarke1@yahoo.com> wrote in message news:<FXhdd.85311$yp.32651@bignews1.bellsouth.net>...
| Quote: | What a coinscedence! I had an octal card with the same error on one of my
BCN's yesterday!
I have seen this error a couple of times before, usually reset the slot and
never see the same error again for a long time.
"Julio Arruda" <jarruda@nospamnortelnetworks.com> wrote in message
news:ckuvsq$o9d$1@zcars0v6.ca.nortel.com...
Carlo wrote:
One of my BLN's rebooted twice today. Slot 3 is an Octal Sync card.
Does this look like a hardware error?
# 544: 10/15/2004 17:43:02.300 FAULT SLOT 3 GAME Code: 164
Error: exception vector 2 - Bus error
system restart
This was all I could find on Nortels web site.
Entity Code/Event Code 5/164
Decimal Identifier 16778660
Severity: Fault
Message: Error: exception vector <vector_no.> - <description
Meaning: GAME detected an unexpected hardware interrupt, typically a
bus error.
Action: Call the Bay Networks Technical Solutions Center to report the
error message.
Call Bay Networks. Sorry, no support contract.
Here is a list of all the hardware in the BLN.
bcc> show hardware slots
show hardware slots Oct 15, 2004
19:26:22 [GMT-5]
Processor Net Module
-----------------------------------------
-----------------------------
Slot Module Revision Serial# Module Revision Serial
No.
---- ---------------- -------- ---------- --------- --------
----------
1 srmf 5 21105 srml 20
14609
2 are 15 1625 atmcoc3mm 7
4e3
3 o60 11 32502 osync 6
266d
4 fre2 22 99557 de100 5
3d97
bcc
Should I be shopping for a new Osync card or something else?
I would first open a case with the whole log file saved (save log
blablabla.log). Bus Errors from what I remember can very easily be
traced to a software problem (kind of a "windows BSOD" for that specific
slot). The log file itself would have a trace of the stack, and support
would be able to use it to locate the exact point of the error (loadmap
and etc are also saved in the log, with this and the stack dump, you
would find the process running).
|
The error has happened four times within the last week. Below is an
excerpt of the log file at the time of the crash. The log has "No
crash dump' retcode = 0"
Is this because the system is set no to save a crash dump? Could this
be due to a DoS attack?
# 339: 10/19/04 21:20:57 DEBUG SLOT 3 GAME Event
Code: 64
Log fltr: 171 entities, msk def: TFWID
0: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
20: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
40: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
60: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
80: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
100: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
120: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
140: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
160: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
Boot image name: 2:bn.exe
Configuration name: 2:config
CPU id 769 rev 11 ser 32502 Link Module id 4352 rev 6 ser 9837
No crash dump; retcode = 0
# 340: 10/19/04 21:20:59 INFO SLOT 3 GAME Event
Code: 11
Starting image rel/14.0.3.0/ Wed Sep 12 19:43:01 EDT 2001
# 341: 10/19/04 21:20:59 DEBUG SLOT 3 GAME Event
Code: 64
BB RCVR: Max Deliver 509 @ 0x317c91f2 Max Clip 0 @ 0x317c91f4
# 342: 10/19/04 21:21:00 INFO SLOT 3 GAME Event
Code: 9
BackBone 0 became re-connected
BackBone 1 became re-connected
BackBone 2 became re-connected
BackBone 3 became re-connected
# 343: 10/19/04 21:21:00 DEBUG SLOT 3 GAME Event
Code: 73
@REMOTE 4 FSM: DOWN -> SYNC (000011: 88000005 18e0b4c 30000000
20000000)
@REMOTE 4 FSM: SYNC -> FLOW (000011: 88000006 18e0b4c 30000000
20000000)
# 344: 10/19/04 21:21:00 INFO SLOT 3 GAME Event
Code: 10
slot 4 became re-connected
# 345: 10/19/04 21:21:00 DEBUG SLOT 3 GAME Event
Code: 77
GID_CB: gate 0x000d1 @ 0x30042a40 (RD=1) - gid_add: ADDING NEW SEGMENT
free: head=0x00008 tail=0x00000->0x1ffff/0x000ff (cnt=248)
curr: head=0x00000 tail=0x00000->0x1ffff/0x00000 (cnt=0)
next: head=0x00000 tail=0x00000->0x1ffff/0x00000 (cnt=0)
@REMOTE 2 FSM: DOWN -> SYNC (000012: a0000004 18e0d24 18000000
08000000)
@REMOTE 2 FSM: SYNC -> FLOW (000012: a0000005 18e0d24 18000000
08000000)
# 346: 10/19/04 21:21:00 INFO SLOT 3 GAME Event
Code: 10
slot 2 became re-connected
# 347: 10/19/04 21:21:00 DEBUG SLOT 3 GAME Event
Code: 73
@REMOTE 4 FSM: ACTIV -> DOWN (000014: 88000004 18e0b50 20000000
20000000)
Setting slowboard reg = 0x7efe
# 348: 10/19/04 21:21:00 WARNING SLOT 3 GAME Event
Code: 8
slot 4 became disconnected
# 349: 10/19/04 21:21:00 DEBUG SLOT 3 GAME Event
Code: 73
@REMOTE 4 FSM: DOWN -> SYNC (000015: 88000005 18e0b50 20000000
20000000)
@REMOTE 2 FSM: ACTIV -> DOWN (000016: a0000004 18e0d28 08000000
08000000)
Setting slowboard reg = 0x7efe
# 350: 10/19/04 21:21:00 WARNING SLOT 3 GAME Event
Code: 8
slot 2 became disconnected |
|
| Back to top |
|
 |
Julio Arruda
Guest
|
Posted:
Thu Oct 21, 2004 1:34 am Post subject:
Re: Bus Error |
|
|
Carlo wrote:
| Quote: |
The error has happened four times within the last week. Below is an
excerpt of the log file at the time of the crash. The log has "No
crash dump' retcode = 0"
Is this because the system is set no to save a crash dump? Could this
be due to a DoS attack?
# 339: 10/19/04 21:20:57 DEBUG SLOT 3 GAME Event
Code: 64
Log fltr: 171 entities, msk def: TFWID
0: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
20: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
40: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
60: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
80: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
100: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
120: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
140: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
160: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
Boot image name: 2:bn.exe
Configuration name: 2:config
CPU id 769 rev 11 ser 32502 Link Module id 4352 rev 6 ser 9837
No crash dump; retcode = 0
|
In fact, the crash dump is not what you need, is the log file, in binary
if you do a log -ffitdw you would see it, but is a lot of things.
This is the 'post crash', they would need the whole log to see what
happens just before.
A DoS atack could create a condition like lack of memory (I don't think
would show as the Bus Error), but your best bet is to open a case with
support (having the config file and the log file saved to save time). |
|
| Back to top |
|
 |
Carlo
Guest
|
Posted:
Fri Oct 22, 2004 12:39 am Post subject:
Re: Bus Error |
|
|
Julio Arruda <jarruda@nospamnortelnetworks.com> wrote in message news:<cl6ll0$6tl$1@zcars0v6.ca.nortel.com>...
| Quote: | Carlo wrote:
The error has happened four times within the last week. Below is an
excerpt of the log file at the time of the crash. The log has "No
crash dump' retcode = 0"
Is this because the system is set no to save a crash dump? Could this
be due to a DoS attack?
# 339: 10/19/04 21:20:57 DEBUG SLOT 3 GAME Event
Code: 64
Log fltr: 171 entities, msk def: TFWID
0: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
20: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
40: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
60: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
80: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
100: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
120: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
140: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
160: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
Boot image name: 2:bn.exe
Configuration name: 2:config
CPU id 769 rev 11 ser 32502 Link Module id 4352 rev 6 ser 9837
No crash dump; retcode = 0
In fact, the crash dump is not what you need, is the log file, in binary
if you do a log -ffitdw you would see it, but is a lot of things.
This is the 'post crash', they would need the whole log to see what
happens just before.
A DoS atack could create a condition like lack of memory (I don't think
would show as the Bus Error), but your best bet is to open a case with
support (having the config file and the log file saved to save time).
|
We don't have support directly through Nortel. We have a time and
material contract with a third party group. Last time I called on a
different problem, they were of little help. Hopefully someone on
this list can provide some insight while I try to figure it out.
Here is part of the log (-ffitdw) just before, during and to the start
of the reboot.
# 431: 10/19/2004 18:44:34.925 DEBUG SLOT 3 GAME
Code: 213
WCLK2: resync adjusted time: c5221fa2.00000000 c5221fa2.09000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WCLK2: resync resync_sec: 00001c20.00000000 00000008.0000ef10
# 432: 10/19/2004 19:28:56.066 DEBUG SLOT 2 GAME
Code: 213
WCLK2: resync adjusted time: c5222a08.00000000 c5222a08.11000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WCLK2: resync resync_sec: 00001c20.00000000 00000039.0000ef10
# 433: 10/19/2004 20:44:34.953 DEBUG SLOT 3 GAME
Code: 213
WCLK2: resync adjusted time: c5223bc2.00000000 c5223bc2.10000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WCLK2: resync resync_sec: 00000e10.00000000 00000009.0000ef10
# 434: 10/19/2004 21:20:57.718 FAULT SLOT 3 GAME
Code: 164
Error: exception vector 2 - Bus error
# 435: 10/19/2004 21:20:57.718 DEBUG SLOT 3 GAME
Code: 64
Log fltr: 171 entities, msk def: TFWID
0: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
20: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
40: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
60: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
80: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
100: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
120: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
140: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
160: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
# 436: 10/19/2004 21:20:57.722 DEBUG SLOT 3 GAME
Code: 64
Boot image name: 2:bn.exe
Configuration name: 2:config
# 437: 10/19/2004 21:20:57.722 TRACE SLOT 3 GAME
Code: 169
File name Load Addr Size
----------------------------------------
--> arp.exe 0x31627c30 0100904
--> fr.exe 0x3156abb0 0121064
--> ftp.exe 0x31640670 0046024
--> tcp.exe 0x3164ba50 0076632
--> tftp.exe 0x3165e5c0 0021116
--> snmp.exe 0x31665860 0041352
--> tn.exe 0x31675a30 0044324
--> ip.exe 0x31680770 0457472
--> hwcomp.exe 0x3158b7d0 0037916
--> quicsync.exe 0x3159dc20 0188592
--> hdwanlm.exe 0x315d8d90 0009576
# 438: 10/19/2004 21:20:57.718 TRACE SLOT 3 GAME
Code: 143
STK GAME
REGS: SR=0x2304 ISP=0x30021eac MSP=0x00000000 USP=0x00000000
VBR=0x30000000 CACR=0xa0808000 SFC=1 DFC=1
DATA: 00000001 00003174 00000008 00003173 00000015 00000000 317e22a0
317e72a0
ADRS: 1000000f 3004d3e0 317c8ca0 317e5d68 3027cd98 3027f4c0 30021eec
30021eac
Func 0x30042282 (0x00000002, 0x30277566, 0x00000001, 0x00003174)
fp=0x30021e8c
Func 0x3004d428: BERR (bus fault RD long @ 0x1000001f) SR=2300
FSLW=01050020 fp=0x30021eb0
Func 0x3004d428 (0x00000059, 0x00002300, 0x0000004d, 0x30008400)
fp=0x30021eec
Func 0x30026408: INT 27 (Level 3 interrupt) SR=2004 FORM=0
fp=0x30021f10
Func 0x30026408 (0x00000000, 0x30021f50, 0x30036224, 0x3002423e)
fp=0x30021f18
Func 0x300242b8 (0x3002423e, 0x3027cd98, 0x00000000, 0x317e22a0)
fp=0x30021f24
Func 0x30036224 (0x00000002, 0x00000000, 0x0000001d, 0x00000000)
fp=0x30021f50
Func 0x3003bf90 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
fp=0x30021ff8
# 439: 10/19/2004 21:20:57.718 DEBUG SLOT 3 GAME
Code: 64
CPU id 769 rev 11 ser 32502 Link Module id 4352 rev 6 ser 9837
No crash dump; retcode = 0
# 440: 10/19/2004 21:20:57.718 FAULT SLOT 3 GAME
Code: 59
system restart
# 804: 10/20/2004 09:28:56.035 DEBUG SLOT 2 GAME
Code: 213
WCLK2: resync adjusted time: c522eee8.00000000 c522eee8.09000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WCLK2: resync resync_sec: 00003840.00000000 00000008.0000ef10
# 805: 10/20/2004 09:29:23.816 DEBUG SLOT 4 GAME
Code: 213
WCLK2: resync adjusted time: c522ef03.00000000 c522ef03.1f000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WCLK2: resync resync_sec: 00003840.00000000 00000047.0000ef10
# 806: 10/20/2004 10:22:13.726 DEBUG SLOT 3 GAME
Code: 213
WCLK2: resync adjusted time: c522fb65.00000000 c522fb65.08000000
WCLK2: resync error factor: 00000001.00000000 00000001.00000000
WC
# 807: 10/20/2004 10:52:01.558 FAULT SLOT 3 GAME
Code: 164
Error: exception vector 2 - Bus error
# 808: 10/20/2004 10:52:01.558 DEBUG SLOT 3 GAME
Code: 64
Log fltr: 171 entities, msk def: TFWID
0: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
20: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
40: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
60: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
80: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
100: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
120: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
140: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
160: 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f - 1f 1f 1f 1f 1f 1f 1f 1f 1f 1f
# 809: 10/20/2004 10:52:01.562 DEBUG SLOT 3 GAME
Code: 64
Boot image name: 2:bn.exe
Configuration name: 2:config
# 810: 10/20/2004 10:52:01.562 TRACE SLOT 3 GAME
Code: 169
File name Load Addr Size
----------------------------------------
--> arp.exe 0x31625810 0100904
--> fr.exe 0x315ae3a0 0121064
--> ftp.exe 0x3163e250 0046024
--> tcp.exe 0x31649630 0076632
--> tftp.exe 0x3165c1a0 0021116
--> snmp.exe 0x31663440 0041352
--> tn.exe 0x31673610 0044324
--> ip.exe 0x3167e350 0457472
--> hwcomp.exe 0x3156c220 0037916
--> quicsync.exe 0x315802e0 0188592
--> hdwanlm.exe 0x315d8d50 0009576
# 811: 10/20/2004 10:52:01.558 TRACE SLOT 3 GAME
Code: 143
STK GAME
REGS: SR=0x2304 ISP=0x30021eac MSP=0x00000000 USP=0x00000000
VBR=0x30000000 CACR=0xa0808000 SFC=1 DFC=1
DATA: 00000001 000005ef 00000008 000005ee 00000015 00000000 317e22a0
317e72a0
ADRS: 1800000f 3004d3e0 317c8ca0 317e2a3c 3027cd98 3027f4c0 30021eec
30021eac
Func 0x30042282 (0x00000002, 0x30277566, 0x00000001, 0x000005ef)
fp=0x30021e8c
Func 0x3004d428: BERR (bus fault RD long @ 0x1800001f) SR=2300
FSLW=01050020 fp=0x30021eb0
Func 0x3004d428 (0x00000059, 0x00002300, 0x0000004d, 0x30008400)
fp=0x30021eec
Func 0x30026408: INT 27 (Level 3 interrupt) SR=2004 FORM=0
fp=0x30021f10
Func 0x30026408 (0x00000000, 0x30021f50, 0x30036224, 0x3002423e)
fp=0x30021f18
Func 0x300242b8 (0x3002423e, 0x3027cd98, 0x00000000, 0x317e22a0)
fp=0x30021f24
Func 0x30036224 (0x00000002, 0x00000000, 0x00000015, 0x00000000)
fp=0x30021f50
Func 0x3003bf90 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
fp=0x30021ff8
# 812: 10/20/2004 10:52:01.558 DEBUG SLOT 3 GAME
Code: 64
CPU id 769 rev 11 ser 32502 Link Module id 4352 rev 6 ser 9837
No crash dump; retcode = 0 |
|
| Back to top |
|
 |
|
|
|
|