[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC X.25 for OpenVMS AXP |
|
| Moderator: | OZROCK::MUGGERIDGE |
|
| Created: | Mon Jan 18 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 524 |
| Total number of notes: | 2218 |
512.0. "Alpha X.25 V1.0-E RSVD_LP crash" by CSC32::J_SOBECKI (John Sobecki, DTN 592-4101, CXO3-2/D2) Thu Apr 17 1997 15:09
Hello,
Need some pointers on analyzing a Alpha X.25 V1.0-E crash. I got the
dump from the customer, but my system has V1.0-G installed.
I could not get the X25_PANIC info out, so I pulled the
X25$KERNEL_RTL.EXE image out of the V1.0-E kit to read in as the symbol
table, but still no luck.
Any ideas would be helpful. I did notice a strange "EMAA Not Loaded"
error listed below from the net show summary command.
Thanks,
John Sobecki
CSC/Colorado
Crashdump Summary Information:
------------------------------
Crash Time: 10-APR-1997 11:36:16.53
Bugcheck Type: RSVD_LP, Reserved for Digital layered product use
Node: NPEMSA (Clustered)
CPU Type: AlphaServer 2100A 5/250
VMS Version: V6.2-1H3
Current Process: NET$EVD
Current Image: <not available>
Failing PC: FFFFFFFF 9BCD2214
Failing PS: 18000000 00000804
Module: X25$KERNEL_RTL
Offset: 00000214
SDA> READ/IMAGE sys$login:X25$KERNEL_RTL ! X.25 1.0-E image
SDA> show sym/all x25_panic
Symbols sorted by name
----------------------
X25_PANIC_ = 9BCF36F0 : 00083089
X25_PANIC_FILE = 9BCEE650 : 00000000
X25_PANIC_LEVEL = 9BCEE65C : 00000000
X25_PANIC_LINE = 9BCEE654 : 00000000
X25_PANIC_MESSAGE = 9BCEE660 : 00000000
X25_PANIC_MODULE = 9BCEE658 : 00000000
X25_PANIC__C = 9BCE9660 : 23DEFFC0
DECnet/OSI For OpenVMS Summary
------------------------------
DECnet/OSI for OpenVMS Version V6.3-ECO06 8-NOV-1996 18:03:20.49
EMAA Not Loaded
Registered VCMS (Vax Communication Modules)
ID: 513, "Data Link - CSMACD & FDDI"
ID: 769, "Alias (Routing portion)"
ID: 1280, "Session Control"
ID: 521, "Data Link - LLC2"
ID: 515, "Data Link - HDLC Synchronous"
ID: 520, "Data Link - LAPB"
ID: 517, "Data Link - X.25"
ID: 768, "Network Routing"
ID: 1024, "Transport - NSP"
ID: 1043, "Unknown VCI_ID name"
ID: 1025, "Transport - OSI"
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 512.1 | Crash Dump Analysis hints | OZROCK::HARTWIG | Arthur Hartwig, TaN Engineering-Australia | Fri Apr 18 1997 01:39 | 30 |
| I would suggest as a good starting point:
1) Read in the symbols from the V1.0-E images
2) Issue a SDA SHOW STACK command
3) Issue SDA SHOW CALL command, then SHOW CALL/NEXT repeatedly until
you run out of call frames.
4) locate the first module "above" X25$KERNEL_RTL in the call stack.
5) read in its symbol table (v1.0-e) and show the X25_PANIC symbols
in that module.
6) Submit an IPMT with a pointer to the crash dump so the EDS team get
some crash dump analysis practice.
Somewhere along the line the X25_PANIC symbols were in a module that
was linked into ALL X.25 exec images rather than the X25$KERNEL_RTL
image. An X.25 panic was invoked by calling a x25_panic function
(which was replicated in all X.25 images) which then called a BUGCHECK
function in X25$KERNEL_RTL. The x25_panic function should live in
X25$KERNEL_RTL so there is only one set of x25_panic_??? symbols.
I can't recall how much of this happened for V1.0-g. the registers
r2 to r5 at the time of the crash (or was it r16 to r22) may also
contain the information about file, line and "panic text" in v1.0-e.
Good hunting.
|