home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 17 Fixes30
/
17-Fixes30.zip
/
warpdump.zip
/
trapdump.fax
next >
Wrap
Text File
|
1995-01-30
|
9KB
|
262 lines
File:TRAPDUMP.fax 11/30/94
TITLE: THE OS/2 DUMP PROCESS
SUMMARY OF RESOLUTION:
A utility exists in OS/2 (including Warp) to dump all of the physical
memory to diskette. The dump is helpful in some situations to identify
a failing component in an OS/2 system.
** THE DUMP PROCESS **
1. THE NEW DUMP PROCEDURE
A) OS/2 2.0, 2.1 and 2.11 do not contain the latest dump files.
You must install the new dump procedure (NEWDUMP.ZIP) on the
system before taking a system dump. NEWDUMP.ZIP can be
obtained from our bulletin board at (407) 443-8000.
- Logon with your own name and password.
- At the main menu press F for files.
- S to Select a library.
- 8 (enter)
- D to download a file.
- Newdump.zip (enter)
There is a readme with this file which explains how to apply
newdump to the system.
B) Warp updates are in warpdump.zip. This update applies only to Warp.
C) OS/2 2.0 requires XR06100 (service pak II) as a prerequisite for
newdump.
** To perform a system dump you will need blank formatted diskettes.
The number of diskettes needed depends on the amount of memory
in your system. For every two mb of memory you will need approximately
one 1.44 diskette (the swapper file is not relevant to the dump).
2. STARTING THE TRACE
NOTE: DO NOT INVOKE TRACE UNLESS INSTRUCTED TO BY AN IBM TECHNICAL
ANALYST.
For OS/2 prior to OS/2 2.1, add the following lines in
config.sys:
TRACE=ON
TRACEBUF=63
TRACE=OFF 4,24,47,50,97,98
and then reboot the machine.
The above starts TRACE function and turns off major codes 4, 24,
47,50, 97, and 98. The default for TRACE=ON is to trace all system
events. These major codes are for some housekeeping functions
hat are not normally used by development.
For OS/2 2.1, add the following lines to the config.sys (exactly):
TRACEBUF=63
TRACE=ON
then reboot the machine.
For OS/2 2.1, enter the following commands from a command prompt
after the reboot noted just above:
TRACE ON KERNEL
TRACE ON DOSCALL1
3. There are several types of memory dumps:
Different situations determine which type of dump is needed. IBM
OS/2 Support will help to determine which process is correct for
your situation.
A. OS/2 2.0, 2.1, OR 2.11 (with no fixpacks)
1. AUTOMATIC DUMP PROCESS (Only to be used for Ring 3 Traps)
In CONFIG.SYS enter the following:
TRAPDUMP=ON
This will cause an automatic DUMP if the failing CS:EIP is
in Ring 3 code (the CS value will end in either 3, 7, B or F).
It will not DUMP on Ring 0 code traps. (Applications run
at Ring 3 while the OS/2 Kernel runs at Ring 0.)
**OR***
2. MANUAL DUMP PROCESS
It is also possible to start a MANUAL DUMP of the system.
Press and hold "Ctrl+Alt" and then press "Num Lock" twice.
This will start the dump process in most cases, even if the
keyboard is locked.
B. OS/2 2.11 WITH FIXPACK (36 or later) OR WARP
1. AUTOMATIC DUMP PROCESS FOR RING 0 TRAPS (dumps BOTH
ring 0 and non-ring 0 traps)
In the CONFIG.SYS enter the following:
TRAPDUMP=ON
This will cause an automatic DUMP.
**OR**
2. AUTOMATIC DUMP PROCESS FOR RING 0 TRAPS (dumps ONLY
ring 0 traps)
In the CONFIG.SYS enter the following:
TRAPDUMP=R0
This will cause an automatic Dump if the Failing CS:EIP is in
Ring 0 code (the EIP will end in 0, 4, or 8). It will not DUMP
Ring 3 traps. (The OS/2 kernel and device drivers run at
Ring 0 while applications run at Ring 3).
This will cause an automatic DUMP.
**OR**
3. MANUAL DUMP PROCESS
It is also possible to start a MANUAL DUMP of the system.
Press and hold "Ctrl+Alt" and then press "Num Lock" twice.
This will start the dump process in most cases, even if the
keyboard is locked.
4. TAKING THE DUMP
When the dump is started, either automatic or manual, the
screen goes blank and the user is instructed to insert a blank
formatted diskette. The user will be prompted for additional
diskettes as needed and then instructed to insert the DUMP
diskette a second time. When this is finished, the system
can be re-booted to return to normal operation.
Note that no register information is displayed when an
automatic dump is taken. The register information is
contained in the dump information.
5. How to read the Trap information from the dump diskettes.
To view the dump diskettes for the revision of the kernel and
the trap infromation:
- Place the first dump diskette into the floppy drive and from
the a: prompt type: e dumpdata.001 (enter).
- You will receive a message that the editor detected embedded
null characters as it read the file.
Press: continue loading file
- A screen of unreadable characters will appear.
- Press edit, find, find: revision
This will find the level of the kernel you are running.
(eg, 6.617 for OS/2 2.11, 8.162 for Warp, etc.)
- You can also search on the cs:eip to see if the trap screen is
present.
Place the mouse pointer at the begining of the file.
Press edit, find find: CS:EIP
If a trap is present it will display the registers. (Sometimes
more than one trap is found in the dump. If the registers are
all x's, press find again to see if there are additional traps.)
**WARNING**
DO NOT edit the file by adding characters or spaces. This can
cause the dump to be unreadable. Once you have completed
viewing the dump, always exit without saving the file because
it may cause the dump to be unreadable. If you have made
any changes to the file by accident, also exit without saving
the file.
DETAILS OF RESOLUTION:
6. MAILING THE DUMP TO IBM
DO NOT send dump diskettes unless instructed by Level 2 Support.
Diskettes MUST be clearly labeled with the PMR# or APAR# and your
name. Please ensure diskettes are numbered as well.
DUMP diskettes should be sent to:
IBM Corp.
1000 NW 51st Street
Boca Raton, FL 33432
ATTN: (Name of the OS/2 Analyst requesting the dump), Bldg 001-3
Internal Zip 1024
** For IBM Internal Customers ONLY**
Disk images may be created using OS2IMAGE.EXE (OS2TOOLS), no other
utility, e.g.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 just the contents of each
diskette). We do not have the capability to download dumps from
IBMLINK, the PCC BBS, COMPUSERVE, etc, although we may be able
to arrange for you to upload to our SDM.
** HOW TO DUMP TO HARDFILE**
NOTE! NOTE! NOTE!
Dump to hardfile must be to a separate, empty partition.
IT WILL ERASE WHATEVER IS ON THE PARTITION.
You MUST install newdump on the system if you are running OS/2 2.0,
2.1, or 2.11.
1. Create a partition about 4meg larger than the amount of memory
installed.
2. Format the partition FAT.
3. Label the partition SADUMP.
4. Modify config.sys as follows:
trapdump=off,X: where X: is the partition letter
5. REBOOT
- To initiate the dump to hardfile, hit ctl-alt-numlock-numlock
16megs should dump in under a minute!!!
A good test would be to run chkdsk on a large enough drive (do
not run chkdsk /f, just chkdsk). Then while chkdsk is still running,
initiate the dump.
- Some modifications have been made to the dump to hardfile on
8/1/94:
1. A message will now display, informing the user of which partition
will be dumped to, and how much memory.
2. A warning message will display informing the user that the dump
will wipe out the dump partition. The user has 30 seconds in which
to respond. If the user does not answer in 30 seconds, the dump
begins.
3. If the user chooses not to dump to the hardfile by answering N to
the above prompt, he is asked if he would like to dump to diskette.
4. If an error is encountered, and the dump cannot proceed to the
hardfile, the user is asked if he would like to dump to diskettes.
If the answer is no, or there is no response in 60 seconds, the
system is rebooted.
- Major modifications were made to both the dump to hardfile and to
diskette on 11/01/94.
1. Improved error checking on dump to hardfile and diskette.
2. More descriptive error messages.
3. NOTE: if there is a bad sector encountered when dumping to
hardfile, a Fatal Dump Error message will display followed by
the bad sector information to help pinpoint the error.
There is currently no error recovery in dump to hardfile.
4. Support for systems with 64meg or more of memory installed.
DO NOT USE a dump dated prior to 11/01/94 on systems with
64 meg or more.
5. Better performance.
6. Improved error recovery from bad diskettes.