This morning my alpha 255 (DU 3.2) had a sudden crash, I was unable to read
the messages (perhaps there was something about machine check, but they run
over the screen to fast), it sync'ed the disks and attempted a crash dump.
I tried a reboot (single user) a couple of time, but the boot stopped with the
message
halted CPU 0
halt code 2
kernel stack not valid halt
PC 180f8
I then switched off the machine, on again, boot single user, bcheckrc (did
salvage a little file) and full boot. The machine has been up and running
happily since then.
There is no track of what happened in uerf -R (binary err log), nor in
messages, nor in /var/adm/crash (this contains a 2-year old crash dump).
During boot I got a message saying that the crash could not complete the dump
(why ? because of the presence of the old one ? I saw that /var/adm/crash
itself was "touched" when the problem occurred, but no files inside it).
Questions now are :
- should I worry ?
- should I call DEC maintenance (but I have no further diagnostic elements)?
- is there any other place or tool which I can use to collect further
diagnostic elements
- (lower priority) why dump could not be completed ? is there anything
to do to prevent this next time ?
----------------------------------------------------------------------------
Lucio Chiappetti - IFCTR/CNR - via Bassini 15 - I-20133 Milano (Italy)
----------------------------------------------------------------------------
Fuscim donca de Miragn E tornem a sta scio' in Bregn
Che i fachign e i cortesagn Magl' insema no stagn begn
Drizza la', compa' Tapogn (Rabisch, II 41, 96-99)
----------------------------------------------------------------------------
For more info :
http://www.ifctr.mi.cnr.it/~lucio/personal.html
----------------------------------------------------------------------------
Received on Thu Jun 11 1998 - 16:06:16 NZST