home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
oshtdump.txt
< prev
next >
Wrap
Text File
|
1997-05-30
|
13KB
|
364 lines
OSHTDUMP - OS/2 MEMORY-DUMP PROCESS
12/06/96
=======================================================================
OS/2 Memory-Dump Process
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
A memory dump is performed when a problem is difficult to
reproduce or other methods of problem determination do not
identify the problem.
RESOLUTION
Note: Make sure you have a backup of any file you intend to change, such
the OS/2 CONFIG.SYS file.
The New OS/2 System Dump Procedure
----------------------------------
Note: Only if you are having Workplace Shell problems, such as the
Desktop collapsing and then re-opening, or if advised by your
Technical Support Representative, place the following statement
in your CONFIG.SYS file:
SET SHELLEXCEPTIONHANDLER=OFF
There are new files required for a memory dump, and OS/2 Warp has
the latest ones. This section does NOT apply to OS/2 Warp.
OS/2 2.1 and OS/2 2.11 do not have the latest dump
files. You must install the new dump procedure, NEWDUMP.ZIP, on
the system before a doing memory dump. You can download
NEWDUMP.ZIP from the bulletin board at 512-823-0345 by doing
the following:
1. Log on with your name and password.
2. At the Main Menu, press F for files.
3. Select S to select a library.
4. Type 8 and press Enter.
5. Type D to download a file.
6. Type NEWDUMP.ZIP and press Enter.
The README file explains how to apply NEWDUMP to the system.
Note: Before following this procedure, OS/2 2.1 systems should
be upgraded to OS/2 2.11, and then FixPak 80 or
later should be installed. For best results, upgrade
OS/2 2.11 systems to FixPak 80 or later.
You need blank formatted diskettes for a memory dump. Generally,
one 1.44 MB diskette is used for each 2 MB of RAM. For example,
if you have a 16 MB system, you need 8 formatted diskettes.
----------------------------------------------------------------
Different situations determine the type of memory dump
required. IBM OS/2 Support can help to determine the correct
process for your situation. For example, the OS/2 kernel and
device drivers run at Ring 0 while applications run at Ring 3.
OS/2 2.1 or OS/2 2.11 without FixPaks
-------------------------------------
Automatic Dump Process for Ring 3 Traps
---------------------------------------
Edit the CONFIG.SYS file and add the following line:
TRAPDUMP=ON
This causes an automatic dump if the failing CS:EIP is in
Ring 3 code (the CS value ends in either 3, 7, B, or F). It
does not dump on Ring 0 code traps. Applications run at Ring
3, while the OS/2 kernel runs at Ring 0.
Manual Dump Process for Ring 3 Traps
------------------------------------
To start a manual dump of the system, press and hold Ctrl+Alt;
then press Num Lock twice. This starts the dump process in most
cases, even if the keyboard is locked.
OS/2 2.11 with FixPak 80 or Later, or OS/2 Warp
-----------------------------------------------
Automatic Dump Process for Ring 0 and Non-Ring-0 Traps
------------------------------------------------------
Edit the CONFIG.SYS file and add the following line:
TRAPDUMP=ON
Automatic Dump Process for Ring 0 Traps
---------------------------------------
Edit the CONFIG.SYS file and add the following line:
TRAPDUMP=R0
This begins an automatic dump if the failing CS:EIP is
in Ring 0 code (the CS ends in 0, 4, or 8). It does not
dump Ring 3 traps.
Note: It is not required to set up for automatic Ring 0
trap dumps in order for the dump to be valid. It is only
recommended.
Manual Dump Process
-------------------
A manual dump is used when the system is in a non-
responsive state (does not respond to your requests) and cannot
be used. Make a note of whether the Caps Lock key, when pressed,
toggles its light and inform your service representative whether it
responded to your keypress or not. Proceed to the next step.
To start a manual dump of the system, press and hold Ctrl+Alt;
then press Num Lock twice. This starts the dump process in most
cases, even if the keyboard is locked. Alternatively, if you do
not have a Num Lock key, press and hold Ctrl+Alt; then press F10
twice.
Starting the Memory Dump
------------------------
When the memory dump begins, the screen goes blank, and then you
are prompted to insert a blank formatted diskette. You also are
prompted to insert additional diskettes, and then are asked to
insert the DUMP diskette again. When the process is complete,
restart the system.
Register information is not displayed when an automatic memory
dump is taken. The register information is in the dump
information.
Reading the Trap Information from the Dump Diskettes
----------------------------------------------------
To view the dump diskettes for the revision of the kernel and
the trap information:
1. Insert the first dump diskette in drive A.
2. Type A: (followed by the ENTER key)
E DUMPDATA.001 and press Enter.
A message appears stating the editor detected embedded
null characters as it read the file.
3. Select Continue Loading File. A screen of unreadable
characters appears.
4. Select Edit, Find, and Find: revision.
This finds the level of the OS/2 kernel you are running.
For example, 6.617 is for OS/2 2.11, 8.162 is for OS/2 Warp 3, and
8.209 is for OS/2 Warp Connect (blue spine box).
You also can search on CS:EIP to see if the trap screen
is present:
a. Place the mouse pointer at the beginning of the file.
b. Select Edit, Find, and Find: CS:EIP.
If a trap is present, it displays the registers. (Sometimes
more than one trap is found in the dump. If the registers
are all x's, select Find again to see if there are more
traps.)
WARNING!
DO NOT edit the file by adding characters or spaces. This can
cause the memory dump to be unreadable. After viewing the dump,
always exit without saving the file, because it might cause the
dump to be unreadable. If you have accidentally made any changes
to the file, exit without saving the file.
Mailing the Memory Dump to IBM
------------------------------
DO NOT send dump diskettes unless instructed to do so by
your Support Representative. Diskettes must be clearly labeled with the
PMR (problem management record) number or APAR (authorized program
analysis report) number and your name. Be sure the diskettes
are numbered. Send dump diskettes to:
IBM Corp.
11400 Burnet Road
Austin, TX 78758
ATTN: Name of the OS/2 Analyst requesting the dump
Bldg. 42
Internal Zip 2901
For IBM Internal Customers Only
-------------------------------
You may create disk images using OS2IMAGE.EXE (from OS2TOOLS).
No other utility program (for example, LOADDSKF) is acceptable.
Please send the disk images to the VM ID given to you by the
OS/2 Analyst. The dump formatter requires disk images, as
opposed to the contents of each diskette. OS/2 Support cannot
download dumps from IBMLINK, the PCC BBS, CompuServe, or other.
OS/2 Support might be able to arrange an upload to our Service
Delivery Machine.
Dumping to Hard Disk
--------------------
Notes: 1. A memory dump to hard disk must be to a separate, empty
partition. The memory dump erases whatever is on
the partition.
2. This information is available in the online help
documentation with OS/2 Warp versions 3 and later;
type HELP TRAPDUMP at an OS/2 command prompt.
You MUST install NEWDUMP on the system if you are running OS/2
2.1 or OS/2 2.11.
1. Create a partition that is approximately 4 MB larger than
the amount of random access memory (RAM) installed.
2. Format the partition as FAT.
3. Label the partition SADUMP using the OS/2 LABEL command.
Type HELP LABEL if you need more information on using
the LABEL command at an OS/2 command prompt.
4. Edit the CONFIG.SYS file and change the TRAPDUMP statement
as follows, where x: is the partition letter:
* For a Manual Dump to hard disk, use:
TRAPDUMP=OFF,x:
* For an Automatic Dump to hard disk, use:
TRAPDUMP=ON,x:
5. Restart the system.
6. To initiate the Manual Dump to hard disk:
Press and hold Ctrl+Alt and press the Num Lock key twice
to start the memory dump to hard disk. It should take less
than a minute to dump 16 MB. If you do not have a Num Lock
key, press and hold Ctrl+Alt and then press F10 twice.
7. Remember that Automatic Dumps will happen automatically when
there is a software (and sometimes even a hardware) failure.
If you wish to dump Ring 0 TRAPs only, modify the
TRAPDUMP=ON,x: statement above to read:
TRAPDUMP=R0,x:
8/1/94 Changes to the Memory-Dump-to-Hard-Disk Process
------------------------------------------------------
1. A message tells which partition will be dumped to, and
how much memory is required.
2. A message warns that the dump will erase the contents of the
dump partition. You have 30 seconds to respond. If you do not
respond within the 30 seconds, the memory dump begins.
3. If you choose not to dump to the hard disk by answering N
to the above prompt, you are asked if you want to dump to
diskette.
4. If an error occurs, and the dump cannot be made to the hard
disk, you are asked if you want to dump to diskettes. If
you answer no, or do not respond within 60 seconds, the
system restarts.
11/01/94 Changes to the Memory-Dump-to-Hard-Disk Process
--------------------------------------------------------
1. Improved error checking on dumps to hard disk and diskette.
2. More descriptive error messages.
3. If a bad sector is encountered when dumping to hard disk,
a Fatal Dump Error message appears followed by the bad
sector information to help pinpoint the error. There is
currently no error recovery when dumping to hard disk.
4. Support for systems with 64 MB or more of memory installed.
DO NOT USE a memory dump dated before 11/01/94 on systems
with 64 MB or more.
5. Better performance.
6. Improved error recovery from bad diskettes.
======================================================================
TRACE SECTION - USE THIS SECTION ONLY IF ASKED TO BY YOUR
IBM SERVICE REPRESENTATIVE
Starting the Trace
------------------
Note: Do NOT begin TRACE unless an IBM Technical Analyst tells
you to do so.
For OS/2 2.1 and OS/2 2.11:
---------------------------
1. At an OS/2 command prompt, type E CONFIG.SYS and press
Enter to edit the CONFIG.SYS file.
2. Add the following lines (exactly):
TRACEBUF=63
TRACE=ON
3. Save and exit the file; then restart the system.
4. At the command prompt, type the following and press Enter
after each:
TRACE ON KERNEL
TRACE ON DOSCALL1
5. Follow the instructions provided by your service
representative at this point.
For OS/2 Warp 3 and OS/2 Warp 4:
--------------------------------
1. At an OS/2 command prompt, type TEDIT CONFIG.SYS and press
Enter to edit the CONFIG.SYS file. Remember to press the
Esc key to move the cursor into the text area to
begin editing. Press the Insert key to allow you to insert
new lines into the CONFIG.SYS file.
2. Add the following lines (exactly) at the top of the
CONFIG.SYS file:
TRACEBUF=63
TRACE=OFF
3. Save the CONFIG.SYS file by pressing F2, and then press F3
to exit the editor. Shutdown and restart the system.
4. At this point, follow the instructions provided by your service
representative to initiate a system trace.
warp4
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.