- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Bugcheck Error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО09-01-2006 06:01 AM
тАО09-01-2006 06:01 AM
Bugcheck Error
INVEXCEPTN, Exception while above ASTDEL
How ever the PC code portion of the error differs. The first one is:
SDA>examine/inst FFFFFFFF800A3708
EXE$REFLECT_C+00638: SLL R7,#X3B,R2
The other is:
SDA> examine/inst FFFFFFFF803359C0
CNX$SEND_MSG_CSB_V2_C+00250: LDQ RD6,#XFFD0(R13)
Can some one explaine to me the meaning of these? Both site are currently running OpenVMS version 7.3.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 10:40 AM
тАО09-01-2006 10:40 AM
Re: Bugcheck Error
How upto date are you with ECO patches for you v.7.3 release ?
Upto to date list available here -> ftp://ftp.itrc.hp.com/openvms_patches/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-01-2006 06:02 PM
тАО09-01-2006 06:02 PM
Re: Bugcheck Error
if possible, please provide the full crash information (the CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS from the date of the crash) - but at least the output of the SDA> CLUE CRASH command - as an attached .TXT file.
In case of an invalid exception, you need to look at the PC of the failing instruction in the Signal Array. Together with the condition code in the Signal Array and the instruction, a first analysis may be possible.
The instruction in your first example shown can NOT generate an exception. So it was either a TRAP and you're looking at the updated PC after the failure or you looked at the wrong PC.
In your second example, R13 must have pointed to an invalid/inaccessible address for this instruction to have caused an exception.
Talking about patches should be delayed, until you better understand the circumstances of the crash.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-03-2006 06:45 AM
тАО09-03-2006 06:45 AM
Re: Bugcheck Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 03:37 AM
тАО09-05-2006 03:37 AM
Re: Bugcheck Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 03:53 AM
тАО09-05-2006 03:53 AM
Re: Bugcheck Error
sorry, but the bugcheck errlog entry does not help at all.
Pleass look at your system disk in the directory pointed to by the logical CLUE$COLLECT. You will find one 'CLUE' file for each valid bugcheck:
CLUE$node_ddmmyy_hhmm.LIS
Date and time are the bugcheck date and time.
If you use the command $ TYPE CLUE$HISTORY, you will get a one-line summary information for each bugcheck seen on your system (use $ SET TERM/WID=132, as the information is 132 columns wide).
Please attach the 'CLUE' files from the relevant crashes.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 04:03 AM
тАО09-05-2006 04:03 AM
Re: Bugcheck Error
Do you know if there are any issues with upgrading the memory in the DS10's? This is what happened at the site just prior to this Bug Check.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 04:11 AM
тАО09-05-2006 04:11 AM
Re: Bugcheck Error
where did you get the SDA information from, which you showed us in your initial posting ? Do you still have access to the crashdump ? If so, you could post the output of the SDA> CLUE CRASH command.
Maybe you're using DOSD and have not correctly set up your CLUE$DOSD_DEVICE logical during startup.
Hardware (memory) problems should show up as MACHINECHK or MCHECKPAL bugchecks.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 04:15 AM
тАО09-05-2006 04:15 AM
Re: Bugcheck Error
OpenVMS (TM) Alpha system dump analyzer
...analyzing a compressed selective memory dump...
%SDA-E-NOTSAVED, S0/S1 space not saved in the dump file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2006 04:18 AM
тАО09-05-2006 04:18 AM
Re: Bugcheck Error
the bugcheck-PC examined in your initial posting
EXE$REFLECT_C+00638: SLL R7,#X3B,R2
is in the central INVEXCEPTN bugcheck reporting routine. For an INVEXCEPTN bugcheck, you can not use the SDA> EXA/INS @PC command to obtain the failing instruction. You need to provide and examine the bugcheck-PC from the signal array. The SDA> CLUE CRASH command always does the right thing for you - depending on the crash context.
Volker.