HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: CRASH ANALYSIS of VAX/VMS server
Operating System - OpenVMS
1828258
Members
2759
Online
109975
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2006 10:31 PM
02-03-2006 10:31 PM
Re: CRASH ANALYSIS of VAX/VMS server
This a not a real valid OpenVMS HALT restart bugcheck, the APPLICATION itself is issueing BUGW BUG$_HALT bugchecks internally !!! This explains, why the registers and the HALT code (e.g. in the RPB) do NOT provide valid values.
Here is an example instruction stream from the application:
00195D27: BRW 00195DEF
00195D2A: PUSHL #10000002
00195D30: CALLS #01,@0019C250
00195D37: BLBS R0,00195D4D <<< return address
00195D3A: PUSHL R2
00195D3C: MOVL #0EC0DE07,R2
00195D43: BUGW #0160 <<< issue HALT bugcheck !!!
The saved PC on the kernel stack should point to the application code declaring the HALT bugcheck, so please provide the following data:
SDA> EXA/INS 195FEB-10;10
The non-fatal bugcheck entries can be reproduced easily with the following piece of MACRO code:
.entry halt, ^m<>
$cmkrnl_s routin=halt_cpu
MOVZWL #1, R0
ret
.entry halt_cpu, ^m<>
bug$_halt=^x160
BUGW
.WORD ; issue a HALT bugcheck
ret
.end halt
Fix the problems in your application and those crashes will go away. If you need further assistance, please consider to contact me offline (see e-mail address in my ITRC profile).
Volker.
Here is an example instruction stream from the application:
00195D27: BRW 00195DEF
00195D2A: PUSHL #10000002
00195D30: CALLS #01,@0019C250
00195D37: BLBS R0,00195D4D <<< return address
00195D3A: PUSHL R2
00195D3C: MOVL #0EC0DE07,R2
00195D43: BUGW #0160 <<< issue HALT bugcheck !!!
The saved PC on the kernel stack should point to the application code declaring the HALT bugcheck, so please provide the following data:
SDA> EXA/INS 195FEB-10;10
The non-fatal bugcheck entries can be reproduced easily with the following piece of MACRO code:
.entry halt, ^m<>
$cmkrnl_s routin=halt_cpu
MOVZWL #1, R0
ret
.entry halt_cpu, ^m<>
bug$_halt=^x160
BUGW
.WORD
ret
.end halt
Fix the problems in your application and those crashes will go away. If you need further assistance, please consider to contact me offline (see e-mail address in my ITRC profile).
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2006 11:48 PM
02-05-2006 11:48 PM
Re: CRASH ANALYSIS of VAX/VMS server
Volker, Sorry for the late response. Pls find the attached SDA output as asked by u.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2006 11:55 PM
02-05-2006 11:55 PM
Re: CRASH ANALYSIS of VAX/VMS server
Now what code is at 000BE3F4
SDA> EXA/INS 000BE3F4;20
I'm even more interested in:
SDA> EXA/INS 195FEB-10;20
This PC is found on the kernel stack in the crash and should reflect the last instruction executed before the crash !
Volker.
SDA> EXA/INS 000BE3F4;20
I'm even more interested in:
SDA> EXA/INS 195FEB-10;20
This PC is found on the kernel stack in the crash and should reflect the last instruction executed before the crash !
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 02:31 AM
02-06-2006 02:31 AM
Re: CRASH ANALYSIS of VAX/VMS server
continued and fully explained in:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=998774
Volker.
PS: Please consider to close this thread (9972828).
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=998774
Volker.
PS: Please consider to close this thread (9972828).
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP