Hi dear alphists ,
I received many replies to my question (see after my signater).
Thanks to :
Whitney Latta <latta_at_decatl.alf.dec.com
Arrigo Triulzi <arrigo_at_albourne.com>
Oisin McGuinness <oisin_at_sbcm.com>
Stanley Horwitz <stan_at_astro.ocis.temple.edu>
John Becker <John.Becker_at_digital.com>
juredd - Justin Reddell <juredd_at_acxiom.com>
"Vayro, Drew" <Drew.Vayro_at_nl.origin-it.com>
balaji chandrasekar <balajic_at_erols.com>
Here follow the summary of the received answers:
1) Unless you are very familiar with crash analysis and use of the debuggers, and have a pretty fair
knowledge of system internals, and have access to source code, it is not likely you will get much
from looking at the crash information. But to start, you can look in the crash-data.0 file. It is
created when crashdc(8) runs at boot, and contains a cursory analysis of the crash. The most
important information in it will be the stack trace of the thread that was running on the panicing
cpu. The stack trace will reveal what code was running that detected the problem. At least it will
give you some idea where to look. To view it, use an editor and search for the stack trace of the
"paniccpu" thread. Usually you can get to it by searching for the string "tset", which preceeds
the stack trace output. You will see several lines in the stack, each line starting with the
activation level number followed by the function called, and some arguments and the code file and
line number, etc.
2) Whenever a Patch Kit comes out, the kernel crash stacks are reproduced in the Readme files,
so you can try to match what you find in crash-data.0 against the contents of the readme's to find
which patch if any might solve your problem, if your problem is not hardware.
You may also want to show crash-data.0 to the CRC or Dec field engineers...
3) Once you know the process that
caused the panic you can search the archive pages for more details or
get the core file sent to DEC/COMPAQ and have them analyse it. They will
only do it if you have a software maintenance.
4) Somebody runs a "sys_check -escalate" and than take the output files
that this generates, tar them together and ftp them to Compaq's support
center so they can analyse them.
Thank you very much to everybody,
LONG LIFE TO OUR LIST !!
Emanuele
Emanuele Lombardi
mail: AMB-GEM-CLIM ENEA Casaccia
I-00060 S.M. di Galeria (RM) ITALY
mailto:lele_at_mantegna.casaccia.enea.it
tel +39 06 30483366 fax +39 06 30483591
This transmission was made possible by 100% recycled electrons.
Hi alpha gurus!
I need your help because my AS 4100 5/466 (3CPU, 1Gb RAM, dunix 4.0d 3rd
patch) has suddently chrashed (and automatically restarted) with only a
criptic message left in /var/adm/message:
Mar 18 16:07:37 botticelli vmunix:
Mar 18 16:07:37 botticelli vmunix: trap: invalid memory read access from kernel mode
Mar 18 16:07:37 botticelli vmunix:
Mar 18 16:07:37 botticelli vmunix: faulting virtual address: 0x0000000000000010
Mar 18 16:07:37 botticelli vmunix: pc of faulting instruction: 0xfffffc00004fc9f0
Mar 18 16:07:37 botticelli vmunix: ra contents at time of fault: 0xfffffc00004fc9d8
Mar 18 16:07:37 botticelli vmunix: sp contents at time of fault: 0xffffffffa6d33978
Mar 18 16:07:37 botticelli vmunix:
Mar 18 16:07:37 botticelli vmunix: panic (cpu 2): kernel memory fault
Mar 18 16:07:37 botticelli vmunix: device string for dump = RAID 1 4 0 0 0 0 0.
Mar 18 16:07:37 botticelli vmunix: DUMP.prom: dev RAID 1 4 0 0 0 0 0, block 524288
Mar 18 16:07:37 botticelli vmunix: device string for dump = RAID 1 4 0 0 0 0 0.
Mar 18 16:07:37 botticelli vmunix: DUMP.prom: dev RAID 1 4 0 0 0 0 0, block 524288
Mar 18 16:07:37 botticelli vmunix: Alpha boot: available memory from 0x18b6000 to 0x3fffa000
Mar 18 16:07:37 botticelli vmunix: Digital UNIX V4.0D (Rev. 878); Thu Mar 4 18:46:29 MET 1999
.....
.....
in /var/adm/crash I found the following files:
1 -rw-r--r-- 1 root system 2 Mar 18 16:07 bounds
30 -rw-r--r-- 1 root system 30412 Mar 18 16:08 crash-data.0
9440 -rw-r----- 1 root system 9661808 Mar 18 16:07 vmunix.0
14584 -rw-r----- 1 root system 14927360 Mar 18 16:07 vmzcore.0
but I don't know what to do with them. I have dia but I don't know how
to use it either.
I will be glad of any suggestion.
Greetings to all from Italy,
Emanuele
Received on Wed Mar 24 1999 - 08:25:54 NZST