| Author |
bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 09 2008 06:03 |
|
|
Hello,
I'm running v8.3 on alpha. previous to v7.3 I used to do a
$analyze/error/since
which now lead to erf.exe not found and the new command seems to be
$analyse/err/evl dump/since=today
which creates a .dmp file.
ok, so far, but how can it be inspected with a human's eye?
I wanted to see what happened: after booting up without doing anything else, I wanted to change something with
$@tcpip$config
where my first action was to shutdown tcp/ip with option 5.
After a few lines of normal log without indication any error, I got a
BUGCHECK code 7CC
NetDLLerr decnet datalink layer detected a fatal error.
sysdump.dmp was written and then the system rebooted automatically without problems (w/o error messages) and everything incl. tcp/ip starts up ok.
I found nothing pointing to the error in the various log files.
any ideas what might be wrong? ever since, the shutdown seem to end prematurely with black screen (without going to the prompt in console mode as it did in previous shutdown) after a screen full of normal operator log messages on this decstation3000 maybe without a newer sysdump being written - black screen - the system didn't display anything. still, I couldn't fine anything suspicious in the log files after reboot. (where is the shutdownlog by the way?)
any help is appreciated. |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
martinv2
Member
Posts: 107
Location: Goslar, Germany
Joined: 02.10.07 |
| Posted on June 09 2008 10:45 |
|
|
|
I'm running v8.3 on alpha. previous to v7.3 I used to do a
$analyze/error/since
which now lead to erf.exe not found and the new command seems to be
$analyse/err/evl dump/since=today
which creates a .dmp file.
ok, so far, but how can it be inspected with a human's eye?
The closest to what you're looking for is
$ analyze/error/elv translate /since=today
though it will report many non-translatable entries.
What you really need on 8.3 is WEBES which contains the System Event Analyzer (SEA).
I wanted to see what happened: after booting up without doing anything else, I wanted to change something with
$@tcpip$config
where my first action was to shutdown tcp/ip with option 5.
After a few lines of normal log without indication any error, I got a
BUGCHECK code 7CC
NetDLLerr decnet datalink layer detected a fatal error.
Sorry, no idea. Except that it's still a good idea to keep up-to-date with ECOs for TCP/IP Services.
HTH,
Martin
http://de.openvms.org/martinv/ |
 |
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 10 2008 00:26 |
|
|
thank you Stephen and Martin!
> keep up-to-date with ECOs for TCP/IP Services.
my memory tells me ECO = engineering change order?
are these available online?
p.s.: yesterday's shutdown worked w/o error and I got the usual >>> prompt. I'll nevertheless try to find out what went wrong when it did a bugcheck. |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 10 2008 01:13 |
|
|
just did
$ analyze/error/elv translate /since=9-jun
and cut out the rest before and after this bugcheck since the other bugchecks are all of type "operator" whereas the one below is the only one of type "NETDLLERR". The analyse/error result does not seem to reveal more useful details about the crash:
EVENT EVENT_TYPE_____________________________ TIMESTAMP______________ NODE__ EVENT_CLASS____________________________
66 Crash Restart 9-JUN-2008 11:10:33.97 A83 BUGCHECKS
DESCRIPTION__________________________________ RANGE___ VALUE_____________ TRANSLATED_VALUE_______________________
Hardware Architecture 4 Alpha
Hardware System Type 4
Logging CPU 0
Number of CPU's in Active Set 1
System Marketing Model 1064 DEC 3000 Model 600
Seconds Since Boot 315
Chip Type 2 EV4 (21064)
Error Sequence Number 209
DSR String DEC 3000 - M600
Operating System Version V8.3
Kernel Stack Pointer 0xFFFFFFFF87831CB8
Executive Stack Pointer 0xFFFFFFFF87833000
Supervisor Stack Pointer 0xFFFFFFFF8782D000
User Stack Pointer 0xFFFFFFFF8782D000
Register R0 0x00000000000000F1
Register R1 0xFFFFFFFF81CDDCC0
Register R2 0x0000000000000001
Register R3 0xFFFFFFFF82F1C408
Register R4 0xFFFFFFFF82F1C000
Register R5 0x0000000000000000
Register R6 0xFFFFFFFF82F1C410
Register R7 0x0000000000000003
Register R8 0x0000000000000000
Register R9 0x0000000000000000
Register R10 0x0000000000000002
Register R11 0xFFFFFFFF8180B1C8
Register R12 0x000000007BB99A28
Register R13 0xFFFFFFFF819E6B20
Register R14 0x0000000000000001
Register R15 0x0000000000000000
Register R16 0x00000000000007CC
Register R17 0x00000000000000D6
Register R18 0x0000000000000003
Register R19 0x0000000000000001
Register R20 0xFFFFFFFF81AD70C0
Register R21 0x0000000000000018
Register R22 0x0000000055435453
Register R23 0x0000000000000000
Register R24 0x0000000000000000
Register R25 0x0000000000000000
Register R26 0xFFFFFFFF8052E188
Register R27 0xFFFFFFFF82F1C408
Register R28 0xFFFFFFFF8052E124
Frame Pointer 0xFFFFFFFF87831FC0
Current Stack Pointer 0xFFFFFFFF87831CB8
Program Counter 0xFFFFFFFF8052E6A0
Processor Status <63:00>: 0x3800000000000804
Interrupt Pending <02>: 0x1
Current Mode <04:03>: 0x0 Kernel
Interrupt Priority Level (IPL) 0x08
Stack Alignment <61:56>: 0x38
Page Table Base Register (PTBR) 0x00000000000000B8
Privileged Context Block Base (PCBB) 0x0000000001016080
Processor Base Register (PRBR) 0xFFFFFFFF81C16000
Virtual Page Table Base (VPTB) 0xFFFFFEFC00000000
System Control Block Base (SCBB) 0x0000000000000964
Software Interrupt Summary (SISR) <63:00>: 0x0000000000000100
IPL 8 Interrupt Pending
Address Space Number (ASN) 0
AST Enable/AST Summary (ASTEN/ASTSR) <63:00>: 0x0000000000000000
Floating-Point Enable (FEN) <63:00>: 0x0000000000000000
Interrupt Priority Level (IPL) 8
Machine Check Error Summary (MCES) <63:00>: 0x0000000000000000
Bugcheck/Crash Code <31:00>: 0x000007CC
Reboot Type <00>: 0x0 WARM
Severity <02>: 0x1 FATAL
Type <31:03>: 0x000000F9 NETDLLERR
Current Process ID 0x00010000
Current Process Name .NULL
EVENT EVENT_TYPE_____________________________ TIMESTAMP______________ NODE__ EVENT_CLASS____________________________
67 Cold Start 9-JUN-2008 11:13:28.06 A83 CONTROL_ENTRIES
...
|
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
imiller
Administrator
Posts: 277
Location: UK
Joined: 24.02.06 |
| Posted on June 10 2008 04:22 |
|
|
In SYS$ERRORLOG there should be a file caled CLUE$*.lis
(the filename contains the date and time of the crash). This contains a summary of the crash. You could attach it to a post here.
Patches for VMS Alpha V8.3 are found at
ftp://ftp.itrc.hp.com/openvms_patches/alpha/V8.3/
Patches for TCPIP V5.6
ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/DEC-AXPVMS-TCPIP-V0506-9ECO2-1.txt
ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/DEC-AXPVMS-TCPIP-V0506-9ECO2-1.ZIPEXE
|
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 10 2008 05:05 |
|
|
Thank you, I'll get and install the ECOs.
In SYS$ERRORLOG there is only one file called ERRLOG.SYS
(I tried $anal/crash but I have no SDA on my system; if crash dump analysis is an installation option, I didn't choose to install it, because I never used it since I got my first vms system back in 1987; I'll see if it could be added.)
Edited by m2-guy on June 10 2008 05:27 |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 10 2008 07:09 |
|
|
After reconfiguring for SDA support, the reboot generated the clue files. The CLUE file is a bit long; if you think the listing is of no help, I'll edit this post to delete [parts of] it.
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 1
Crashdump Summary Information:
Crash Time: 9-JUN-2008 11:10:33.97
Bugcheck Type: NETDLLERR, DECnet Datalink Layer detected a fatal error
Node: A83 (Standalone)
CPU Type: DEC 3000 - M600
VMS Version: V8.3
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.8052E69C LAN$FATAL_ERROR_CSMACD_C+0074C
Failing PS: 38000000.00000804
Module: SYS$LAN_CSMACD (Link Date/Time: 29-JUN-2006 18:18:49.34)
Offset: 0000E69C
Boot Time: 9-JUN-2008 11:05:23.00
System Uptime: 0 00:05:10.97
Crash/Primary CPU: 0./0.
System/CPU Type: 0402
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 96 MByte (12288 PFNs, contiguous memory)
Dumpfile Pagelets: 120682 blocks
Dump Flags: writecomp,errlogcomp
Dump Type: raw,selective,shared_mem
EXE$GL_FLAGS: poolpging,init,bugdump
Paging Files: 1 Pagefile and 1 Swapfile installed
Stack Pointers:
KSP = FFFFFFFF.87831CB8 ESP = FFFFFFFF.87833000 SSP = FFFFFFFF.8782D000
USP = FFFFFFFF.8782D000
General Registers:
R0 = 00000000.000000F1 R1 = FFFFFFFF.81CDDCC0 R2 = 00000000.00000001
R3 = FFFFFFFF.82F1C408 R4 = FFFFFFFF.82F1C000 R5 = 00000000.00000000
R6 = FFFFFFFF.82F1C410 R7 = 00000000.00000003 R8 = 00000000.00000000
R9 = 00000000.00000000 R10 = 00000000.00000002 R11 = FFFFFFFF.8180B1C8
R12 = 00000000.7BB99A28 R13 = FFFFFFFF.819E6B20 R14 = 00000000.00000001
R15 = 00000000.00000000 R16 = 00000000.000007CC R17 = 00000000.000000D6
R18 = 00000000.00000003 R19 = 00000000.00000001 R20 = FFFFFFFF.81AD70C0
R21 = 00000000.00000018 R22 = 00000000.55435453 R23 = 00000000.00000000
R24 = 00000000.00000000 AI = 00000000.00000000 RA = FFFFFFFF.8052E188
PV = FFFFFFFF.82F1C408 R28 = FFFFFFFF.8052E124 FP = FFFFFFFF.87831FC0
PC = FFFFFFFF.8052E6A0 PS = 38000000.00000804
System Registers:
Page Table Base Register (PTBR) 00000000.000000B8
Processor Base Register (PRBR) FFFFFFFF.81C16000
Privileged Context Block Base (PCBB) 00000000.01016080
System Control Block Base (SCBB) 00000000.00000964
Software Interrupt Summary Register (SISR) 00000000.00000100
Address Space Number (ASN) 00000000.00000000
AST Summary / AST Enable (ASTSR_ASTEN) 00000000.00000000
Floating-Point Enable (FEN) 00000000.00000000
Interrupt Priority Level (IPL) 00000000.00000008
Machine Check Error Summary (MCES) 00000000.00000000
Virtual Page Table Base Register (VPTB) FFFFFEFC.00000000
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 2
Crashdump Summary Information:
Failing Instruction:
LAN$FATAL_ERROR_CSMACD_C+0074C: BUGCHK
Instruction Stream (last 20 instructions):
LAN$FATAL_ERROR_CSMACD_C+006FC: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+00700: BSR R26,#X00009F
LAN$FATAL_ERROR_CSMACD_C+00704: BR R31,#XFFFFD6
LAN$FATAL_ERROR_CSMACD_C+00708: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+0070C: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+00710: LDA R17,#XFFE5(R0)
LAN$FATAL_ERROR_CSMACD_C+00714: BNE R17,#X000006
LAN$FATAL_ERROR_CSMACD_C+00718: LDA R27,#X0030(R13)
LAN$FATAL_ERROR_CSMACD_C+0071C: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+00720: BSR R26,#X0000AB
LAN$FATAL_ERROR_CSMACD_C+00724: BR R31,#XFFFFCE
LAN$FATAL_ERROR_CSMACD_C+00728: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+0072C: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+00730: LDA SP,#XFFF0(SP)
LAN$FATAL_ERROR_CSMACD_C+00734: STQ R16,#X0008(SP)
LAN$FATAL_ERROR_CSMACD_C+00738: STQ R17,(SP)
LAN$FATAL_ERROR_CSMACD_C+0073C: LDQ R17,#XF500(R13)
LAN$FATAL_ERROR_CSMACD_C+00740: BIS R17,#X04,R16
LAN$FATAL_ERROR_CSMACD_C+00744: LDQ R17,(SP)
LAN$FATAL_ERROR_CSMACD_C+00748: LDA SP,#X0008(SP)
LAN$FATAL_ERROR_CSMACD_C+0074C: BUGCHK
LAN$FATAL_ERROR_CSMACD_C+00750: HALT
LAN$FATAL_ERROR_CSMACD_C+00754: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+00758: LDQ_U R31,(SP)
LAN$FATAL_ERROR_CSMACD_C+0075C: LDQ_U R31,(SP)
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 3
Current Registers: Process index: 0000 Process name: NULL PCB: 818E05C8 (CPU 0)
R0 = 00000000.000000F1 %SYSTEM-S-ILLIOFUNC, illegal I/O function code
R1 = FFFFFFFF.81CDDCC0
R2 = 00000000.00000001
R3 = FFFFFFFF.82F1C408
R4 = FFFFFFFF.82F1C000
R5 = 00000000.00000000
R6 = FFFFFFFF.82F1C410
R7 = 00000000.00000003
R8 = 00000000.00000000
R9 = 00000000.00000000
R10 = 00000000.00000002
R11 = FFFFFFFF.8180B1C8 SMP$GQ_DEBUG
R12 = 00000000.7BB99A28
R13 = FFFFFFFF.819E6B20 LAN$FATAL_ERROR_CSMACD+00078
R14 = 00000000.00000001
R15 = 00000000.00000000
R16 = 00000000.000007CC
R17 = 00000000.000000D6
R18 = 00000000.00000003
R19 = 00000000.00000001
R20 = FFFFFFFF.81AD70C0 INET_CCL_VEC_D
R21 = 00000000.00000018
R22 = 00000000.55435453
R23 = 00000000.00000000
R24 = 00000000.00000000
AI = 00000000.00000000
RA = FFFFFFFF.8052E188 LAN$FATAL_ERROR_CSMACD_C+00238
PV = FFFFFFFF.82F1C408
R28 = FFFFFFFF.8052E124 LAN$FATAL_ERROR_CSMACD_C+001D4
FP = FFFFFFFF.87831FC0
PC = FFFFFFFF.8052E6A0 LAN$FATAL_ERROR_CSMACD_C+00750
PS = 38000000.00000804 Kernel Mode, IPL 8, Interrupt
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 4
Stack Decoder:
System Stack (NULL Process):
Stack Pointer FFFFFFFF.87831CB8
Stack Limits (low) FFFFFFFF.8782E000
(high) FFFFFFFF.87832000
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 5
Bugcheck Stack:
Stack Pointer SP => FFFFFFFF.87831CB8
Stack (not decoded):
FFFFFFFF.87831CB8 00000000.00010010 V_EXE$CBB_LOCK
FFFFFFFF.87831CC0 FFFFFFFF.8052E188 LAN$FATAL_ERROR_CSMACD_C+00238
Null Frame:
PV FFFFFFFF.87831CC8 FFFFFFFF.819E6AB8 LAN$FATAL_ERROR_CSMACD+00010
Entry Point FFFFFFFF.8052E020 LAN$FATAL_ERROR_CSMACD_C+000D0
FFFFFFFF.87831CD0 FFFFFFFF.8051BD3C LAN$COMPLETE_DP_C+0027C
FFFFFFFF.87831CD8 FFFFFFFF.8052C2B8 LAN$COMPLETE_VCRP_CSMACD_C+00348
FFFFFFFF.87831CE0 00000000.0000002C
FFFFFFFF.87831CE8 00000000.00000000
FFFFFFFF.87831CF0 00000000.00000001
FFFFFFFF.87831CF8 FFFFFFFF.81DA9040
FFFFFFFF.87831D00 FFFFFFFF.81D42C40
FFFFFFFF.87831D08 FFFFFFFF.82F1C000
FFFFFFFF.87831D10 00000000.00000003
Null Frame:
PV FFFFFFFF.87831D18 FFFFFFFF.819E68B0 LAN$COMPLETE_VCRP_CSMACD+00010
Entry Point FFFFFFFF.8052C060 LAN$COMPLETE_VCRP_CSMACD_C+000F0
FFFFFFFF.87831D20 FFFFFFFF.82F1C3E8
FFFFFFFF.87831D28 FFFFFFFF.8052BFB8 LAN$COMPLETE_VCRP_CSMACD_C+00048
FFFFFFFF.87831D30 00000000.00000001
FFFFFFFF.87831D38 FFFFFFFF.81DA9040
FFFFFFFF.87831D40 FFFFFFFF.82F1C000
FFFFFFFF.87831D48 FFFFFFFF.81D42C40
FFFFFFFF.87831D50 FFFFFFFF.82F1C410
Null Frame:
PV FFFFFFFF.87831D58 FFFFFFFF.819E68A0 LAN$COMPLETE_VCRP_CSMACD
Entry Point FFFFFFFF.8052BF70 LAN$COMPLETE_VCRP_CSMACD_C
FFFFFFFF.87831D60 FFFFFFFF.8052E8C8 LAN$FATAL_ERROR_CSMACD_C+00978
FFFFFFFF.87831D68 00000000.00000001
FFFFFFFF.87831D70 FFFFFFFF.81DA9040
FFFFFFFF.87831D78 FFFFFFFF.82F1C000
FFFFFFFF.87831D80 FFFFFFFF.81D42C40
Null Frame:
PV FFFFFFFF.87831D88 FFFFFFFF.819E6B30 LAN$FATAL_ERROR_CSMACD+00088
Entry Point FFFFFFFF.8052E6D0 LAN$FATAL_ERROR_CSMACD_C+00780
FFFFFFFF.87831D90 FFFFFFFF.8052E5F4 LAN$FATAL_ERROR_CSMACD_C+006A4
FFFFFFFF.87831D98 00000000.00000001
FFFFFFFF.87831DA0 FFFFFFFF.82F1C000
Null Frame:
PV FFFFFFFF.87831DA8 FFFFFFFF.819E6B20 LAN$FATAL_ERROR_CSMACD+00078
Entry Point FFFFFFFF.8052E590 LAN$FATAL_ERROR_CSMACD_C+00640
FFFFFFFF.87831DB0 FFFFFFFF.8052E188 LAN$FATAL_ERROR_CSMACD_C+00238
Null Frame:
PV FFFFFFFF.87831DB8 FFFFFFFF.819E6AB8 LAN$FATAL_ERROR_CSMACD+00010
Entry Point FFFFFFFF.8052E020 LAN$FATAL_ERROR_CSMACD_C+000D0
FFFFFFFF.87831DC0 00000000.00000001
FFFFFFFF.87831DC8 FFFFFFFF.8052C2B8 LAN$COMPLETE_VCRP_CSMACD_C+00348
FFFFFFFF.87831DD0 00000000.00000001
FFFFFFFF.87831DD8 00000000.00000000
FFFFFFFF.87831DE0 00000000.00000001
FFFFFFFF.87831DE8 FFFFFFFF.81DA9040
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 6
Bugcheck Stack:
FFFFFFFF.87831DF0 FFFFFFFF.81D42C40
FFFFFFFF.87831DF8 FFFFFFFF.82F1C000
FFFFFFFF.87831E00 00000000.00000000
Null Frame:
PV FFFFFFFF.87831E08 FFFFFFFF.819E68B0 LAN$COMPLETE_VCRP_CSMACD+00010
Entry Point FFFFFFFF.8052C060 LAN$COMPLETE_VCRP_CSMACD_C+000F0
FFFFFFFF.87831E10 FFFFFFFF.81D40DC0
FFFFFFFF.87831E18 FFFFFFFF.8052BFB8 LAN$COMPLETE_VCRP_CSMACD_C+00048
FFFFFFFF.87831E20 00000000.00000001
FFFFFFFF.87831E28 FFFFFFFF.81DA9040
FFFFFFFF.87831E30 FFFFFFFF.82F1C000
FFFFFFFF.87831E38 FFFFFFFF.81D42C40
FFFFFFFF.87831E40 00000000.00000001
Null Frame:
PV FFFFFFFF.87831E48 FFFFFFFF.819E68A0 LAN$COMPLETE_VCRP_CSMACD
Entry Point FFFFFFFF.8052BF70 LAN$COMPLETE_VCRP_CSMACD_C
FFFFFFFF.87831E50 FFFFFFFF.8052B7E4 LAN$COMPLETE_IO_CSMACD_C+00034
FFFFFFFF.87831E58 00000000.00000001
FFFFFFFF.87831E60 FFFFFFFF.81DA9040
FFFFFFFF.87831E68 FFFFFFFF.82F1C000
FFFFFFFF.87831E70 FFFFFFFF.81D42C40
Null Frame:
PV FFFFFFFF.87831E78 FFFFFFFF.819E6828 LAN$COMPLETE_IO_CSMACD
Entry Point FFFFFFFF.8052B7B0 LAN$COMPLETE_IO_CSMACD_C
FFFFFFFF.87831E80 FFFFFFFF.805145E4 SYS$ESDRIVER+025E4
Null Frame:
PV FFFFFFFF.87831E88 FFFFFFFF.819E45A0 SYS$ESDRIVER+049A0
Entry Point FFFFFFFF.80514550 SYS$ESDRIVER+02550
FFFFFFFF.87831E90 FFFFFFFF.805143EC SYS$ESDRIVER+023EC
FFFFFFFF.87831E98 FFFFFFFF.81C16038 CPUDB+00038
FFFFFFFF.87831EA0 00000000.00000008
Null Frame:
PV FFFFFFFF.87831EA8 FFFFFFFF.819E4558 SYS$ESDRIVER+04958
Entry Point FFFFFFFF.80514270 SYS$ESDRIVER+02270
FFFFFFFF.87831EB0 FFFFFFFF.81C16038 CPUDB+00038
FFFFFFFF.87831EB8 FFFFFFFF.8004BE94 EXE_STD$IOFORK_CPU_C+00424
FFFFFFFF.87831EC0 FFFFFFFF.81C16038 CPUDB+00038
FFFFFFFF.87831EC8 00000000.00000008
FFFFFFFF.87831ED0 FFFFFFFF.81852618 EXE_STD$PRIMITIVE_FORK+00020
FFFFFFFF.87831ED8 00000000.00000000
FFFFFFFF.87831EE0 FFFFFFFF.87831FC0
FFFFFFFF.87831EE8 00000000.00000003
FFFFFFFF.87831EF0 00000000.00010000 SYS$K_VERSION_19
FFFFFFFF.87831EF8 00000000.00000004
FFFFFFFF.87831F00 FFFFFFFF.81C88CC0
FFFFFFFF.87831F08 FFFFFFFF.818E3C68 SCH$CALC_CPU_LOAD+000B8
FFFFFFFF.87831F10 00000000.00000000
FFFFFFFF.87831F18 0000FFF0.00007C04 V_SWP$GL_MAP+00034
FFFFFFFF.87831F20 00000000.00000000
FFFFFFFF.87831F28 00000000.00000001
FFFFFFFF.87831F30 00000000.00000000
FFFFFFFF.87831F38 FFFFFFFF.82C78080
FFFFFFFF.87831F40 FFFFFFFF.8180ACC8 MMG$GL_RES_MEM_FLINK
FFFFFFFF.87831F48 FFFFFFFF.8180D538 SCH$GL_NO_KTB_CPUS
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 7
Bugcheck Stack:
FFFFFFFF.87831F50 FFFFFFFF.81808000 EXE$GR_SYSTEM_DATA_CELLS
FFFFFFFF.87831F58 00000000.00000000
FFFFFFFF.87831F60 FFFFFFFF.8180808C SCH$GL_MFYCNT+00008
FFFFFFFF.87831F68 00000000.00000001
FFFFFFFF.87831F70 FFFFFFFF.81808000 EXE$GR_SYSTEM_DATA_CELLS
FFFFFFFF.87831F78 FFFFFFFF.87831FC0
FFFFFFFF.87831F80 FFFFFFFF.8180A1C0 SCH$GQ_ACTIVE_PRIORITY
Null Frame:
PV FFFFFFFF.87831F88 FFFFFFFF.818E8C60 SCH$WAIT_ANY_MODE
Entry Point FFFFFFFF.80159F10 SCH$WAIT_ANY_MODE_C
FFFFFFFF.87831F90 FFFFFFFF.81C88CC0
FFFFFFFF.87831F98 00000000.00000001
FFFFFFFF.87831FA0 FFFFFFFF.81C16000 CPUDB
FFFFFFFF.87831FA8 00000000.00000000
FFFFFFFF.87831FB0 FFFFFFFF.80128AB8 SCH$CALC_CPU_LOAD_C+003C8
FFFFFFFF.87831FB8 00000000.00000303 CTL$C_KRP_SIZE+00003
Stack Frame:
PV FFFFFFFF.87831FC0 FFFFFFFF.818E3C68 SCH$CALC_CPU_LOAD+000B8
Entry Point FFFFFFFF.80128960 SCH$CALC_CPU_LOAD_C+00270
FFFFFFFF.87831FC8 00000000.00000000
FFFFFFFF.87831FD0 FFFFFFFF.81C88CC0
return PC FFFFFFFF.87831FD8 FFFFFFFF.80159C88 PROCESS_MANAGEMENT+31C88
saved R3 FFFFFFFF.87831FE0 FFFFFFFF.818E8C60 SCH$WAIT_ANY_MODE
saved R13 FFFFFFFF.87831FE8 FFFFFFFF.818E7910 SYS$HIBER
saved R14 FFFFFFFF.87831FF0 00000000.00000001
saved FP FFFFFFFF.87831FF8 00000000.00000000
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 8
System Configuration:
System Information:
System Type DEC 3000 - M600 Primary CPU ID 0.
Cycle Time 5.71 nsec (175 MHz) Pagesize 8192 Byte
Memory Configuration:
Cluster PFN Start PFN Count Range (MByte) Usage
#000 0 256 0.0 MB - 2.0 MB Console
#001 256 12032 2.0 MB - 96.0 MB System
Per-CPU Slot Processor Information:
CPU ID 0. CPU State rc,pa,pp,cv,pv,pmv,pl
CPU Type EV4 Pass 3 (21064)
PAL Code 5.56 Halt PC 00000000.00000000
CPU Revision F001 Halt PS 00000000.00000000
Serial Number .......... Halt Code "Bootstrap or Powerfail"
Console Vers V7.0 Halt Request "Warm Bootstrap Request"
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 9
Adapter Configuration:
TR Adapter ADP Hose Bus BusArrayEntry Node CSR Vec/IRQ Port Slot Device Name / HW-Id
-- ----------- ----------------- ---- ----------------------- ---- ---------------------- ---- ---- ---------------------------
1 KA0402 FFFFFFFF.81C553C0 0 BUSLESS_SYSTEM
2 TC FFFFFFFF.81C55700 0 TURBO
FFFFFFFF.81C55B80 3 00000001.70000000 GYA: 3 ZLX-E (SFB+/HX+)
FFFFFFFF.81C55CE8 6 00000001.D0000000 6 PMAZB-AA SCSI
FFFFFFFF.81C55D60 7 FFFFFFFF.87984000 7 COREIO
3 TURBO_SCSI FFFFFFFF.81C58140 0 SCSI
FFFFFFFF.81C58458 0 FFFFFFFF.87996000 PKA: 0 PMAZB-AA SCSI
FFFFFFFF.81C584D0 1 FFFFFFFF.87996200 PKB: 1 PMAZB-AA SCSI
4 COREIO FFFFFFFF.81C58580 0 COREIO
FFFFFFFF.81C58898 0 FFFFFFFF.879A2000 ESA: 0 LANCE (Ethernet)
FFFFFFFF.81C58910 1 FFFFFFFF.87984000 TTA: 1 Onboard Serial Ports
FFFFFFFF.81C58988 2 FFFFFFFF.87984000 2 Onboard Serial Ports
FFFFFFFF.81C58A00 3 FFFFFFFF.87984000 SOA: 3 ISDN Sound
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 10
Paging File Usage (blocks):
Swapfile (Index 1) Device DKA100:
PFL Address FFFFFFFF.81C61700 UCB Address FFFFFFFF.81C659C0
Free Blocks 11776 Bitmap FFFFFFFF.81C617A8
Total Size (blocks) 11776 Flags inited,swap_file
Total Write Count 0 Total Read Count 0
Smallest Chunk (pages) 736 Largest Chunk (pages) 736
Chunks GEQ 64 Pages 1 Chunks LT 64 Pages 0
Pagefile (Index 254) Device DKA100:
PFL Address FFFFFFFF.81C60F80 UCB Address FFFFFFFF.81C659C0
Free Blocks 204672 Bitmap FFFFFFFF.81C61028
Total Size (blocks) 204672 Flags inited
Total Write Count 0 Total Read Count 0
Smallest Chunk (pages) 12792 Largest Chunk (pages) 12792
Chunks GEQ 64 Pages 1 Chunks LT 64 Pages 0
Summary: 1 Pagefile and 1 Swapfile installed
Total Size of all Swap Files: 11776 blocks
Total Size of all Paging Files: 204672 blocks
Total Committed Paging File Usage: 55280 blocks
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 11
Memory Management Statistics:
Pagefaults: Non-Paged Pool:
Total Page Faults 31251 Successful Expansions 0
Total Page Reads 15799 Unsuccessful Expansions 0
I/O's to read Pages 7105 Failed Pages Accumulator 0
Modified Pages Written 0 Total Alloc Requests 2465
I/O's to write Mod Pages 0 Failed Alloc Requests 0
Demand Zero Faults 9456
Global Valid Faults 6032 Paged Pool:
Modified Faults 7908 Total Failures 0
Read Faults 56 Failed Pages Accumulator 0
Execute Faults 1858 Total Alloc Requests 1993
Failed Alloc Requests 0
Direct I/O 13191 Cur Mapped Gbl Sections 510
Buffered I/O 16890 Max Mapped Gbl Sections 529
Split I/O 191 Cur Mapped Gbl Pages 6190
Hits 7667 Max Mapped Gbl Pages 6618
Logical Name Transl 58070 Maximum Processes 19
Dead Page Table Scans 0 Sched Zero Pages Created 0
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 12
Memory Management Statistics:
Distributed Lock Manager: Local Incoming Outgoing
$ENQ New Lock Requests 14710 0 0
$ENQ Conversion Requests 2893 0 0
$DEQ Dequeue Requests 14455 0 0
Blocking ASTs 5 0 0
Directory Functions 0 0
Deadlock Messages 0 0
$ENQ Requests that Wait 41 Deadlock Searches Performed 0
$ENQ Requests not Queued 0 Deadlocks Found 0
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 13
Memory Management Statistics:
File System Cache: Current SYSGEN Param Hits Misses Hitrate
File Header Cache (ACP_HDRCACHE = 192) 2842 812 77.8%
Storage Bitmap Cache (ACP_MAPCACHE = 48) 0 2 0.0%
Directory Data Cache (ACP_DIRCACHE = 192) 6684 113 98.3%
Directory LRU (ACP_DINDXCACHE= 48) 5327 56 99.0%
FID Cache (ACP_FIDCACHE = 64) 54 2 96.4%
Extent Cache (ACP_EXTCACHE = 64) 67 2 97.1%
Quota Cache (ACP_QUOCACHE = 98) 0 0 0.0%
Volume Synch Locks 144 Window Turns 24
Volume Synch Locks Wait 0 Currently Open Files 341
Dir/File Synch Locks 10453 Total Count of OPENs 1349
Dir/file Synch Locks Wait 5 Total Count of ERASE QIOs 30
Access Locks 0
Free Space Cache Wait 0
Global Pagefile Quota 16699 GBLPAGFIL (SYSGEN) Limit 17184
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 14
Process DCL Recall Buffer:
%CLUE-W-NOACC, either no CLI or process area paged out
OpenVMS Operating System, Version V8.3 -- System Dump Analysis 9-JUN-2008 11:10:33.97 Page 15
Active XQP Processes:
Extended Indx Process name Username PCB XQP Threads Outstanding
--PID--- ---- --------------- ------------ -------- --active--- -BIO---DIO-
%CLUE-I-NOACTIVE, there are no active XQP processes
Edited by m2-guy on June 10 2008 07:11 |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 10 2008 08:41 |
|
|
|
Your Ethernet LAN device driver puked.
thank you!
1. maybe there's a hardware problem with one of the ethernet ports?
I do not have any documentation for the 3000/600; it has 2 ethernet connectors, one AUI where I have a transceiver with twisted pair connector and one RJ45. I believe the bugcheck happened while the CAT5 cable was plugged directly in the RJ45; in any case it happened when I wanted to shutdown the tcp/ip in tcpip$config.com in order to change the IP address of the alpha, because a ping from alpha to the PC resulted in time-out. after the crash I rebooted and changed the IP but ping still didn't get through. this is when I put the CAT5 cable into the plugin-transceiver on the AUI and that was the solution: ping worked and no bugcheck appeared ever since.
who knows, maybe there a functional difference between the two ethernet ports AUI+transceiver and RJ45?
p.s.: I also have a decstation3000/300 and it has only the RJ45 connector which works great with the MR122T repeater.
2. 2D instead of 3D is already more than I ever wanted. (on VAX I'd be happy with VWS* instead of DW-MOTIF, ... but on vax/vms v6.1, VWS which I installed from a v5.4 kit doesn't run; the error I get is "VADRIVER mismatch; reassemble and relink driver" but I don't believe I have the source; is there a VADRIVER for v6.1? or does vax/vms v8.3 still support VWS?)
*) VW = VaxWorkstation # VolksWagen  |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
imiller
Administrator
Posts: 277
Location: UK
Joined: 24.02.06 |
| Posted on June 11 2008 04:46 |
|
|
I think VWS support went away many years ago.
I've not seen one of these workstations (Sandpiper+ ?) for while. They have a mighty 175Mhz first generation alpha chip and don't run but amble slowly. Still, if it works I guess its better than nothing. |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 11 2008 08:48 |
|
|
|
Stephen Hoffman wrote:In aggregate, this behavior implies you need ECOs for IP and for the driver stack, and (for good measure) the current UPDATE kit.
I already downloaded some update kits (vms and tcp/ip), but the error (bugcheck) didn't reappear; so for the time being I don't see any urgence to install the updates.
>> 2. 2D instead of 3D is already more than I ever wanted. (on VAX I'd be happy with VWS* instead of DW-MOTIF
> VWS is usually VAX Workstation Software.
yes.
> VWS is OpenVMS VAX only, and is further limited on which graphics controllers it supports.
yes, and I wrote "on VAX I'd be happy..." - just to express how much I miss VWS on VAX - to make it clear that I'm more than happy with 2D on alpha.
> VWS never made it over to OpenVMS Alpha.
no problem. dw-motif is fast enough as software development environment even on a slow 100MHz decstation3000/300
> VWS is (was) an add-on kit for OpenVMS VAX.
back in 1987, VWS came with my new microvax and was preinstalled. VWS is a very efficient development interface, - actually the only viable development enviroment on microvax ii and iii, for one simple reason, i.e.: with dw-motif it takes too long to open a DECterm. An ascii-terminal emulation is all I need and VWS still works very well and fast on my mvax3, if I boot vms v5.4; and sadly, I didn't get VWS to work in v6,1 on vax, except if I'd find the VADRIVER source.
One can write interesting applications without any graphics. (For graphics, back in 1987, I used a 3rd party AGDC-11 (quad-slot q-bus) graphics adapter on alpha; I never did any VWS programming. Of course, if I needed graphics today, I'd use X; by the way, does X support 64 bit addressing in the meantime on alpha? in v7.1 it did not yet.)
> Comparatively little software uses the old XUI stuff, and even less uses the VWS stuff. Some bits do use X Windows and CDE and mayhap Motif.
that's all correct of course. but wanting to use VWS as a development enviroment doesn't mean that the development depends on (or knows anything about) VWS.
In addition, in contrast to DW-motif, VWS doesn't need a PAK, which is very convenient, given that I got a vms license w/o expiration with my mvax and almost each time I rebooted my vax in the last few years, the dw-motif license had expired and I'm back at console mode to enter a PAK; console is much worse as VWS as everybody might want confirm.
the vax is just a hobby; I can run anything on alpha which I wrote on vax. But I'll keep the vax, - I don't know why - most probably because I like it, since there are so many souvenirs attached. In contrast, I'll most probably not rebuild a LSI-11/73 Q-bus system although I kept a cpu and memory board. Nevertheless, I'll try SIMH pdp-11 simulator one day, given that the programming system I used didn't suffer from the 16 bit address space limitation, see article "On LSI-11, RT-11, Megabytes of Memory and Modula-2/VRS" http://www.modulaware.com/history/Vrsmot.pdf
p.s.: The other article by Gordon Bell published in 1975 which I found in http://en.wikipedia.org/wiki/PDP-11 is well worth reading:
http://research.microsoft.com/users/GBell/Digital/Bell_Strecker_What_we%20_learned_fm_PDP-11c%207511.pdf |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 11 2008 09:01 |
|
|
>I've not seen one of these workstations (Sandpiper+ ?) for while. They have a mighty 175Mhz first generation alpha chip and don't run but amble slowly. Still, if it works I guess its better than nothing.
The speed of the Sandpiper is more than I ever needed, but one day I'll try to get less power hungry alpha.
> comparatively poor performance and particularly on Mozilla or web
yes, Mozilla is slow, but I use Mozilla only very occassionally, to view a html file offline.
> or other "modern" applications (and anything else that benefits from the Alpha byte-word instruction subset),
no problem, I'm 100% certain, that all the applications wrote don't use these byte-word instructions [and also don't necessarily suffer from unalignment traps].
> some of the older EV6 boxes (AlphaStation XP1000, etc) can be cheap or even at the give-away price level these days.
yes, but give-away can be expensive in shipping cost.
> The DEC 3000 series is usually a "bird".
maybe it is my age? - because it took me a while to understand what you meant , most probably because with Piper I associated a Flugzeug not a bird, although both fly as long as they don't drop |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
operagost
Member
Posts: 4
Joined: 14.01.08 |
| Posted on June 17 2008 03:50 |
|
|
|
m2-guy wrote:
I believe the bugcheck happened while the CAT5 cable was plugged directly in the RJ45; in any case it happened when I wanted to shutdown the tcp/ip in tcpip$config.com in order to change the IP address of the alpha, because a ping from alpha to the PC resulted in time-out. after the crash I rebooted and changed the IP but ping still didn't get through. this is when I put the CAT5 cable into the plugin-transceiver on the AUI and that was the solution: ping worked and no bugcheck appeared ever since.
who knows, maybe there a functional difference between the two ethernet ports AUI+transceiver and RJ45?
I used to have one of those. You need to set the media type at the SRM console. Type "show ew" and look for something like "ewa0_mode". You want to "SET EWxx_mode Twisted-Pair". I suppose it's possible there is a hardware switch in between the connectors which you need to push towards the interface you wish to use, but I'll bet I'm thinking of my VAXStation. |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 17 2008 10:38 |
|
|
Thank you. I just checked config with SRM.
there's
>>> SHOW ETHERNET
and it's set to THICK. (I've noticed THICK previously in show config but didn't know it's either AUI or twisted pair, but not both.)
I checked with SRM's HELP SET; so to use the twisted pair, I'd need
>>> SET ETH TENBT
You made me curious about the switches on the back:
below the AUI is the reset button. but a bit farther, near the status LEDs, there is a switch called "S3". maybe someone knows what's its purpose? |
|
|
| Author |
RE: bugcheck - where did $analyze/error/since go? |
m2-guy
Member
Posts: 38
Location: Provence
Joined: 19.12.07 |
| Posted on June 18 2008 03:19 |
|
|
> many of the older manuals are on-line at the vt100.net/manx server.
thank you; 'tis a great site.
found the manuals - and those for my VAXstation 3200 too. |
|
|
